Community
Participate
Working Groups
Source based, v_833. When I released the first patch for bug 100278, it contained a typo for the literal value of JavaCore.COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_UNCHECKED_EXCEPTIONS, introducing a mismatch with CompilerOptions.OPTION_ReportUnusedDeclaredThrownException, and consequently an errant behavior when looked at from the API users standpoint. The simplest thing to do would be to initialize one of the constants series from the other's values. Since we do not want compiler to depend upon model, it would have to be the JavaCore constants initialized using the CompilerOptions ones. One issue with this is that then the resulting literal value would no more be displayed closed to the JavaCore constant. The remedy to this could come from bug 202490 and related ones (in that the literal value would then be explicit in the javadoc for the constant, lowering the need to display it in the code). Note that some means should be put in place anyway to test that the javadoc remains in sync with the literal value itself...
That would be good. Some test using reflect or so could be used. Along the same lines, a test ensuring that PublicScanner is really a clone of Scanner would be good as well.
