John Wilson schrieb: [...] > Groovy has this as a potential issue because it also supports optional > typing.
All that follows is a response to this and specific to Groovy: but only because you say "any typing" -> "static typing". That is not the case in Groovy and we don't plan to go this route. Instead using a type is a way to ensure that my object will at runtime be at last of this type and it can be used by the compiler to guess methods. But it will not be used to bypass the Meta Object Protocol or force any type of static method selection. And after saying that there is no need for use to make a difference between a dynamic type and java.lang.Object. bye blackdrag -- Jochen "blackdrag" Theodorou The Groovy Project Tech Lead (http://groovy.codehaus.org) http://blackdragsview.blogspot.com/ http://www.g2one.com/ --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
