Friedrich Weber a écrit :
Hi all,
thanks for your thoughts :)
Nicolas, I think the approach is cool for immutable values, but if I use
mutable Neko values (like an array for example), my wrap function will
create a wrapper object each time I use this value (and that's not
optimal) - or am I missing something?
Yes. You'll have to create a wrapper object each time you're accessing a
method/field that is part of your API. Depending on your API size it
might be a lot of accesses or not. But allocating a new object is quite
fast so not a very big issue here.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
