home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.perl
- Path: sparky!uunet!usc!news.cerf.net!netlabs!lwall
- From: lwall@netlabs.com (Larry Wall)
- Subject: Re: Perl IV & V incompatibilities?
- Message-ID: <1992Dec19.023709.2700@netlabs.com>
- Sender: news@netlabs.com
- Nntp-Posting-Host: scalpel.netlabs.com
- Organization: NetLabs, Inc.
- References: <1992Dec17.175420.19745@merlin.dev.cdx.mot.com>
- Date: Sat, 19 Dec 1992 02:37:09 GMT
- Lines: 33
-
- In article <1992Dec17.175420.19745@merlin.dev.cdx.mot.com> lezz@merlin.dev.cdx.mot.com (Lezz Giles) writes:
- :
- : I'm getting a little bit scared about Perl V - I have lots of Perl IV code
- : and I'm scared that it'll all have to be rewritten when I move to Perl V.
- : So my question is very simple - what _isn't_ compatible? What will need
- : to be rewritten?
-
- Here's my current list of incompatibilities:
-
- The second and third arguments of splice are now evaluated in scalar
- context (like the book says) rather than list context.
-
- Saying shift @foo + 20 is now a semantic error.
-
- The elements of argument lists for formats are now evaluated in list
- context.
-
- You can't do a goto into a block that is optimized away.
-
- Some error messages will be different.
-
- s'$lhs'$rhs' now does no interpolation on either side. It used to
- interplolate $lhs but not $rhs.
-
- Not a real big list, as you can see. I think that the list context for
- format arguments is probably the likeliest one to bite you, and it's
- real easy to work around. Unless, of course, you're in the habit of
- using "goto" to enter "while (0)" blocks...
-
- I may well deprecate select(FILEHANDLE) in favor of some other mechanism,
- but I won't break it (yet).
-
- Larry
-