PerlIO - what next? - (should getc get a character?)

I have guts of a stack-of-layers PerlIO scheme coded now (//depot/perlio/... for those with perforce access - merge to 5.7.0 will occur as soon a Jarrko likes.) So we now have a C level mechanism for all the things we said we could do when we had "disciplines". The front of the queue is the UT

Re: PerlIO - what next? - (should getc get a character?)

> "NI" == Nick Ing-Simmons <[EMAIL PROTECTED]> writes: NI> I have guts of a stack-of-layers PerlIO scheme coded now NI> (//depot/perlio/... for those with perforce access - merge to 5.7.0 NI> will occur as soon a Jarrko likes.) does it support multiple instances for threads and asyn

Re: PerlIO - what next? - (should getc get a character?)

Uri Guttman <[EMAIL PROTECTED]> writes: >> "NI" == Nick Ing-Simmons <[EMAIL PROTECTED]> writes: > > > > NI> I have guts of a stack-of-layers PerlIO scheme coded now > NI> (//depot/perlio/... for those with perforce access - merge to 5.7.0 > NI> will occur as soon a Jarrko likes.) > >does i

Re: PerlIO - what next? - (should getc get a character?)

> "NI" == Nick Ing-Simmons <[EMAIL PROTECTED]> writes: >> and async i/o? NI> If I can find a system that has async IO I will give it a try. NI> I may do Win32 system that way ... i have an nice event kernel we can play with. better code than Event.pm. it is generic, uses control block