On Fri, Jul 15, 2005 at 12:09:22PM -0400, John E. Malmberg wrote: > 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?
I presume you mean eliminate_macros and fixpath that exist in both ExtUtils::MM_VMS and File::Spec::VMS? I believe they started life in MakeMaker and then when File::Spec was carved out of MakeMaker they made the jump with them because catdir() and catfile() calls them. It makes no sense for the code to be in File::Spec, for starters they're object methods (everything in File::Spec is a class method) and do make macro expansion. So I pulled them back into MakeMaker and deprecated the File::Spec::VMS version. This also means MakeMaker can fix bugs in them without having to depend on a newer File::Spec. Long story short: MM_VMS' versions are the real ones. File::Spec's are vestigal. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Insulting our readers is part of our business model. http://somethingpositive.net/sp07122005.shtml
