At 2:43 PM + 3/24/02, Nicholas Clark wrote:
>On Sun, Mar 24, 2002 at 01:06:40AM -0500, Clinton A. Pierce wrote:
> > But if ya can get the data in, everything works *great*. Interactive
>> mode's all working now, even a functonal INPUT statement. My TODO's are
>> down to: 1. making sure th
On Sun, Mar 24, 2002 at 01:06:40AM -0500, Clinton A. Pierce wrote:
> I just got this message and it's 1am. There's no way I'm applying patches
> this late. :)
Wise man.
> But if ya can get the data in, everything works *great*. Interactive
> mode's all working now, even a functonal INPUT st
I just got this message and it's 1am. There's no way I'm applying patches
this late. :)
The situation I've got now works reasonably well using read/print. The
version of BASIC I just uploaded to geeksalad.org/basic is okay unless you
try performing a LOAD more than once with a reasonably la
At 05:45 PM 3/23/2002 -0500, Clinton A. Pierce wrote:
>At 04:31 PM 3/23/2002 -0500, you wrote:
>Okay. I've been unable to do a CVS update this afternoon, no response
>from the
Same here, having problems.
print S0
> print N0
> print I0
>
>And the Right Thing happens. A
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.
>>
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 con
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 pr
