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
--- Begin Message ---
Andrew J Bromage wrote:
>
> G'day all.
>
> I'm working on the Optimizer (adding a new intermediate form to allow
> for more aggressive optimization) but mail to Jeff Goff seems to be
> bouncing. Does anyone know where he is?
>
> Cheers,
> Andrew Bromage
No idea :)
It'
G'day all.
I'm working on the Optimizer (adding a new intermediate form to allow
for more aggressive optimization) but mail to Jeff Goff seems to be
bouncing. Does anyone know where he is?
Cheers,
Andrew Bromage
Hi.
Congratulations, you've made a lot of progress during the last two months.
Trying to get back I read embed.c and made a trivial cleanup:
[PATCH] in attachment:
Changed struct Parrot_interp * to Parrot, following the typedef in
parrot.h (I believe).
Boris.
diff -r1.18 embed.c
21c21
< str
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
At 04:45 PM 3/23/2002 -0500, Dan Sugalski wrote:
>Okay, folks, I think it's time for some really heavy-duty, nasty tests.
>Up until now, all the testa hve been reasonably small, to check for core
>functionality. This is a good thing. We've now verified that things like
>eq and pushp work right.
At 04:46 PM 3/23/2002 -0500, Dan Sugalski wrote:
>At 4:41 PM -0500 3/23/02, Melvin Smith wrote:
>>At 01:42 PM 3/23/2002 -0800, Brent Dax wrote:
>>>and Python--languages where you can redefine the world at any time. JVM
>>>and the CLR aren't written in a way that allows for such dynamic
>>>behavio
At 4:41 PM -0500 3/23/02, Melvin Smith wrote:
>At 01:42 PM 3/23/2002 -0800, Brent Dax wrote:
>>and Python--languages where you can redefine the world at any time. JVM
>>and the CLR aren't written in a way that allows for such dynamic
>>behavior, so we're making a third VM that does.
>
>"... and o
Okay, folks, I think it's time for some really heavy-duty, nasty tests.
Up until now, all the testa hve been reasonably small, to check for
core functionality. This is a good thing. We've now verified that
things like eq and pushp work right.
What we need to do now is verify that the interpret
At 01:42 PM 3/23/2002 -0800, Brent Dax wrote:
>and Python--languages where you can redefine the world at any time. JVM
>and the CLR aren't written in a way that allows for such dynamic
>behavior, so we're making a third VM that does.
"... and one VM to rule them all"
-Melvin
[EMAIL PROTECTED]:
# Sorry for a kind of off topic post but I haven't got a reply from
# [EMAIL PROTECTED] (I'd guess with all the other things in
# his life my
# question was kind of low on the food chain.)
#
# After a rather bad start with the idea of parrot (I missed
# the whole joke
# of Per
At 12:02 PM -0800 3/23/02, <[EMAIL PROTECTED]> wrote:
>After a rather bad start with the idea of parrot (I missed the whole joke
>of Perl and python) I found this list and have been lurking. Other than
>listening to real programmers talk - and enjoying it - I'm wondering if
>parrot is (or will) b
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
Sorry for a kind of off topic post but I haven't got a reply from
[EMAIL PROTECTED] (I'd guess with all the other things in his life my
question was kind of low on the food chain.)
After a rather bad start with the idea of parrot (I missed the whole joke
of Perl and python) I found this list
At 01:45 PM 3/23/2002 -0500, Melvin Smith wrote:
>At 01:40 PM 3/23/2002 -0500, Melvin Smith wrote:
>NEXTLINE:
>> read S0, 256
>>-- print S0
>++ puts S0
>> branch NEXTLINE
>> end
>
>Correction, print is stdio, puts is PIO. Use puts if you are using read.
>I just ch
At 01:40 PM 3/23/2002 -0500, Melvin Smith wrote:
NEXTLINE:
> read S0, 256
>-- print S0
++ puts S0
> branch NEXTLINE
> end
Correction, print is stdio, puts is PIO. Use puts if you are using read.
I just checked it into CVS btw.
-Melvin
At 01:00 PM 3/23/2002 -0500, Clinton A. Pierce wrote:
>For your weekend entertainment, here's a bit of parrot assembler for the
>adventurous to play with. To get the code, just head to:
>http://geeksalad.org/basic and download the latest tar bundle you
>find. The README.basic file included in
Does anyone else see this?
# ./parrot examples/assembly/life.pbc
500 generations in 1.784740 seconds. 280.152856 generations/sec
A total of 32768 bytes were allocated
A total of 13094 DOD runs were made
A total of 1104 collection runs were made
Copying a total of 0 bytes
There are 61 active Buffe
For your weekend entertainment, here's a bit of parrot assembler for the
adventurous to play with. To get the code, just head to:
http://geeksalad.org/basic and download the latest tar bundle you
find. The README.basic file included in the tar bundle is listed after this.
[Small amount of be
21 matches
Mail list logo
