<br><tt><font size=2>>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?</font></tt>
<br>
<br><tt><font size=2>As far as I know this should be handled by </font></tt><font size=2 face="Courier New"><u>DelayedReferencesHelper::setDelayedReferenceWithPredicate</u></font><tt><font size=2>().
Thus leaving only one TestBlock for the part that has still a syntax contribution
and adding all other elements as </font></tt><font size=2 face="Courier New"><u>ForEachContext</u></font><tt><font size=2>
elements. However, I remember that we recently identified an issue with
this already. I would leave this for our upcoming discussion.<br>
</font></tt><font size=2 face="sans-serif"><br>
</font>
<table>
<tr>
<td valign=top><img src=cid:_1_0C6A00E40C25CBA0004F0114C125783A>
<td><font size=3> </font>
<td><font size=1 face="Verdana"><b>Thomas Goldschmidt </b><br>
<br>
ABB AG<br>
Forschungszentrum<br>
Wallstadter Straße 59<br>
68526 Ladenburg<br>
Office Phone: +49 6203 716134<br>
Office Fax: +49 6203 716253<br>
e-mail:</font><font size=1 color=blue face="Verdana"> thomas.goldschmidt@de.abb.com</font></table>
<br>
<br><font size=1 color=#808080 face="Verdana">ABB AG<br>
Sitz/Head Office: Mannheim <br>
Registergericht/Registry Court: Mannheim<br>
Handelsregisternummer/Commercial Register No.: HRB 4664<br>
Geschäftsführung/Managing Board: Peter Smits (Vorsitzender), Joachim Schneider,
Markus Ochsner, Hans-Georg Krabbe<br>
Vorsitzender des Aufsichtsrats/Chairman of Supervisory Board: Bernhard
Jucker<br>
<br>
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
erhalten haben, informieren Sie bitte sofort den Absender und vernichten
Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe
dieser Mail ist nicht gestattet. <br>
<br>
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Uhl, Axel" <axel.uhl@sap.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: furcas-discussion-bounces@lists.furcas.org</font>
<p><font size=1 face="sans-serif">17.02.2011 14:57</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">furcas-discussion <furcas-discussion@lists.furcas.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [furcas-discussion] Question regarding
re-use strategy for
foreach-produced elements</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>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?<br>
<br>
-- Axel<br>
<br>
> -----Original Message-----<br>
> From: furcas-discussion-bounces@lists.furcas.org [mailto:furcas-<br>
> discussion-bounces@lists.furcas.org] On Behalf Of Uhl, Axel<br>
> Sent: Thursday, February 17, 2011 2:29 PM<br>
> To: furcas-discussion<br>
> Subject: [furcas-discussion] Question regarding re-use strategy for<br>
> foreach-produced elements<br>
> <br>
> Hi,<br>
> <br>
> DelayedReferencesHelper.setReference(...) seems to implement some
sort<br>
> of re-use strategy for the elements produced by a foreach predicate.
It<br>
> uses a reusableResultElement obtained from a map earlier produced
by<br>
> setDelayedReferenceWithPredicate(...). The re-use is decided based
upon<br>
> whether the template found for producing the new element has a<br>
> metaReference pointing to the class that is the type of the existing<br>
> element.<br>
> <br>
> What does it mean for such an element to be re-used instead of<br>
> producing a new one? I would assume that there is a TextBlock that<br>
> documents the execution of the old template used for the element's<br>
> production. This, however, could be one that---while for the same<br>
> class---uses a different mode and therefore entirely different property<br>
> inits.<br>
> <br>
> I can't find the code that would update the TextBlocks hierarchy in<br>
> case of such a re-use across differently-moded templates being used.<br>
> Bug?<br>
> <br>
> Best,<br>
> -- Axel<br>
> _______________________________________________<br>
> Furcas-discussion mailing list<br>
> Furcas-discussion@lists.furcas.org<br>
> </font></tt><a href="http://lists.furcas.org/cgi-bin/mailman/listinfo/furcas-discussion"><tt><font size=2>http://lists.furcas.org/cgi-bin/mailman/listinfo/furcas-discussion<br>
_______________________________________________<br>
Furcas-discussion mailing list<br>
Furcas-discussion@lists.furcas.org<br>
</font></tt><a href="http://lists.furcas.org/cgi-bin/mailman/listinfo/furcas-discussion"><tt><font size=2>http://lists.furcas.org/cgi-bin/mailman/listinfo/furcas-discussion<br>
</font></tt></a></a>
<br>