There was some discussion a while ago about having a whole class of array pmc, some for each type as well as some that auto expand and others that don't. I am about to go on a trip and will thus have time on the plane to implement such things; however, I do not recall any official decision about what each should be called and which should do what.
If someone would provide me with this basic information, I will go about implementing these things. Having looked at doing this before, I am not entirely sure which vtable functions should be defined in these classes, or if they should have an inheritance hierarchy of any type. But given a little guidance I can put in all the grunt work here.
Matt
Dan Sugalski wrote:
At 10:43 PM +0100 3/31/04, Jens Rieks wrote:
Hi,
On Wednesday 31 March 2004 20:42, Dan Sugalski wrote:
*) Get continuations all nailed down. There seems to be some lingering problems in the system I'd like identified with tests and fixed *) Get lexical pad operations spec'd out and possibly working *) Fix hash.c. (Though it may not be broken. Signs are good, though) *) MMD vtable ops in bytecode *) ICU building, if Jeff gets things integrated in time
Exceptions will be fixed later?
Yes. They still need some thought and work, and there's a limit to what I want to deal with in one go. After 0.1.1 beat me up about it and we'll get them fully specified and implemented, then we can release 0.2.0 :)
