Posted Apr 18, 2012 19:07 UTC (Wed) by jthill
In reply to: Not Again
Parent article: PHP: a fractal of bad design (fuzzy notepad)
From the standpoint of software maintenance I'll argue that's a good thing: when you're changing code, the single most critical question you can ask is "is this change safe?". In common cases leaving expression-evaluation order unspecified when the math doesn't require it limits the spelunking necessary to answer that question to the code in front of you.
Or, shorter: relying on undocumented API implementation details and unnecessarily specifying implementation details both produce bad, fragile code.
to post comments)