Tom Edelson wrote:
One thing to consider (again from PERLVMS):
PERL_ENV_TABLES is translated once when Perl starts up; any changes you make
while Perl is running do not affect the behavior of %ENV .
That can be dealt with in several ways.
1. It can be properly set before running Perl that needs to run
MakeMaker, and Makemaker can optionally verify the setting in a VMS
specific INIT setting.
The advantage is that that should work with out changing Perl, so would
work on older Perls.
2. I can remove that restriction by implementing a method that changes
the PERL_ENV_TABLES value in use. But that would mean the resultant
modified Makemaker would be dependent on that patch to remove those VMSisms.
3. A conservative approach would be to check the PERL_ENV_TABLES setting
in the macro expansion routine and if they are set correctly not do the
macro replacement. But this does not simplify the code maintenance.
The comments indicated that the person that put in the macro expansion
did not understand why MMS/MMK were not doing the expansions.
An issue that this also brings up is that there are two modules that do
the macro expansion. One in MM_VMS.PM which overrides the methods in
VMS.PM which also do macro replacements.
Are those macro expansions only there in VMS.PM for Makemaker which no
longer uses them?
Or if Makemaker did not need to do the macro expansions on VMS, would
all that code be able to just go away?
-John
[EMAIL PROTECTED]
Personal Opinion Only
