Craig A. Berry <[EMAIL PROTECTED]> writes: >At 10:04 PM +0100 5/21/02, Nick Ing-Simmons wrote: > >>Okay - can you do the PERLIO=perlio thing and run the whole test suite? >> >>If that looks "good" the above may suffice for 5.8 > >Sigh. Putting PERLIO=perlio in the environment introduces at least >the following test failures: > >lib/ExtUtils/t/Embed................FAILED at test 6 >lib/File/Copy.......................FAILED at test 4 > > >and in lib/warnings it runs up to > ># From lib/warnings/perlio. >ok 291 >ok 292 > >and then gets stuck forever in a cpu-bound loop.
It would be good to get VMS working with :perlio as well. However if the test suite has tests which test VMS's stdio extensions they will not work right with :perlio. IIRC from way back VMS occasionaly needs to get a file name for an open handle - its stdio does that but currently PerlIO does not save that information itself. So there maybe things that will not work with :perlio - but it would be good to figure out what those are with a view to fixing them in 5.9* Can someone re-try with bleadperl with the ungetc() fixes? I don't think they should affect anything. -- Nick Ing-Simmons http://www.ni-s.u-net.com/
