At 8:30 PM +0200 10/29/04, Abe Timmerman wrote: >Craig A. Berry wrote: >> usevmsdebug compiles and links everything for the > >VMS debugger (more or less equivalent to gdb).
>A bit like: -Doptimize='-g' ? Yes. >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. >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. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
