Re: argv/argc
| From: | Zeev Suraski | Date: | Fri, 28 Jan 2000 17:56:04 +0000 |
| Subject: | Re: argv/argc | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-14993@lists.php.net to get a copy of this message | ||
On Fri, 28 Jan 2000 rasmus@php.net wrote:
> > > Are there always supposed to be registered? That looks like an awful
> > > waste of time in most cases...?
> >
> > They should be registered for cgi SAPI.
>
> They should also be there for the module versions. This lets you take a
> URL of the form:
>
> http://www.php.net/?blah
What do you mean by 'it lets you take it'...?
My understanding, based on the ad-hoc statistics generator, is that most
scripts don't use argc/argv, and there are probably whole sites that don't
use it. Still, there's no way to let PHP know it's not necessary for it
to set them up...
> Would checking if there is any query data before registering these speed
> things up?
It would in this specific case, but I think that if people expect
argv/argc, they expect them to exist and be empty in case of an empty
query.
Any reason not to selectively turn argv/argc off by an INI directive?
Zeev
--
Zeev Suraski <zeev@zend.com>
http://www.zend.com/