[furcas-discussion] [IMP] Incremental Lexer Crashes]

[Uhl, Axel]

I see. Please also note that the way in which EcoreUtil.delete works, it may register a new cross reference adapter each time a delete occurs. This is inefficient and largely incorrect because it only sees the resources already loaded into the resource set.

If you really want to reliably delete all references (do you?), consider using the OppositeEndFinder for any reverse navigation because we then have the option to back it with query2 if needed/desired.

Best,
-- Axel

> -----Original Message-----
> From: furcas-discussion-bounces at lists.furcas.org [mailto:furcas-
> discussion-bounces at lists.furcas.org] On Behalf Of Stephan Erb
> Sent: Friday, February 11, 2011 3:40 PM
> To: furcas-discussion
> Subject: [furcas-discussion] [IMP] Incremental Lexer Crashes]
> 
> 
> > Did I miss something? Which of the horrible EMF element lifecycle
> > aspects was at fault and how?
> 
> Well, we maintain three versions of a TextBlocks model. Each
> DocumentNode in one of these versions references its two counterparts
> in
> the other versions.
> 
> In MOIN we simply used to recursively delete one version of the model.
> In EMF delete only removes from the composite parent. Thus, for a full
> delete of a version of the TextBlocks model, we also have to walk all
> other versions and delete the references to the version that we want to
> delete.
> 
> Ugly :-)
> 
> 
> 
> 
> 
> _______________________________________________
> Furcas-discussion mailing list
> Furcas-discussion at lists.furcas.org
> http://lists.furcas.org/cgi-bin/mailman/listinfo/furcas-discussion