Perl problems...

[Edward Glowacki]

Hmm... interesting... that seems to help a lot, now just have to find a
good way to get those paths in the include path... tried adding spaces
before the -I's to push them past the 32 char limit, but it didn't seem to
work right...

-- 
Edward Glowacki			glowack2@msu.edu
A PBS mind in an MTV world. 
	-- Author unknown

On 3 Apr 2000, Ben Pfaff wrote:

> Edward Glowacki <glowack2@key-largo.cl.msu.edu> writes:
> 
> > OK, I'm really really confused now...  Is there any difference between
> > these two, because they don't behave the same:
> > 
> > First line of script.pl:
> > #!/usr/bin/perl -w -I/usr/local/etc -I/usr/local/bin
> > 
> > Command line:
> > # perl -w -I/usr/local/etc -I/usr/local/bin script.pl
> 
> >From perlrun(1p):
> 
>        Because many operating systems silently chop off kernel
>        interpretation of the #! line after 32 characters, some
>        switches may be passed in on the command line, and some
>        may not; you could even get a "-" without its letter, if
>        you're not careful.  You probably want to make sure that
>        all your switches fall either before or after that 32
>        character boundary.  Most switches don't actually care if
>        they're processed redundantly, but getting a - instead of
>        a complete switch could cause Perl to try to execute
>        standard input instead of your script.  And a partial -I
>        switch could also cause odd results.
>