I can feel you regarding your offtopic comments regarding why core developpers step up and leave the project. So much about that.
But let's get back to the topic. The existance of suhosin itself addresses the ignorance of the current team. They've been told about issues for many years, PHP is used by a large userbase on the net, and they have to install an addon/plugin/whatever because the devs won't fix known issues.
Especially in this age, security and reliability is key. Period.
So, instead of extending php with features, maybe it's time to put them on a pile of todo and fix issues first before introducing this new features, or the community might start to turn their backs on php and switch to a language that does not have these issues.
Manuel Lemos - 2012-02-04 02:12:45 - In reply to message 3 from Alexander Maassen
Actually it seems to be only when you have memory canary options set. These seem to be to verify if memory allocated by PHP is being used beyhond the allocated space due to eventual PHP bugs or security exploit attempts.
These would not be necessary if there are no memory usage bugs, but we never know that because there are no bug free programs.