Eclipse Community Forums: Dynamic Languages Toolkit (DLTK) » Tracking parsing/semantic errors/warnings (problems)

Help

Home

Home » Eclipse Projects » Dynamic Languages Toolkit (DLTK) » Tracking parsing/semantic errors/warnings (problems)

Show: Today's Messages :: Show Polls :: Message Navigator

Tracking parsing/semantic errors/warnings (problems) [message #28073]

Fri, 11 July 2008 15:10

Charles Doucette

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

Report message to a moderator

Re: Tracking parsing/semantic errors/warnings (problems) [message #28379 is a reply to message #28073]

Mon, 14 July 2008 05:22

Alex Panchenko

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
>
>

Report message to a moderator

Previous Topic:	Accessing org.eclipse.dltk.tcl.ui.editor.TclEditor
Next Topic:	problem markers

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Jul 27 01:29:57 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter