ID: 40477 Updated by: [EMAIL PROTECTED] Reported By: piotrek dot pokora at gmail dot com -Status: Open +Status: Bogus Bug Type: Variables related Operating System: debian/linux PHP Version: 5.2.1 New Comment:
There is not bug and I asked you to discuss issues rising in custom PHP extensions in [EMAIL PROTECTED] Please subscribe to this list and lets discuss it there. Previous Comments: ------------------------------------------------------------------------ [2007-02-14 16:10:18] piotrek dot pokora at gmail dot com Sorry, changed summary by accident. ------------------------------------------------------------------------ [2007-02-14 16:08:03] piotrek dot pokora at gmail dot com > Again, please use pecl-dev, this is not a forum. http://pecl.php.net/bugs/ points directly to bugs.php.net. So I think I am at correct bugtracker. ------------------------------------------------------------------------ [2007-02-14 15:56:19] [EMAIL PROTECTED] Again, please use pecl-dev, this is not a forum. ------------------------------------------------------------------------ [2007-02-14 15:51:49] piotrek dot pokora at gmail dot com >Please use pecl-dev. Please, make this bug open for the sake of logic and consistency. I know how to write own get_properties hook. I know how to workaround this problem ( yes it's workaround now, ugly though ). I know what any php extension developer is able to tell me. It doesn't change the fact that print_r or var_dump doesn't respect object's read_property hook. It must be clear and clean that (pseudocode): if(zval.type == IS_OBJECT) zval.value.obj.handlers.read_property Will pecl-dev advice will fix this issue? No. Is there another zend bug tracker and pecl-dev will help me find it? Or should I prepare patch and send somewhere? ------------------------------------------------------------------------ [2007-02-14 15:33:25] [EMAIL PROTECTED] Please use pecl-dev. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/40477 -- Edit this bug report at http://bugs.php.net/?id=40477&edit=1
