Re: Pluto updated

["Grisha" <grisha@...>]

Hi, Ben

Thanks again for great work, I'm going to include Pluto in our project
framework though it doesn't fit few of our requirements still:

1. String keys in unpersistables table (you know :) ). This puts a ban on
plugin architecture. Different set of plugins => different keys in the table
=> wrong reference links.

2. Userdata serialization. Serialization via closure requires userdata to
'transfer' its state into 'Lua' form. In our case we have complex universe
of Lua and C++ objects with references between all of them. So serialization
normally goes on both sides simultaneosly. So during serialization of
userdata we can (for example) encounter reference to some other C++ object
that needs to be serialized and this can go very far away from Lua side of
the project.
    If persist/unpersist metamethod could somehow get chunkreader/writer
passed to Pluto, this reader/writer can then be binded to any stream and
allow direct serialization of C++ data to it. I don't see how it can be done
nice way with just Lua closure fixups.

Best Regards,
Grisha


----- Original Message ----- 
From: "benjamin sunshine-hill" <bsunshin@usc.edu>
To: <lua@bazar2.conectiva.com.br>
Sent: Tuesday, June 08, 2004 6:16 AM
Subject: Pluto updated


> Version alpha2 of Pluto has been released. Among the highlights:
> * Full support for Lua closures
> * Userdata are persistable
> * Special (metafunction) persistence now implemented
> * More comprehensive docs, including file format documentation
>
> Get it from the wiki: http://lua-users.org/wiki/PlutoLibrary
>
> Ben
>