Am 29.11.2011 13:39, schrieb Jochen Theodorou:
Am 28.11.2011 17:38, schrieb Julien Ponge:
Is it very different from the call sites in JRuby? They have a solid
> invokedynamic implementation to look at already. Might inspire you in
> a few places :-)
Is it different? afaik JRuby does not care about Class.forName for
example. Also I think JRuby doesn't have to handle method calls with a
null receiver and other things. I think many things are common, but only
with JRuby, with almost any invokedynamic using implementation. But you
get into details very fast and then it is not so equal anymore. For the
performance very important is also for example the guards you use. that
is very much internal and thus very different for JRuby and Groovy.
I should add, that the problems I have now are still very basic ones...
more about how to use the API correctly. I have for example to replace
an argument with a new value, but no real idea how to do that.
bye Jochen
--
Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
blog: http://blackdragsview.blogspot.com/
german groovy discussion newsgroup: de.comp.lang.misc
For Groovy programming sources visit http://groovy-lang.org
--
You received this message because you are subscribed to the Google Groups "JVM
Languages" group.
To post to this group, send email to jvm-languages@googlegroups.com.
To unsubscribe from this group, send email to
jvm-languages+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/jvm-languages?hl=en.
