Abusing these so they aren't just virtual wrappers, and are actually
efficient (as they can all be done as a plain C array of pointers or
values--they don't have to be, and probably shouldn't be, sparse)
would certainly be a Good Thing.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
On Tuesday 30 March 2004 18:57, Dan Sugalski wrote:
> I just checked in stub code for the PMCArray and StringArray classes.
I've attached a patch for the data dumper.
> Ultimately they should be auto-resizeable, PMC or String only arrays,
> though right now they aren't. (They wrap PerlArray right now, so
> they're far from efficient, but at least they're in to be used)
> Integer and Float arrays should probably go in, and we should add in
> the non-auto-resizing versions as well.
>
> Abusing these so they aren't just virtual wrappers, and are actually
> efficient (as they can all be done as a plain C array of pointers or
> values--they don't have to be, and probably shouldn't be, sparse)
> would certainly be a Good Thing.
The EBNF Parser is now using PMCArrays.
jens
Applied, thanks.