It's worse than just the configuration file. In the middle of the 5.2.x development, they changed which value types automatically passed by reference -- in a security patch! 5.2.1 you can modify your arrays in place, 5.2.3 your code is broken. If you want to change the semantics of function calling, you should give the new version a new name; it's a new language. At the very least, you'd better give me a new major version or I'll stop using your platform. I've stopped using the platform.
(I know it was 5.x, it might have been 5.3-ish when all this happened. This rant is from memory. Consider this a pre-emptive [citation needed]. There's no way we were the only ones bitten by change.)
wmcliphist is a windowmaker dockapp that stores the last several X cuts. Doesn't solve the problem entirely, but it does make it easy to recover the last selection. Works well enough that I don't notice anymore.
You could pretty easily argue that SQL itself has the same tendencies to be exploitable as PHP. This might have been the point. If you ask me, a quoted-string interface to data storage is begging for trouble from the start. Buffers with byte counts would be better in many (I think most/all) ways.
Slashdot Mirror
It's worse than just the configuration file. In the middle of the 5.2.x development, they changed which value types automatically passed by reference -- in a security patch! 5.2.1 you can modify your arrays in place, 5.2.3 your code is broken. If you want to change the semantics of function calling, you should give the new version a new name; it's a new language. At the very least, you'd better give me a new major version or I'll stop using your platform. I've stopped using the platform.
(I know it was 5.x, it might have been 5.3-ish when all this happened. This rant is from memory. Consider this a pre-emptive [citation needed]. There's no way we were the only ones bitten by change.)
wmcliphist is a windowmaker dockapp that stores the last several X cuts. Doesn't solve the problem entirely, but it does make it easy to recover the last selection. Works well enough that I don't notice anymore.
You could pretty easily argue that SQL itself has the same tendencies to be exploitable as PHP. This might have been the point. If you ask me, a quoted-string interface to data storage is begging for trouble from the start. Buffers with byte counts would be better in many (I think most/all) ways.