Re: 0.1.0

2003-02-26 Thread Steve Fink
On Feb-25, Leon Brocard wrote: > David sent the following bits through the ether: > > > Thanks. I better upgrade my version, I'm not seeing it in 0.0.9. > > It's been a while since 0.0.9 (errr, 20th Dec). A lot has changed > since then. Maybe it's time for a 0.1.0 release. What are we waiting > f

Re: 0.1.0

2003-02-25 Thread Piers Cawley
Jerome Quelin <[EMAIL PROTECTED]> writes: > And even toy languages may benefit from objects (yes, I really need > objects in order to implement -98 version of Befunge, especially > since I want to include concurrent-funge support). Well, I could use > my own hand-crafted objects as a list of whatev

Re: 0.1.0

2003-02-25 Thread Leon Brocard
Dan Sugalski sent the following bits through the ether: > While I'll call C many things (not all of them repeatable) I'm not > sure "toy" is one of them. Nor Forth, Fortran, APL, COBOL, Lisp, or > Basic... :) Granted, but those aren't the languages we're interested in. Parrot is for dynamic lan

Re: 0.1.0

2003-02-25 Thread Dan Sugalski
At 4:52 PM + 2/25/03, Leon Brocard wrote: David sent the following bits through the ether: Thanks. I better upgrade my version, I'm not seeing it in 0.0.9. It's been a while since 0.0.9 (errr, 20th Dec). A lot has changed since then. Maybe it's time for a 0.1.0 release. What are we waiting fo

Re: 0.1.0

2003-02-25 Thread Simon Glover
On Tue, 25 Feb 2003, Jerome Quelin wrote: > I want to include concurrent-funge support. I'm not even going to ask :-) Simon

Re: 0.1.0

2003-02-25 Thread Jerome Quelin
Leon Brocard wrote: > It's been a while since 0.0.9 (errr, 20th Dec). A lot has changed > since then. Maybe it's time for a 0.1.0 release. What are we waiting > for? Dan said: "either exceptions or objects". Once we have one, we'll go to 0.1.0, and when the second will be implemented (order does