On 9/20/2013 8:05 PM, Craig A. Berry wrote:
On Sep 20, 2013, at 6:01 PM, John E. Malmberg
malmb...@encompasserve.org wrote:
After all, if you are going to always use Perl to invoke it, why
add the hack to make it work as a command file?
Because you may not use Perl to invoke it. You
On Sep 21, 2013, at 11:02 AM, John E. Malmberg malmb...@encompasserve.org
wrote:
On 9/20/2013 8:05 PM, Craig A. Berry wrote:
On Sep 20, 2013, at 6:01 PM, John E. Malmberg
malmb...@encompasserve.org wrote:
After all, if you are going to always use Perl to invoke it, why
add the hack
On 9/21/2013 12:48 PM, Craig A. Berry wrote:
On Sep 21, 2013, at 11:02 AM, John E. Malmberg malmb...@encompasserve.org
wrote:
On 9/20/2013 8:05 PM, Craig A. Berry wrote:
On Sep 20, 2013, at 6:01 PM, John E. Malmberg
malmb...@encompasserve.org wrote:
After all, if you are going to
On Sep 21, 2013, at 1:33 PM, John E. Malmberg malmb...@encompasserve.org
wrote:
The wrapper that simulates the shebang only runs it in a way that produces an
error message. I can not find any way to run it that takes advantage of the
wrapper and results in useful output.
All attempts
On Thu, Sep 19, 2013 at 10:29:37PM -0500, Craig A. Berry wrote:
On Sep 19, 2013, at 1:36 PM, Nicholas Clark n...@ccl4.org wrote:
So, my question is, surely that file should be installed as
utils/perldoc.COM not utils/perldoc?
Yes.
Would anyone notice if it wasn't installed as
The perldoc command looks weird on VMS, and I do not know the origin of
that convention.
VMS does not support shebangs.
Passing parameters on the command line to a program require that either
the DCL shell command tables be modified to know about that command, or
a foreign command to be
On 9/19/2013 1:36 PM, Nicholas Clark wrote:
If I delete the perldoc.com, I get this:
$ perldoc
Can't open perl script perl_root:[utils]perldoc.com: no such file or directory
%SYSTEM-F-ABORT, abort
(mail client may wrape the line)
LION show sym perldoc
PERLDOC == $PERL_ROOT:[00]PERL.EXE
On Sep 19, 2013, at 1:36 PM, Nicholas Clark n...@ccl4.org wrote:
So, my question is, surely that file should be installed as
utils/perldoc.COM not utils/perldoc?
Yes.
And if so, where in ExtUtils::MakeMaker does it need fixing?
Good question. ExtUtils::MakeMaker::MM_Unix::installbin says:
