|Re: Validating JvmType imports [message #841552 is a reply to message #840798]
||Wed, 11 April 2012 13:03
| Sebastian Zarnekow
Registered: July 2009
it will become public API as soon as we have the feeling that it's
mature enough. We don't have the resources to maintain poorly designed
APIs and apply deprecation strategies thus we warn clients that the
referenced code may change.
What you consider pretty stable is not necessarily stable from our
perspective, e.g. the resource set may be a to broad context for the
lookup environment of a type (which indeed it is).
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 10.04.12 16:21, schrieb Aaron Digulla:
> Karsten Thoms wrote on Fri, 06 April 2012 14:55
>> You can add @SuppressWarnings("restriction")
>> to your class.
> Well, yes but I was rised to pay heed to warnings ;)
> My main complaint is that I must add the annotation to the class
> (because I also get warnings for the imports), so the scope of the
> annotation to too broad for my liking.
> Okay, I can work around this by not using imports but FQ names but,
> well, it would be better if Xtext would offer an official API for this.
> I think that many DSLs need to interface Java code and the API to check
> imports and type names should be pretty stable.
Powered by FUDForum
. Page generated in 0.06011 seconds