m.invoke() vs. m()
ricky.clarkson at gmail.com
Sat Dec 5 06:59:08 PST 2009
Fine, but if it's a warning it shouldn't be active by default.
Warnings that you cannot (or won't want to) program your way out of
should not be enabled by default. This was a mistake Java 5 made, and
look how long it took people to move to it, compared to the 1.3 -> 1.4
or 5 -> 6 moves. I don't count @SuppressWarnings as programming your
way out of it.
2009/12/5 Vladimir Kirichenko <vladimir.kirichenko at gmail.com>:
> Ricky Clarkson wrote:
>> Whereas the only interpretation that actually makes sense is to choose
>> the closest in lexical scope.
> Or compiler should report an ambiguity error or shadowing warning.
> Any of these is better than "invoke".
> Best Regards,
> Vladimir Kirichenko
Java and Scala Programmer, AD Holdings
+44 1565 770804
Google Talk: ricky.clarkson at gmail.com
Google Wave: ricky.clarkson at googlewave.com
More information about the closures-dev