Op een grimmige herfstdag (Friday 29 October 2004 22:15),schreef Craig A.
Berry:
> At 8:30 PM +0200 10/29/04, Abe Timmerman wrote:
> >Craig A. Berry wrote:
> >Okay, so do we want the results of -Dusevmsdebug in the reports?
>
> I would make it a lower priority than various other options that
> don't get tested much, such as 64-bit support.
The "/macro..." thing needs to be hard coded (and already is), all normal
configure options can be put into a configuration file by the smoker.
While still working on the porting, I'll limit the number of configurations,
as it takes about 5 hours for a single configuration...
> >Another question is about PerlIO. Does VMS support the PERLIO logical? If
> > so, is there a difference between it being set to 'stdio' or 'perlio'?
>
> Hmm. At one time there was an issue with PERLIO defined to 'perlio'
> because the logical name is case blind so you'd end up in an infinite
> iteration. I limited the iteration but can't remember if we ended up
> with PerlIO being selectable this way. Does Test::Smoke configure
> and build with PerlIO enabled and then define PERLIO to stdio and
> re-run the test suite? I think that should work on VMS but I've
> never tried it.
Yes sort of. When configured, the test suite (mmk test_harness for vms) will
be run twice. Once with $ENV{PERLIO} = 'stdio' and once with $ENV{PERLIO} =
'perlio'.
I'll try and see what happens.
Thanks again +
Good luck,
Abe
--
Schwern> Just to appease the pedants I'll actually include a patch
Schwern> with this email that says "PATCH".
Such attention to detail :-)
-- Jarkko Hietaniemi on p5p @ 2003-04-07
