Ticket #67 (closed defect: fixed)

Opened 6 months ago

Last modified 3 months ago

Medium problems with editor on Eclipse 3.4 RC4

Reported by: gahen Assigned to: mb0
Priority: blocker Milestone: AXDT 0.0.7
Component: editor Version: AXDT 0.0.2
Keywords: Eclipse RC4 Cc:

Description (Last modified by mb0)

I have IMP 1.74, LPG Runtime 2.0.12, SDF and BOX 1.0.9 (I read IMP may use it), and AXDT Feature 0.0.2.

Everything seems to work fine when looking at code, but some editing capabilities are missing. I get no code hinting, and a weird error description, with some efficiency issues. The main problem seems to be the syntax error handler. When the editor detects an syntax error, it keeps "refreshing" it forever (fast blinking from black to red, and from red underlined to no underlined), and when I ctrl-space after some text (for example "pub") it says "No info available due to syntax errors", when the only one I get is the line I'm writing. Except for this and other derived errors, the editor seems to work right.

Thanks, Joaquín.

Change History

06/25/08 18:58:12 changed by mb0

  • owner changed from asdt.org to mb0.
  • status changed from new to assigned.

you dont need to install SDF and BOX.

i can reproduce the error on ganymede and i have a guess for the refreshing craze. the editor requests a model of the document but the content has errors so no model is returned (eclipse imp will provide prosthesis nodes for missing syntax later). at some point in the reconciler asks for the model again, there is none, try to compile, no ast due to errors, repeat.

i will try to look into it but it has a low priority right now. chances are high that the current svn version of imp has already a fix. it will certainly be fixed for the next imp release.

thanks for testing - i report back when i know more.

06/25/08 20:56:09 changed by mb0

my first guess was almost right. the problem is not another request but a change notification that is received by the reconciler.

i think this is fixed in imp svn. i found this snippet in the ParserScheduler (that was moved to its own file since 1.7.4): 

public void notifyAstListeners(IProgressMonitor monitor) {
        // Suppress the notification if there's no AST (e.g. due to a parse error)
        if (fParseController != null) {
           ...

however i did not tested it with the svn version. we have to wait anyway for the imp release.

08/07/08 18:57:03 changed by mb0

  • priority changed from trivial to blocker.
  • severity changed.
  • description changed.
  • milestone set to AXDT 0.0.5.

i changed to eclipse 3.4 and this bug makes axdt unusable.

i debugged it in detail yesterday but could not figure out how to fix it. it seems that the PresentationReconciler schedules the ParserSchedular without a input change. maybe the error markers trigger it ?!

however there are big related changes on svn. so without having tested it i think its fixed in the next imp build.

08/09/08 03:44:14 changed by dain@cipherprime.com

I can confirm this bug in Eclipse 3.4. The refreshing issue renders axdt unusable -- a shame, because I'm looking forward to using it for production work. Error fires as follows:

An internal error occurred during: "Language[name=AS3,description=The ActionScript?3 programming language for flash.,filename extensions=[as]] ParserScheduler?". java.lang.NullPointerException?

10/08/08 11:05:51 changed by mb0

  • description changed.

i found the corresponding bug reports http://bugs.eclipse.org/240906 and http://bugs.eclipse.org/240744

10/12/08 13:25:21 changed by jstpierre@mecheye.net

This seems to be somewhat resolved in a "new update"

https://bugs.eclipse.org/bugs/show_bug.cgi?id=240906#c6

10/12/08 13:28:03 changed by jstpierre@mecheye.net

Just to clarify, the build is from August, but it was just recently rolled out. I haven't tested it yet though.

10/12/08 16:11:29 changed by mb0

2 days ago a new imp build arrived at the sourceforge update site. i failed to install it because of a missing jar, but i guess i can start to work with it this week.

10/12/08 16:18:53 changed by mb0

sorry for the duplication - the bugzilla request took very long. i try to install it right now.

10/12/08 16:37:23 changed by mb0

  • status changed from assigned to closed.
  • resolution set to fixed.

yay its working fine with axdt 0.0.5 and the newer imp build.