<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 02 Apr 2013, at 11:11, Marc Weustink wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">On 28-3-2013 17:52, Jonas Maebe wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">+= does *not* prevent re-evaluating the left side. It is internally<br></blockquote><blockquote type="cite">translated to "x:=x+y" and then evaluated like normal. So if "x"<br></blockquote><blockquote type="cite">contains a function call with side effects, these side effects are still<br></blockquote><blockquote type="cite">triggered twice.<br></blockquote><br>Is evaluated as x := x + y or as x := x + (y)<br></span></span></blockquote></div><br><div>FPC guarantees nothing about the order in which expressions are evaluated. FPC generally reorders expressions based on how many registers the compiler thinks it will need.</div><div><br></div><div><br></div><div>Jonas</div></body></html>