Hi Gents,
This is new territory for my as I do not do C, but if someone can
confirm for me the following, it might help me at least move in the
right direction.
Yes, I'm still screwing around with CPAN.pm and I believe I see what is
happening and I've attempted to add calls to CPAN to vmsify the target
files, but nothing changed. So I added debug lines to [.VMS]Filespec.pm
and was taken back a bit when none worked, except the main routine at
Perl startup. I then noticed the comments at the top of Filespec.pm
referring to the vms.c hooks.
If I understand (aka guess) properly, at run time the default calls to
VMS::Filespec are basically being redirected to hardcoded C by way of
the newXSproto calls, which might explain why my debug statements in
Filespec.pm are not working. First, is this what is happening? If not,
then does anyone have any idea as to why I'm not getting basic print
debug lines I've added to Filespec.pm?
Best regards,
Barry
--
Barry Treahy, Jr E-mail: [EMAIL PROTECTED]
Midwest Microwave Phone: 480/314-1320
Vice President & CIO FAX: 480/661-7028
- Re: VMS::Filespec vs. hardcoding in VMS.C in Perl 5... Barry Treahy, Jr.
- Re: VMS::Filespec vs. hardcoding in VMS.C in P... Craig Berry
- Re: VMS::Filespec vs. hardcoding in VMS.C ... Barry Treahy, Jr.
- Re: VMS::Filespec vs. hardcoding in VMS.C in P... Dr. Martin P.J. Zinser
- Re: VMS::Filespec vs. hardcoding in VMS.C in P... Craig Berry
- Re: VMS::Filespec vs. hardcoding in VMS.C ... Barry Treahy, Jr.
