At 4:59 PM -0500 12/31/02, [EMAIL PROTECTED] wrote:

>I found a problem with the main descrip.mms file and
>its handling of perly.c and perly.h (the additional /NoConfirm
>qualifier change was a bit too aggressive about getting
>rid of the $(MMS$TARGET) macros).

Were you having a specific problem the way it was?  The problem with
$(MMS$TARGET) is that it is an upcased version of the target
filename.  However, if we specify only the target directory, allowing
the name part of the file spec to be defaulted, then the case of the
source filename will be preserved by the COPY command.  Obviously
this only has relevance on ODS-5 volumes.  At the moment, preserving
case may be mostly a cosmetic issue, but there will be (is already)
an ODS-5 option that is case sensitive as well as case preserving.
Even now, with various special C RTL logicals defined, C programs
(and thus Perl programs) might not see PERLY.H when they are looking
for perly.h.

> I've also included
>a potential fix for the test failure in:
>ext/Filter/t/call....................FAILED at test 30
>
>Here it is:
>
>diff -ru perl_18376/ext/Filter/t/call.t perl/ext/Filter/t/call.t
>--- perl_18376/ext/Filter/t/call.t  Sun Dec  8 19:26:42 2002
>+++ perl/ext/Filter/t/call.t  Tue Dec 31 16:43:30 2002

That looks good.

>diff -ru perl_18376/vms/descrip_mms.template perl/vms/descrip_mms.template
>--- perl_18376/vms/descrip_mms.template   Wed Dec 11 04:57:06 2002
>+++ perl/vms/descrip_mms.template   Tue Dec 31 16:42:42 2002
>@@ -1174,9 +1174,9 @@
>
> # VMS uses modified perly.[ch] with tags for globaldefs if using DEC compiler
> perly.c : [.vms]perly_c.vms
>-     Copy/NoConfirm/Log $(MMS$SOURCE) []
>+     Copy/NoConfirm/Log $(MMS$SOURCE) $(MMS$TARGET)
> perly.h : [.vms]perly_h.vms
>-     Copy/NoConfirm/Log $(MMS$SOURCE) []
>+     Copy/NoConfirm/Log $(MMS$SOURCE) $(MMS$TARGET)

I'd hold off on this until I know what problem the current
implementation is causing.  I can't see how it could go wrong unless
you're default directory is not the main source directory, and if
that's the case this would be the least of your problems.

>I also found a way to work around the problem with this failure:
>
>lib/ExtUtils/t/Constant..............FAILED at test 27
>
>but I am not too certain about which MakeMaker is in perl@18376

I'm not either, but whatever it is it's going to change.  But is
Constant.t part of MakeMaker?  I don't see it in the current snapshot.

>By the way is anyone else upset that on Unix you can escape
>perl's globbing, e.g. in the perl source tree:
>
>unix_prompt% ./perl -e 'print join("< >",@ARGV),"\n"' perl.*
>perl.c< >perl.h< >perl.h.orig< >perl.o
>unix_prompt% ./perl -e 'print join("< >",@ARGV),"\n"' "perl.*"
>perl.*

I guess I don't know enough about what that means to miss it.  Are
you saying that double quotes around an argument prevents wildcard
expansion?
-- 
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Reply via email to