[furcas-discussion] Bug in DelayedReferencesHelper.setDelayedReferenceWithPredicate

Thomas Goldschmidt thomas.goldschmidt at de.abb.com
Thu Feb 17 08:24:48 CET 2011


Hi Axel,

does this also have to do with the previous ordering issue you 
encountered?

Cheers,
Thomas


 
Thomas Goldschmidt 

ABB AG
Forschungszentrum
Wallstadter Straße 59
68526 Ladenburg
Office Phone: +49 6203 716134
Office Fax: +49 6203 716253
e-mail: thomas.goldschmidt at de.abb.com

ABB AG
Sitz/Head Office: Mannheim 
Registergericht/Registry Court: Mannheim
Handelsregisternummer/Commercial Register No.: HRB 4664
Geschäftsführung/Managing Board: Peter Smits (Vorsitzender), Joachim 
Schneider, Markus Ochsner, Hans-Georg Krabbe
Vorsitzender des Aufsichtsrats/Chairman of Supervisory Board: Bernhard 
Jucker

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. 

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.



"Uhl, Axel" <axel.uhl at sap.com> 
Sent by: furcas-discussion-bounces at lists.furcas.org
16.02.2011 23:13

To
furcas-discussion <furcas-discussion at lists.furcas.org>
cc

Subject
[furcas-discussion] Bug in 
DelayedReferencesHelper.setDelayedReferenceWithPredicate






Hi,

I found a bug that I need to fix urgently. When there is more than one 
element resulting from the foreach expression, and the parser runs with 
TextBlocks creation (which is not the case for the barebones tests), only 
one target element will reside in the feature to be filled by the foreach 
predicate. The problem is an erroneous nesting of the textblocks / 
elements re-use strategy inside the loop over the foreach evaluation 
results.

My strategy which I hopefully get implemented tomorrow is to first compute 
the replacement elements and then, in one go, update the feature and the 
textblocks information at once.

Until then don't expect foreach to work for more than one foreach result 
when textblocks creation is active in the parser.

Best,
-- Axel
_______________________________________________
Furcas-discussion mailing list
Furcas-discussion at lists.furcas.org
http://lists.furcas.org/cgi-bin/mailman/listinfo/furcas-discussion

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.furcas.org/pipermail/furcas-discussion/attachments/20110217/f46ccc1e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 454 bytes
Desc: not available
URL: <http://lists.furcas.org/pipermail/furcas-discussion/attachments/20110217/f46ccc1e/attachment.gif>


More information about the Furcas-discussion mailing list