begin quote from Steve Fink:
> Perhaps a target version for each item?
Oh, bother. This is the second time I've been asked about this, so I
suspect that my goals for the forthcoming releases aren't amazingly
clear.
Here is the Grand Pronouncement!
0.0.4 WILL HAPPEN WHEN we have decent keyed aggregate support, and
support for other string encodings to the same level as ASCII. (This may
have to slip, since it's a biggy.)
0.0.5 WILL HAPPEN WHEN we have symbol table and heap access. This also
includes storage of subroutines in the symbol table, which in turn
requires the serialisation of PMCs to the bytecode constant table.
0.0.6 WILL HAPPEN WHEN we have Really Good GC support.
0.1.0 WILL HAPPEN WHEN we have an implementation of one reasonably
well-known high-level programming language. That's to say, Perl, Python,
Scheme, etc. Parsing does not need to be included, nor a full "library";
just running bytecode is fine.
Given that the Unicode requirement may slip, expect 0.0.4 relatively
soon.
--
buf[hdr[0]] = 0; /* unbelievably lazy ken (twit) */ - Andrew Hume
