[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse-pmc] API Request: New IProblem constant
|
Discussing with Olivier, beyond the nice error message improvement (which
is rather cosmetics at this stage), it has nice characteristics in term of
error resilience which are improving some annotation processing behavior
(jsr269). Now, we still need confirmation that this kind of resilience is
indeed required, since by the spec, we don't have to do so.
Therefore, I think we should defer such a change for 3.4, where cosmetics
can be a fair enough reason to motivate such a change (along the lines of
making JDT more resilient).
Olivier Thomann
<Olivier_Thomann@
ca.ibm.com> To
Sent by: eclipse-pmc@xxxxxxxxxxx
eclipse-pmc-bounc cc
es@xxxxxxxxxxx
Subject
[eclipse-pmc] API Request: New
05/14/2007 05:59 IProblem constant
PM
Please respond to
eclipse-pmc@eclip
se.org
In order to provide a better support for annotation declaration
declaration, we would like to request the addition of a new
org.eclipse.jdt.core.compiler.IProblem constant:
InvalidUsageOfTypeParametersForAnnotationDeclaration
GOALS/BENEFITS:
- This new constant would be used to be able to report the corresponding
error in the Parser instead of failing with a syntax error. Preventing the
syntax error would help the compiler to report additional errors on the
same unit and not report additional syntax issues.
CORRESPONDING BUG:
- [1.5][compiler] Add more resilience on annotation type declaration with
type parameters
https://bugs.eclipse.org/bugs/show_bug.cgi?id=186822
RISKS:
No known risks.
PERFORMANCE IMPACTS:
None.
Olivier
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc