Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33172
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender)
Message-ID: <473D56C4.4060600@daylessday.org>
Date: Fri, 16 Nov 2007 11:37:24 +0300
User-Agent: Thunderbird 2.0.0.6 (X11/20070801)
MIME-Version: 1.0
To: Stanislav Malyshev <stas@zend.com>
CC: Steph Fox <steph@zend.com>, internals <internals@lists.php.net>, 
 Elizabeth Smith <emsmith@elizabethmariesmith.com>
References: <015f01c827e0$0a3b38b0$e6dfc350@foxbox> <473D5453.3060402@zend.com>
In-Reply-To: <473D5453.3060402@zend.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC Making compiler info accessible
From: tony@daylessday.org (Antony Dovgal)

On 16.11.2007 11:26, Stanislav Malyshev wrote:
>> logistics, and then it struck me that it might be useful for _everybody_ 
>> to have compiler info (make/version) as part of the string returned from 
>> php -v, probably alongside the build date. We could then sanely ask for 
>> that information as part of PHP bug reports.
> 
> I don't think it belongs to php -v, but to phpinfo(). There's a lot of 
> useful stuff you can know about PHP build, and it almost all is in 
> phpinfo().

Yes, phpinfo() seems to be the best place for such info.

-- 
Wbr, 
Antony Dovgal