[furcas-discussion] Question regarding re-use strategy for foreach-produced elements

Uhl, Axel axel.uhl at sap.com
Thu Feb 17 14:57:27 CET 2011


Follow-up question: Are transitive, nested foreach-executions all documented by correspondingly nested TextBlock instances? Probably something for our workshop where we discuss the future TextBlocks structures. Anybody have an idea right now?

-- Axel

> -----Original Message-----
> From: furcas-discussion-bounces at lists.furcas.org [mailto:furcas-
> discussion-bounces at lists.furcas.org] On Behalf Of Uhl, Axel
> Sent: Thursday, February 17, 2011 2:29 PM
> To: furcas-discussion
> Subject: [furcas-discussion] Question regarding re-use strategy for
> foreach-produced elements
> 
> Hi,
> 
> DelayedReferencesHelper.setReference(...) seems to implement some sort
> of re-use strategy for the elements produced by a foreach predicate. It
> uses a reusableResultElement obtained from a map earlier produced by
> setDelayedReferenceWithPredicate(...). The re-use is decided based upon
> whether the template found for producing the new element has a
> metaReference pointing to the class that is the type of the existing
> element.
> 
> What does it mean for such an element to be re-used instead of
> producing a new one? I would assume that there is a TextBlock that
> documents the execution of the old template used for the element's
> production. This, however, could be one that---while for the same
> class---uses a different mode and therefore entirely different property
> inits.
> 
> I can't find the code that would update the TextBlocks hierarchy in
> case of such a re-use across differently-moded templates being used.
> Bug?
> 
> Best,
> -- Axel
> _______________________________________________
> Furcas-discussion mailing list
> Furcas-discussion at lists.furcas.org
> http://lists.furcas.org/cgi-bin/mailman/listinfo/furcas-discussion


More information about the Furcas-discussion mailing list