Re: SAPI_API glitch
| From: | Zeev Suraski | Date: | Wed, 15 Aug 2001 15:20:02 +0000 |
| Subject: | Re: SAPI_API glitch | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-63288@lists.php.net to get a copy of this message | ||
Is there any reason to have them even exported? I think we can just nuke SAPI_API altogether (I could be wrong, we might be referencing them somewhere, but I don't think we do)
At 17:58 15-08-01, Daniel Beulshausen wrote:
hi currently if extensions want to define their own SAPI_POST_*_FUNC (fdf, mbstring) they'll run into trouble, because they are defined as 'SAPI_API void ... my_handler'. this however doesn't work, because you'll need to define SAPI_EXPORTS (to export it) and are thus loosing the sapi_globals_id (which must be imported). nuking SAPI_API from the macro, and using (SAPI_API || PHP_EXT_API) SAPI_POST_*_FUNC would avoid this glitch. anyone objects? daniel /*-- daniel beulshausen - daniel@php4win.de using php on windows? http://www.php4win.de -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/