Re: Re: cvs: php4 /sapi/cgi cgi_main.c /sapi/cli php_cli.c
| From: | Dan Kalowsky | Date: | Sat, 11 May 2002 04:33:21 +0000 |
| Subject: | Re: Re: cvs: php4 /sapi/cgi cgi_main.c /sapi/cli php_cli.c | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-83895@lists.php.net to get a copy of this message | ||
On Sat, 11 May 2002, Markus Fischer wrote:
>
> $ php -v
> PHP 4.3.0-dev (cli)
> Zend Engine v1.2.1, Copyright (c) 1998-2002 Zend Technologies
> PHP_VERSION_API 20020510
> ZEND_EXTENSION_API_NO 20020510
> ZEND_MODULE_API_NO 20020510
While this may look ugly, I'd say stick with this option. It's more of an
understood standard for all end users. But I question what use
PHP_VERSION_API, ZEND_EXTENSION_API_NO, and ZEND_MODULE_API_NO are going
to be for anyone outside of PHP language developers. Is it possible to
have multiple versions (i.e. ZEND_MODULE_API_NO) per release? Consdering
most (if not all) all endusers will be using a release version, this may
be a case of too much useless information.
> $ php -vv
> PHP 4.3.0-dev (cli)
> Zend Engine v1.2.1, Copyright (c) 1998-2002 Zend Technologies
> PHP_VERSION_API 20020510
> ZEND_EXTENSION_API_NO 20020510
> ZEND_MODULE_API_NO 20020510
>
> Or is this just unnecessary bloat and let's fire all versions
> we have to standard output with -v ?
This just looks bad. What is -vv? It really doesn't follow any standard
options for people.
-1 to the -vv option.
>---------------------------------------------------------------<
Dan Kalowsky "The record shows, I took the blows.
http://www.deadmime.org/~dank And did it my way."
dank@nospam-deadmime.org - "My Way", Frank Sinatra
kalowsky@nospam-php.net