I think we were trying to help people avoid the confusing bug of
accidentally redefing call and apply, and getting obscure bugs because
they forgot those were JavaScript builtins
Sent from my iPhone
On May 8, 2010, at 11:27 AM, André Bargull <[email protected]>
wrote:
Both, "apply" and "call" are marked as final in lfc-undeclared.xml,
is there any reason for this decision? I know this question was
already raised in an earlier thread.
I'm working on LPP-8982, LPP-8983 and LPP-8986 and I think I've
found a way to fix these bugs, but unfortunately compiling an
application will now result in a compiler warning caused by
<state>#apply():
trunk/WEB-INF/lps/schema/lfc.lzx:509:42: Method state.apply is
overriding a superclass method of the same name which has been
declared final
The compiler warning is actually correct, if apply() is final it
should not be possible to declare a method named "apply" in <state>.
So, should I just remove those annotations from lfc-undeclared or
add an ugly workaround to the compiler or ...?
- André
