in reply to Re: When in Rome: Re: colons don't always separate path items!
in thread colons don't always separate path items!

I'd characterize lib's use of unix conventions as unusual. Having environment variables with values suitable for a different operating system would be odd. It might be because of the source file, operating environment distinction though. lib's value is used at compile time and is directly in the source so it may be less copacetic to require a OS-neutral representation. The environment variable though is completely divorced from the perl script. In fact, it is applicable to all perl scripts so in that context I still hold that it would strange to require unix conventions in a very non-unix place.

  • Comment on Re: Re: When in Rome: Re: colons don't always separate path items!

Replies are listed 'Best First'.
Re: Re: Re: When in Rome: Re: colons don't always separate path items!
by theorbtwo (Prior) on Jul 02, 2003 at 01:11 UTC

    Oh, lib's use of unix path conventions, and PERL5LIB (et al)'s use of the arch-specific list-of-paths seperators both make perfect sense. They're both the correct decisions for where they're being used and what they are. OTOH, I just meant to point out that nothing of that sort is obvious; they should all be documented.


    Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).