Hi Stas:
> I'm sorry that influences you code, it is unfortunate, but relying
> on an obscure bug, however convenient, is not a good practice.
Please don't put this on me. It's not about me. It's about many, many
developers who have this usage in many places. This change will open up
many unexpected, hard-to-track-down, bugs (and possible security holes)
all over the place.
> I'm sorry but it's too late for big additions in 5.4, such as
> introducing new warnings or new semantics.
Adding a notice is possible. The whole point of release candidates is
to find edge case problems in the wild that developers didn't expect.
I found one. Now let's do something about it.
Don't we want people to upgrade to 5.4? If so, we should not place
hidden trapping pits that will end up swallowing and injuring our users.
Sincerely,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
