m.invoke() vs. m()

[Neal Gafter]

On Mon, Dec 7, 2009 at 2:46 PM, Osvaldo Doederlein <opinali at gmail.com>wrote:

> The problem of separate variable/method namespaces can be handled by making
> the conflict illegal - any given scope cannot see two methods, or variables
> of closure type, with the same signature.


Things are not that simple.  What about nested scopes, or the scope of a
class/interface versus its subclasses/subinterfaces?  Hiding?  Shadowing?
Overloading?  These all have to be worked out.  I think it's worth doing,
but it's not trivial.

Cheers,
Neal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/closures-dev/attachments/20091207/eba6d3fd/attachment.html