|
Re: EOL fully qualified name [message #1834833 is a reply to message #1834830] |
Wed, 18 November 2020 18:10 |
Alfonso de la Vega Messages: 18 Registered: January 2016 |
Junior Member |
|
|
Hello Ludovico,
As others have suggested in the past [1], avoiding having several packages in the same metamodel can prevent the apparition of bugs with existing tools (I guess that can be extended for having EClasses with the same name!).
If you currently cannot avoid that metamodel structure, you can use "::" separators to specify a fully qualified name including all nested packages (e.g. "p::p1::A").
I have put together an example in the newly available playground for Epsilon [2] (thank you for any feedback on that!). In my case, the second query (all instances of type "A", unqualified) only shows instances of the first A class found in the metamodel, instead of showing all of them. When using the qualifiers you can get the instances of the precise type you are interested in.
Regards,
Alfonso
[1] https://eclipsesource.com/blogs/2013/03/19/emf-dos-and-donts-5/
[2] https://bit.ly/3pHQgvu
[Updated on: Wed, 18 November 2020 19:52] by Moderator Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.04813 seconds