At 11:17 AM 4/3/00 -0400, Charles Lane wrote:
>This should have been CC:'d to vmsperl
>
>----- Start of forwarded message[s] -----
>Return-path: <[EMAIL PROTECTED]>
>Date: Mon, 3 Apr 2000 11:15:47 EDT
>From: lane (Charles Lane) @ DUPHY4.Physics.Drexel.Edu
>Message-Id: <[EMAIL PROTECTED]>
>Subject: Re: [ID 20000330.044] Not OK: perl v5.6.0 on VMS_AXP V7.1
>In-Reply-To: Your message <[EMAIL PROTECTED]>
>dated 3-Apr-2000
>To: BAILEY @ newman.upenn.edu
>Bcc: lane @ DUPHY4.Physics.Drexel.Edu
>
>Charles Bailey [EMAIL PROTECTED] writes:
> > Charles Lane <[EMAIL PROTECTED]> wrote:
>
> > | A patch for the glob-basic test was posted here on 17 Mar.
>
> > It's in the repository, but I think it just missed being wrapped
> > into the 5.6.0 kit as sarathy was trying to minimize changes.
> > The GLOB_NOCASE question is stil up in the air (briefly: would
> > it be best under VMS to add GLOB_NOCASE to all calls, since the
> > filesystem is monocase?).
>
>Well, maybe our friends at Compaq/DEC could gives us a hint: is
>VMS going to go "cased" anytime in the forseeable future? With all
>the other "creeping unixisms", I figure cased filenames can't be
>that far behind...
I expect there'll be a number of dead bodies in VMS engineering required
before a case-sensitive filesystem goes in. :)
> > | The piping changes depend on PERL_ROOT being defined so that the
> > | DCL wrapper file can be found when spawning subprocesses; in
> > | discussion with Charles Bailey it was clear that other approaches
> > | (writing local tempfiles) weren't very secure...and I don't much
> > | like the idea of "hard-coding" a directory spec into the code.
> > |
> > | Is it worth looking for a different method just so we can avoid
> > | using PERL_ROOT during build/test?
>
> > How 'bout doing a regular @INC lookup, and installing vmspipe.com in
> > the library?
>
>Hmmm....that's got a ton of implications, you know.
>
>For example, a user's script mucks around with @INC and then can't do
>any system() calls. Not exactly an "obvious consequence".
That'd be profoundly bad, I think. Hardcoding PERL_ROOT:[LIB] (or wherever
it goes by default) as a final default might not be unreasonable.
>I'll have to do some poking to see whether a @INC scheme would work
>for miniperl during the build...since miniperl can't do "use" but
>does do "system()", it's not clear that @INC is set up properly.
miniperl *can* do a use. It can do anything that perl can except use XS
modules. Regular .PM-only ones work just dandy. (The build of perl itself
couldn't succeed if that weren't the case)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
