Re: SAPI_API glitch

From:	Zeev Suraski	Date:	Wed, 15 Aug 2001 17:23:03 +0000
Subject:	Re: SAPI_API glitch
References:	1 2 3 4 5	Groups:	php.dev
Request:	Send a blank email to php-dev+get-63305@lists.php.net to get a copy of this message

At 20:20 15-08-01, Daniel Beulshausen wrote:

At 19:33 15.08.2001 +0300, Zeev Suraski wrote:
At 18:40 15-08-01, Daniel Beulshausen wrote:
At 17:36 15.08.2001 +0200, Daniel Beulshausen wrote:
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 :)
no i just looked, they are (i.e. sapi_read_standard_form_data in the fdf extension)
They are what? :)
breaking && using exported SAPI_POST_* functions. i conclude, they still should get exported. :)

Why? Are modules using any SAPI_POST functions which are defined in PHP? If they are, we should probably change the SAPI_POST_HANDLER definition not to include SAPI_API, and add the SAPI_API explicitly before those functions which are referenced by modules. Zeev