At 12:51 PM -0700 3/3/06, Mark Berryman wrote: >On a related note (since I'm going to have to change code anyway): does any >one know why the logical DECC$FILENAME_UNIX_ONLY impacts the -e switch? As in: >$ >$ DEFINE DECC$FILENAME_UNIX_ONLY FALSE >$ perl -e "print 1;" >1 >$ DEFINE DECC$FILENAME_UNIX_ONLY TRUE >%DCL-I-SUPERSEDE, previous value of DECC$FILENAME_UNIX_ONLY has been superseded >$ perl -e "print 1;" >Can't open perl script "-e": no such file or directory >%RMS-E-FNF, file not found
My guess would be we're doing a syntax-only parse and considering it a switch rather than a file when the parse fails. With DECC$FILENAME_UNIX_ONLY enabled, "-e' is probably considered a valid filename, so we follow a different path, the one expecting it to be the name of a Perl script. That will need to be verified by stepping through the code, and of course something ought to be done about it. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
