Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Dynamic Languages Toolkit (DLTK) » Tracking parsing/semantic errors/warnings (problems)
Tracking parsing/semantic errors/warnings (problems) [message #28073] Fri, 11 July 2008 15:10 Go to next message
Charles Doucette is currently offline Charles DoucetteFriend
Messages: 125
Registered: July 2009
Senior Member
Is there a way to track whether a module has any problems,
whether they be:
a) errors/warnings
b) from parsing/semantic-checking?

I thought I saw something in the DLTK core code to track parsing errors -
but I can't find it.
We can't easily extend SourceModule - but I can extend ModuleDeclaration if
that is appropriate.

Chuck
Re: Tracking parsing/semantic errors/warnings (problems) [message #28379 is a reply to message #28073] Mon, 14 July 2008 05:22 Go to previous message
Alex Panchenko is currently offline Alex PanchenkoFriend
Messages: 342
Registered: July 2009
Senior Member
Hi Chuck,

Problems are persisted as markers, so

IMarker[] markers = resource.findMarkers(IMarker.PROBLEM, true,
IResource.DEPTH_INFINITE);

after that you can check severity of markers if needed.

Regards,
Alex


Chuck Doucette wrote:
> Is there a way to track whether a module has any problems,
> whether they be:
> a) errors/warnings
> b) from parsing/semantic-checking?
>
> I thought I saw something in the DLTK core code to track parsing errors -
> but I can't find it.
> We can't easily extend SourceModule - but I can extend ModuleDeclaration if
> that is appropriate.
>
> Chuck
>
>
Previous Topic:Accessing org.eclipse.dltk.tcl.ui.editor.TclEditor
Next Topic:problem markers
Goto Forum:
  


Current Time: Fri Apr 12 17:12:02 GMT 2024

Powered by FUDForum. Page generated in 0.02972 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top