SAPI_API glitch
| From: | Daniel Beulshausen | Date: | Wed, 15 Aug 2001 14:58:17 +0000 |
| Subject: | SAPI_API glitch | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-63283@lists.php.net to get a copy of this message | ||
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