At 02:27 AM 8/13/2002 -0400, Dan Sugalski wrote:
>Anyone up to throwing a list of outstanding
> problems with the I/O system together?
From: Clinton A. Pierce [mailto:[EMAIL PROTECTED]]
>I'd volunteer, except that I'm used to grunging
> around at the assembler level of I/O (INT 21h!)
> or with C'
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
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 p
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 obje
On Mon, 12 Aug 2002, Jerome Quelin wrote:
> Thus, I thought this one was the one I wanted. So:
> LOAD:
> read S0, 256
> chopn S0, 1 # trailing newline
> open I10, S0, "r"
> eq I10, 0, ERR_IO
> set S1, ""# Accumulator
> LOAD_READ:
> read S1, I10
