Re: [MacPerl-Porters] possible bug on #! line, PERL5OPTS

[Chris Nandor <pudge@pobox.com>]

At 09.11 -0500 1999.03.05, Arved Sandstrom wrote:
>I started digging into the source files to figure this one out, just so
>you know. For your example above, on my machine, it looks like MacPerl
>treats -w as the first line of code.

Just for clarification and to those who say "well, don't do that" about
putting -M flags on the #! line, I primarily want to use this in
$ENV{PERL5OPTS}.  It seems both have the same problem, and it is more
easily tested with #!.

>Could be some pretty subtle script bugs come out of this if the switch
>that you stuck in on the shebang line, after -M, was also a filetest
>operator. :-) Especially if the first line after the shebang was a ;#
>comment (you remember when some people were proselytizing ;# comment lines
>as opposed to just # comment lines? Goes a ways back.) Just some twisted
>musings on my part... :-)

Hmmmmm.

#!perl -MData::Dumper print -e 'Shuck Manual'
;# my program
print 'foo';
__END__

1foo

--
Chris Nandor          mailto:pudge@pobox.com         http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10  1FF77F13 8180B6B6'])

==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-porters-request@macperl.org