At 18:20 15.08.2001 +0300, Zeev Suraski wrote:
>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)

not sure, but we can add it later if it breaks :)


>At 17:58 15-08-01, Daniel Beulshausen wrote:
>>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 beulshausen - [EMAIL PROTECTED]
>>using php on windows?
>>PHP Development Mailing List <>
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>To contact the list administrators, e-mail: [EMAIL PROTECTED]
>Zeev Suraski <[EMAIL PROTECTED]>
>CTO &  co-founder, Zend Technologies Ltd.

daniel beulshausen - [EMAIL PROTECTED]
using php on windows?

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to