Re: Re: PHP 4.0 Bug #5882 Updated: Use inline directive in *.c files for global functions in Zend engine
| From: | Andi Gutmans | Date: | Wed, 16 Aug 2000 04:20:05 +0000 |
| Subject: | Re: Re: PHP 4.0 Bug #5882 Updated: Use inline directive in *.c files for global functions in Zend engine | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-29090@lists.php.net to get a copy of this message | ||
At 01:02 AM 8/16/00 +0200, Sascha Schumann wrote:
Wait, before applying that patch I would like to understand what's happening here. In gcc the previous way works, right? In C99, if you put the extern keyword it still won't inline those functions right? If they are moved to an .h file then gcc will probably complain about multiple declerations? If all of the above is true, maybe these inline functions should be moved to an .h file which we'll #include in zend_gcc_inline.c? Damn, it used to be C++ which wasn't standardized enough and now C is being attacked. Although maybe some of the changes are good it's quite annoying. Andi --- Andi Gutmans <andi@zend.com> http://www.zend.com/I still don't get why some compilers regard inline as macro. Ifthere's no"static", function should be in symbol table, not?Does anyone have access to ISO 9899:1999?Finally. ANSI sells the standard in electronic form for 18 bucks.C99 wants us to add the 'extern' keyword in the function declarations. Otherwise, no external linkage will be created (because these are auxiliary inline functions).Patch: http://toye.php.net/~sas/extern-inline-patchMaxim, please let me know whether it works for you.