On Mon, May 15, 2006 2:47 pm, Marcus Boerger wrote: >> [...] Is there a significant performance >> enhancement in the engine that depends on eliminating semi-static >> or somesuch? > > Security. We might as well enable the crash function in non debug > builds. > Or just drop 'static' again and go back to the PHP 4 object model.
I realize I'm the village idiot here, but... How does throwing, say, E_NOTICE or E_OOP_PURIST or something instead of E_FATAL when the programmer does this, turn into a crashing security issue? While encapsulation can be an important component of data-integrity and security in an application's OOP model, I'm just not seeing this as a general security flaw that should halt somebody's program because they prefer a looser encapsulation model in their OOP... Am I being particularly naive or blind here? If so, could you elaborate on how this is a Security concern, and equates with a crash function in non debug builds? Much less regressing to the inherently flawed PHP4 OOP model? If you're sure I'm the only idiot not getting this, feel free to point me to references or reply off-list or just ignore me, as I know you're crazy busy. :-) -- Like Music? http://l-i-e.com/artists.htm -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
