Craig A. Berry wrote:
At 5:31 PM -0500 1/26/06, John E. Malmberg wrote:
Martin Borgman of the Open Office on VMS team sent me this
information about a problem he had running Perl.
Because he also needs to run Java, his session has the logical name
DECC$ARGV_PARSE_STYLE defined as "ENABLE".
When this is set, the unquoted parameters are passed in exact case
to perl, and not converted to lower case.
He found this problem and there may be some others, and it looks
like in this case it should not be too hard to patch the
>> configure.com to fix this.
For PERLDOC, the resulting symbols need the -t to be in quotes in
one of these two ways:
$ PERLDOC :== -
$PERL_ROOT:[000000]PERL.EXE PERL_ROOT:[LIB.POD]PERLDOC.COM "-t"
$ PERLDOC == -
"$PERL_ROOT:[000000]PERL.EXE PERL_ROOT:[LIB.POD]PERLDOC.COM -t"
I'm confused. The -t is already in lower case. Or is that DCL
upcases it if you do not have extended parse enabled as well as
DECC$ARGV_PARSE_STYLE enabled?
DCL does not pay attention to the DECC$ARGV_PARSE_STYLE at all in this case.
If the quotes are missing, the foreign command symbol PERLDOC will have
-T in it instead of -t per standard DCL rules.
And then per the DECC$ARGV_PARSE_STYLE being enabled, the DECC RTL which
runs before main() is called in Perl will not lower case the parameter
as is the default behavior.
Martin is reporting that the result is that the PERLDOC command stops
working.
-John
[EMAIL PROTECTED]
Personal Opinion Only
