At 10:30 AM +1100 on 5/26/99, spierings wrote:
>I can't wait to see a snapshot of the interpreter too. Please post it to me
>privately if you can't upload it Anthony. I have been looking at making an
>xTalk compiler based on Icon. It will take a lot of work but it looks
>promising. I was thinking for starters I could write an icon script to convert
>xTalk code into Icon and then compile the Icon and execute that. It would mean
>that we could program in xTalk or Icon in OpenCard. Icon is a very good
>language and has its advantages over xTalk and visa versa. if you are
>interested in checking out Icon you can find it at:
>
>http://www.cs.arizona.edu/icon/index.htm
OK. The next Interpreter release is Sunday. Anyone who me to send them interpreters
via email (since apparently Alain still has not got ASIP up) should tell me. I think I
can keep all distributions under 1/2 MB.
I also plan to make the frontend and backend seperate, so you might be able to create
an icon frontend.
>
>I think is is a much better compiler than Bison, but it is also more complex. I
>would like to do a speed test between the two at some stage.
Bison is not a compiler. It is a parser generator.
FYI: I'm doing a lot of egcs hacking presently and may at some point give egcs an
OpenTalk frontend.
