Eclipse Community Forums: TMF (Xtext) » DiagnosticMessage in LazyLinkingResource

Help

Home

Home » Modeling » TMF (Xtext) » DiagnosticMessage in LazyLinkingResource

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

DiagnosticMessage in LazyLinkingResource [message #640532]

Mon, 22 November 2010 12:51

Jan Ortmann

Messages: 7
Registered: November 2010

Junior Member

Hi all,

I noticed that removeDiagnosticMessage in LazyLinkingResource creates a DiagnosticMessage even if there is no error/warning in a document. Is this due to some wrong ScopeProvider-Implementation on my side or is it meant to be this way? As I try to give rather detailed feedback when a resource cannot be resolved (i.e. finding spelling errors), this slows down the building process significantly for me. I solved the issue by lazily creating the DiagnosticMessage text on a getMessage()-invocation. Yet I wondered if it wouldn't be more efficient to have a different implementation of removeDiagnostic in LazyLinkingResource.
Please let me know if 1) this should not occur and is most likely due to a wrong ScopeProvider-Implementation on my side or 2) you are going to change this in a future release.

Regards,

Jan

Report message to a moderator

Re: DiagnosticMessage in LazyLinkingResource [message #640777 is a reply to message #640532]

Tue, 23 November 2010 07:15

Sebastian Zarnekow

Messages: 3118
Registered: July 2009

Senior Member

Hi Jan,

it is not your fault. We create a message (and assume it is really cheap
to do so) to find previously generated diagnostics and remove them from
the respective error / warning lists. Did you face any runtime problems
with this approach?

Regards,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com

Am 22.11.10 13:51, schrieb Jan Ortmann:
> Hi all,
> I noticed that removeDiagnosticMessage in LazyLinkingResource creates a
> DiagnosticMessage even if there is no error/warning in a document. Is
> this due to some wrong ScopeProvider-Implementation on my side or is it
> meant to be this way? As I try to give rather detailed feedback when a
> resource cannot be resolved (i.e. finding spelling errors), this slows
> down the building process significantly for me. I solved the issue by
> lazily creating the DiagnosticMessage text on a getMessage()-invocation.
> Yet I wondered if it wouldn't be more efficient to have a different
> implementation of removeDiagnostic in LazyLinkingResource.
> Please let me know if 1) this should not occur and is most likely due to
> a wrong ScopeProvider-Implementation on my side or 2) you are going to
> change this in a future release.
>
> Regards,
> Jan

Report message to a moderator

Previous Topic:	Language mix-ins?
Next Topic:	Does Xtext support only context-free grammars?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 08:45:07 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter