On Sun, Aug 31, 2003 at 12:03:48PM +0200, Leopold Toetsch wrote:
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> > class freezer {
> > class thawer {
> > class cloner {
>
> [ big snip ]
>
> Do you expect that these are overridden by some languages using parrot?
> I.e. that ponie tries to implement a freezer that writes output for
> Storable?
That would seem nice, but optional. I'd expect ponie's XS emulation interface
to be good enough to allow Storable to be compiled as is. (Maybe with some
tweaks, but only tweaks)
Storable should be a good test of ponie because it expects to do evil
things, prodding and poking the internals where it wasn't invited.
But that's for discussion on ponie-dev. Mmm. Or possibly not.
(ie "patches welcome" rather than discussion welcome)
> Further: having clone implemented in terms of freeze + thaw needs
> additional memory for the intermediate frozen image. Isn't that
> suboptimal?
I think it's suboptimal (not that you asked me)
However, it should work.
> A general traverse routine or iterator seems to be more flxible.
Because it would mean that cloning would just be another "output format"
for the freezer part. [Not sure if we can be sufficiently crafty to also
make traversing just another "input format" for the thawer part. Parrot
doesn't give us co-routines in C, does it :-)]
Nicholas Clark
