Re: Bug #1452 Updated: $i = $i++ fails

On May 25, Colin Putney wrote: > My question was not entirely rhetorical. Is there a reason to choose the > current behaviour (which is counter-intuitive and can lead to bugs in > programs which are not well written) over the alternative (where PHP > behaves as expected)? You're making the strong assertions that the behavior you describe is "expected" and "intuitive". The construct we're talking about doesn't lead to bugs because of how PHP evaluates it, it IS a bug. I see no reason to pin down a defined behavior since if anything is obvious, it is that the construct is completely bogus, and to define its behavior limits future opportunities for possible code optimization. Of course, Zeev is the one you have to convince, not me. :) Jim -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net