Um, it's not-so-useful this way (I want to transfer entire programs,
i.e. code with the state, like a serialized frozen virtual machine,
ready to be resumed at any time). What is easier to write -
disassembler, offset fixer (or similar bytecode patcher), or JIT
plug-in that saves source code together with byte code into a code
object, to allow for serialization?
On Mon, Nov 17, 2008 at 4:24 PM, Nicolas Cannasse
<[EMAIL PROTECTED]> wrote:
> Alexander Nikitin a écrit :
>>
>> Hi, Neko users!
>>
>> I wonder if Neko is able to serializable its very own code objects?
>> If i write a simple snippet like
>> a=function(x){...}
>> b=serialize(a)
>>
>> the exception 'Cannot serialize JIT method' is thrown.
>>
>> Is there a standard or custom solution for this problem? (Needed to do
>> transparent code transfer, for example, on-the-fly code patching and
>> so on)
>
> You cannot serialize functions, but you can serialize object prototypes,
> check http://nekovm.org/doc/view/serialize
>
> Best,
> Nicolas
>
>
> --
> Neko : One VM to run them all
> (http://nekovm.org)
>
--
With best wishes, Alexander Nikitin
icq 362376762 | +38 093 768-30-83 | [EMAIL PROTECTED] |
[EMAIL PROTECTED] | http://hall.org.ua/ |
http://hairlabs.org.ua/
--
Neko : One VM to run them all
(http://nekovm.org)
