At 05:45 PM 3/23/2002 -0500, Clinton A. Pierce wrote: >At 04:31 PM 3/23/2002 -0500, you wrote: >>I've just fixed several bugs in the read ops, I commited so do a cvs update. >>They were in the ops, not the IO system. Hasty coding is to blame, but I'm >>glad someone is actually testing this now. >> >>I wrote a slurp test that reads in a file by line and concats each buffer >>to the >>main string, then prints the string out, with the following patch it works >>ok, without it gets screwed up buffers. > >Okay. I've been unable to do a CVS update this afternoon, no response >from the server during the checkout. But what I discovered was this: > >* Using print/read everything works fine. There is Joy. >* Going anywhere near readline causes segvs >* Using puts/read takes me back to the bad-old-days of garbage in my >strings and stack from improper memory reclamation. > >I can't explain why, I only see the results. > >>>Second question: how do I use puts with a Ix register? That opcode >>>doesn't seem to work... >> >>It doesn't use an Ix reg, it uses an PMC IO stream. If you want to print >>to a stream use print PMC, STR on the PMC that open returned. > >No, no. I meant how do I output an Int or a Num to the output >stream? Print's nice enough to allow me to say: > > print S0 > print N0 > print I0 > >And the Right Thing happens. Ah well, since I'm avoiding puts for the >moment it's kind of a moot question.
Here is the patch. -Melvin
io.patch
Description: Binary data
