"Andrei Zmievski" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Yes, this is pretty high impact as far as code changes are concerned. > Since one should not attempt to access a class entry without > U_CLASS_ENTRY() macro, should it even be optional? my uneasiness with this is that if the macro is mandatory, it (to me) implies, from a usability point of view, that that zend_parse_parameters, instanceof_functions etc are now "broken". z_p_p, for example, was a god-send, because it took care of all the lifting, without reminding me of implementation details. now everytime i use it with objects, im forced to think of whether or not i'm in unicode mode, when i neither knew or cared about such things when the class_entry was created.
i really think the macro should be moved to the appropriate functions. clayton -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
