[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [Dltk-dev] bug #239707 discussion
|
Hi Michael,
I have started working on these two issues.
The correct solution would be
a) report problems from the reconciler to the annotation model. This
could be solved without breaking API, using code similar to the option #2.
b) report problems as markers from builder
Thanks for your ideas.
Regards,
Alex
Michael Spector wrote:
Hi All,
I would like to discuss possible solutions to the bug #239707
<https://bugs.eclipse.org/239707>
There are two solutions I can see now, the first is breaking the API
the other - is not:
1. Introduce new extension point: ISourceModuleProblemFinder that will
be responsible
for re-parsing a source module being reconciled. Implementing
extension class will accept
IProblemRequestor (which should be un-deprecated) for reporting on
found problems.
2. Use dirty hack, like this: http://pastebin.com/mf22397e
In addition, I think this bug should be solved ASAP, since reconciler
does not work properly.
What are your comments?
--
Michael
------------------------------------------------------------------------
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev
