RE: [eclipse-pmc] API Request: New IProblem constant

["Walter Harley" <wharley@xxxxxxx>]

Error resilience is important for annotation processors running in the
IDE.  The JSR269 spec doesn't require it, because it doesn't address
behavior in the IDE; but our experience is that the more fault-tolerant
we can make the typesystem that is presented to the processors, the
better the user experience.  When code doesn't parse, the processors
tend to silently fail rather than being able to report semantic errors
on the legitimate part of the code as they are supposed to.

If there is a chance of getting this change in, perhaps for 3.3.1
instead of 3.4, it would be good, in my opinion.

Thanks,
  -walter


-----Original Message-----
From: eclipse-pmc-bounces@xxxxxxxxxxx
[mailto:eclipse-pmc-bounces@xxxxxxxxxxx] On Behalf Of Philippe P Mulet
Sent: Tuesday, May 15, 2007 6:44 AM
To: eclipse-pmc@xxxxxxxxxxx
Subject: 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


_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.