I accidently did override a private method in the superclass, in the java vm this no problem since it know that is shielded, but in JS is does not, it will override the private method in the super class which should not happen.
This could either be disallowed or somehow solved in JS, but will be more difficult problem to solve. At least there should be warning.
andySun 25 Sep 2011
I'm aware of that issue - it's one we'll need to address soon. A proper solution is going to be a bit gnarly - but maybe we can live with a compiler error for now.
alex_panchenkoSun 25 Sep 2011
Name mangling for private functions could help. It should be easy enough to implement.
andySun 25 Sep 2011
Name mangling for private functions could help.
Thats the gnarly part ;) A few tens/hundreds thousands lines of native code to update.
jessevdam Sun 25 Sep 2011
I accidently did override a private method in the superclass, in the java vm this no problem since it know that is shielded, but in JS is does not, it will override the private method in the super class which should not happen.
This could either be disallowed or somehow solved in JS, but will be more difficult problem to solve. At least there should be warning.
andy Sun 25 Sep 2011
I'm aware of that issue - it's one we'll need to address soon. A proper solution is going to be a bit gnarly - but maybe we can live with a compiler error for now.
alex_panchenko Sun 25 Sep 2011
Name mangling for private functions could help. It should be easy enough to implement.
andy Sun 25 Sep 2011
Thats the gnarly part ;) A few tens/hundreds thousands lines of native code to update.