Execution order

[Jay Ashworth]

----- Original Message -----
> From: "Kenneth Brody" <kenbrody at spamcop.net>

> On 3/24/2014 12:44 PM, Jay Ashworth wrote:
> > Filepro doesn't do any optimizations that break execution order,
> > right?
> >
> > ::ns=ctl(1); ctl(1)=ns+"1":
> >
> > is going to do what I so clearly expect, right?
> 
> You will always end up with ns being the current value of ctl(1), and
> then
> ctl(1) will be incremented -- the C equivalent of "ns = ctl[1]++;".
> 
> Assuming that that's what you expect, then yes, it will do what you
> expect. :-)

It was, in actual fact, what I expected.  

> Any optimizer that would change that would be "broken".

What I would think, but it's my understanding that there exist optimizers
that do that which are not considered broken.

You can understand why I'd have a hard time googling up the details.  :-)

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates       http://www.bcp38.info          2000 Land Rover DII
St Petersburg FL USA      BCP38: Ask For It By Name!           +1 727 647 1274