At 02:27 AM 8/13/2002 -0400, Dan Sugalski wrote: >At 11:13 PM -0400 8/12/02, Clinton A. Pierce wrote: >>At 10:04 PM 8/12/2002 +0200, Jerome Quelin wrote: >> >>>I looked at parrot_assembly.pod and saw: >>> open px, sy >>> Open the file Y on filehandle X >>> read px, py, pz >>> Issue a read on the filehandle in y, and put the >>> result in PMC X. PMC Z is the sync object. >> >>Ow. The I/O still hurts my head even now. It seemed to be an ugly >>stepchild at the time. > >Anyone up to throwing a list of outstanding problems with the I/O system >together? We need to get I/O off of Melvin's altogether too-full plate >before his wife hunts me down and does nasty things, so this'd be a good >place to start.
I'd volunteer, except that I'm used to grunging around at the assembler level of I/O (INT 21h!) or with C's stdio and I don't think that your goal is either one of these targets. Frankly too, I don't understand the reasons and goals behind the monstrous complexity of Perl 6 and latter Perl 5's I/O. If you simply want a list of what we have outlined in core_ops, what works, what doesn't, and what's needed for a primitive I/O system... THAT I could piece together.
