Comments on: PHP5 Object Oriented Properties - Tested! http://www.102degrees.com/blog/2007/06/21/php5-object-oriented-properties-tested/ Web Programming and Design by Aaron Saray Fri, 05 Dec 2008 12:09:52 +0000 http://wordpress.org/?v=2.6.3 By: Todd http://www.102degrees.com/blog/2007/06/21/php5-object-oriented-properties-tested/#comment-703 Todd Thu, 12 Jun 2008 22:21:13 +0000 http://www.102degrees.com/blog/2007/06/21/php5-object-oriented-properties-tested/#comment-703 Update: This bug has been fixed in CVS. http://bugs.php.net/bug.php?id=44769 Fixed in 5_3 and HEAD. Update: This bug has been fixed in CVS.
http://bugs.php.net/bug.php?id=44769

Fixed in 5_3 and HEAD.

]]> By: Todd http://www.102degrees.com/blog/2007/06/21/php5-object-oriented-properties-tested/#comment-307 Todd Thu, 17 Apr 2008 20:38:14 +0000 http://www.102degrees.com/blog/2007/06/21/php5-object-oriented-properties-tested/#comment-307 Actually, you may have discovered a bug here. I tested the code again to test a private __set method in PHP 5.2.5. First, according to the PHP manual page on OOP5 overloading: http://us.php.net/manual/en/language.oop5.overloading.php "All overloading methods must be defined as public." I would think that by attempting to define the __set magic method as private you should send the parser into an error state and at the very least throw a warning. Actually, you may have discovered a bug here. I tested the code again to test a private __set method in PHP 5.2.5. First, according to the PHP manual page on OOP5 overloading:
http://us.php.net/manual/en/language.oop5.overloading.php

“All overloading methods must be defined as public.”

I would think that by attempting to define the __set magic method as private you should send the parser into an error state and at the very least throw a warning.

]]>