Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [incquery-dev] eclipsecon example

Dynamic case: I have access to the features themselves in the IncQueryXcoreEcoreBuilder class when for example the annotation is created. I think the registration would be fine here, however, this registration would hold a strong reference in the Registry to the feature. (Every time the xcore is modified a new feature will be created) Is it safe to modify the Registry to use some weak collection?

Generated case: from the documentation: " extend the org.eclipse.incquery.runtime.base.wellbehaving.derived.features extension point as described here" I think a link is missing at "here"

Go ahead, thanks

On Wednesday, October 23, 2013, Tamas Szabo wrote:
Hi

If nobody has started to deal with this issue then I can fix this thing today.

Cheers,
Tamas
I should have recognised the symptoms (QBF inside query doesn't work) earlier, but you shouldn't have ignored that warning all the way until now :)

The engine will not traverse a feature when building the pattern matchers if it is not well-behaving, e.g. derived. However, you can specify that a given feature is well-behaving through the WellBehavingDerivedFeatureRegistry (catchy name, huh?). This is actually documented here: http://wiki.eclipse.org/EMFIncQuery/UserDocumentation/Query_Based_Features#Well-behaving_structural_features

In the dynamic case: use the register method at some point, before engine initialisation
In the generated case: put the proper extension into the plugin.xml, this was done by the @QueryBasedFeature code generator, I haven't thought that you forgot to do that.

Cheers,
   Ábel Hegedüs

Fault Tolerant Systems Research Group
Department of Measurement and Information Systems
Budapest University of Technology and Economics


On 22 October 2013 23:44, Istvan Rath <rath@xxxxxxxxxx> wrote:
Two more notes:
- this behavior is observed with the Query Explorer as well as the QBF on the Properties View
- this behavior is observed with the generated domain editor, meaning it probably has nothing to do with our recent code change to avoid using the QuerySpec registry

--
Istvan RATH, PhD
Research fellow
Budapest University of Technology and Economics
Fault Tolerant Systems Research Group

On Tuesday, October 22, 2013 at 11:20 PM, Istvan Rath wrote:

Just to entertain everyone, it seems we've been happy too early to declare that using QBFs inside QBFs work.

@QueryExplorer(display = true)

pattern weirdBook3(B : Book) {

Book.allCitations(B, B); // doesn't work



--
Istvan RATH, PhD
Research fellow
Budapest University of Technology and Economics
Fault Tolerant Systems Research Group



_______________________________________________
incquery-dev mailing list
incquery-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/incquery-dev


-- 
Tamas Szabo
Software engineer

Tel.:   +49 711 342 191 0
Fax.:   +49 711 342 191 29
Mobil:  +49 171 565 416 9
Web:    www.itemis.de
Mail:   tamas.szabo@xxxxxxxxx
Skype:  szabta89

itemis AG
Niederlassung Süd
Meitnerstr. 10
70563 Stuttgart

Rechtlicher Hinweis:
Registergericht: Amtsgericht Dortmund HRB 20621 | Sitz der Gesellschaft:
Lünen
Vorstand: Jens Wagener (Vorsitzender) | Wolfgang Neuhaus | Dr. Georg
Pietrek | Jens Trompeter | Sebastian Neus
Aufsichtsrat: Prof. Dr. Burkhard Igel (Vorsitzender) | Stephan Grollmann
| Michael Neuhaus

Back to the top