Hi,
Yes, I have read pages and code of v8-juice and vu8,
but as I understood, both are template based,
require compilation (of module) and work at
compile time.
What I need is runtime binding.
A frequent use case is to create(open) the library instance
and AFTER that, the (end) user implement/create a method
to bind to a function... send the message...
and thats all! the result is there (if we are lucky :-P )
If a new function needs to be called, the same
library instance is used and a new method is built
on the fly to bind another function... etc.
If there is a new version of the DLL, it can be
created a new instance of library; open and add/edit/remove
methods to use them instantly (the "old" running instance
of the library will complete it's lifecycle as usual with
all objects, been collected when appropiate)
hope this help to clarify the point,
and justify my presistence with the topic :-)
kind regards,
Ale.
----- Original Message -----
From: "gqt65" <[email protected]>
To: "v8-users" <[email protected]>
Sent: Wednesday, March 30, 2011 12:35 PM
Subject: [v8-users] Re: Dynamic bindings (C and API calls) (was: Re:
Expanding the language)
Check this out:
http://code.google.com/p/v8-juice/wiki/HomePage
I haven't had the time for deep reading yet, but it seems it may be
helpful.
--
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
