*) Exceptions. (Adding the cope and hcf instructions for them)
*) A better C function call interface. (And an incredibly hackish one at that)
*) Finalized dynamic loading for PMCs and C libraries
*) Finalized embedding spec. (Based largely, I expect, on the
long-deferred work Brent's done)
*) First cut extension spec
Should be reasonably straightforward. Hopefully quick, too, as I'm
pressed for time here.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
Hmm... Object frameworks ? ... (or is that shelved for the present ?)
Gopal
--
The difference between insanity and genius is measured by success
Not shelved, no. (And arguably the infrastructure in place is
sufficient to do objects, but that's a bit of a stretch) But with the
things I've named, we have a complete functional core. (Well, OK, a
complete imperative core. Close enough) With an object framework, we
have an incomplete object core and incomplete functional core. I'm
feeling the need for some completion here. :)
Don't worry, objects will get done, and soon. I just wanted a short list there.
> ... These are the things going in, and in
> the order they're going in:
Could you comment on current unresolved issues:
- string_set, reusing string headers
- the inconsistencies in the PASM examples, especially the last one in
this thread:
"[CVS ci] string_set is back for a faster live - not only"
and a general roadmap considering:
- subject "Parrot 0.0.9"
- Buffer/PMC unification
- var/value vtable split
thanks,
leo