Date: Wed, 7 Jun 1995 17:19:41 +0200 From: Wolfram Schneider <wosch@cs.tu-berlin.de> To: freebsd-current@FreeBSD.ORG (FreeBSD-current users), joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: perl[45] (Re: sup is fetching whole src tree) Message-ID: <199506071519.RAA18626@caramba.cs.tu-berlin.de> In-Reply-To: <199506040750.JAA26622@uriah.heep.sax.de> References: <199506040346.UAA18045@gndrsh.aac.dev.com> <199506040750.JAA26622@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Try:
$ perl4 -cw foo.perl
$ perl5 -cw foo.perl
-c causes perl to check the syntax of the script and then
exit without executing it.
-w prints warnings about identifiers that are mentioned
only once, and scalar variables that are used before
being set. Also warns about redefined subroutines, and
references to undefined filehandles or filehandles
opened readonly that you are attempting to write on.
Also warns you if you use == on values that don't look
like numbers, and if your subroutines recurse more than
100 deep.
Wolfram
J. Wunsch writes:
>As Rodney W. Grimes wrote:
>>
>> > While you're at it, how about making our custom version perl 5 clean?
>>
>> I am *NOT* a perl hacker, I can just scrap by fixing broken things. That
>> and can it be made to be both perl 4.136 and 5.0 clean? Remeber, FreeFall
>> runs releases, not the cutting edge, and the release is and will be for
>> some time at perl 4.136.
>
>Should be possible. Perl 5 has some syntax extensions, e.g. an
>unquoted @ within a "" string is now expanded; fixed scripts (that do
>not use the extensions, but take care of them) should be backwards
>compatible to Perl 4 however.
>
>I've been told that the perl 5 compiler gives a detailed error message.
>I don't have perl 5 by now, so please don't ask me... (yet).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506071519.RAA18626>