Re: function proposal - php_check_syntax_string

Hi all, Val is right with define. but i have unexpected result when: 1 - redeclare existing function in main code-> end after function call 2 - redefine __autoload -> same 3 - redeclare function in test code -> same i think that's due fatal error as Andi say "some of the engine internals can be left in an unstable state after a fatal error" cause exit. redefine a class works even if it's destroyed during clean up (?) here test, output and new diff ( no cleanup after parse error) http://php-dev.burnweb.net. finally, i can avoid exit with zend_try but 1 - segfault with cleanup method after fatal error from test code 2 - declared class are registered with swapping method ( i'm not sure that i do the right thing for Alan's idea. any suggestion ?) perhaps, use an alternative simple scanner like PHP_Parser would be a reasonable solution fred ----- Original Message ----- From: "Marcus Boerger" <helly@php.net> To: "val khokhlov" <val@vk.kiev.ua> Cc: <internals@lists.php.net> Sent: Sunday, February 20, 2005 6:05 PM Subject: Re: [PHP-DEV] function proposal - php_check_syntax_string | Hello val, | | Sunday, February 20, 2005, 5:59:21 PM, you wrote: | | > Hello Marcus, | | > Sunday, February 20, 2005, 6:32:57 AM, you wrote: | | MB>> what happend to defines (when redefining) | > define() is called at run-time, as far as i saw, so there should be no | > problems with it | | MB>> and what happens to __autoload()? | > well, i never used it myself, so i've never tested bcompiler with this | > feature (and apc developers haven't too). maybe zend developers will comment on | > __autoload - if this feature is compile-time or run-time? (seems that it's | > run-time only, so it shouldn't cause a crash) | | | Even though it is run-time only, the point is that the pointers are set | during compile time. | | | -- | Best regards, | Marcus mailto:helly@php.net | | -- | PHP Internals - PHP Runtime Development Mailing List | To unsubscribe, visit: http://www.php.net/unsub.php |