Hi all,
This is just a suggestion at this stage, I'd like to test the waters with it
before writing a patch.
Apropos the VS discussion, I was thinking about suffixing the PHP version
number in these 'beta builds', to help with the ensuing QA 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.
The MS compiler version is transparently available to the source code, so it
wouldn't be difficult to make the information available in the resulting PHP
binary. (It's also available to our MS build system[*].) I know rather less
about the situation with compilers on other platforms though...?
Comments? Particularly, does anyone actually use php -v output in their
scripting in a way that would make this a bad idea all round?
- Steph
[*] The build system currently appears to be using that info for BC
workarounds, among other things. Elizabeth, if you're reading this please be
aware that it needs a little investigation.
I think it's a good idea and would be useful in unix-world too (we
have a hell-lot of compilers and versions these days)
Hi all,
This is just a suggestion at this stage, I'd like to test the waters with it
before writing a patch.Apropos the VS discussion, I was thinking about suffixing the PHP version
number in these 'beta builds', to help with the ensuing QA 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.The MS compiler version is transparently available to the source code, so it
wouldn't be difficult to make the information available in the resulting PHP
binary. (It's also available to our MS build system[*].) I know rather less
about the situation with compilers on other platforms though...?Comments? Particularly, does anyone actually use php -v output in their
scripting in a way that would make this a bad idea all round?
- Steph
[*] The build system currently appears to be using that info for BC
workarounds, among other things. Elizabeth, if you're reading this please be
aware that it needs a little investigation.--
--
Alexey Zakhlestin
http://blog.milkfarmsoft.com/
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().
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com
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
Hello Stanislav,
same here. Especially since phpinfo can be accessed very easy from command
line too: php -i
marcus
Friday, November 16, 2007, 9:26:59 AM, you 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().Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com
Best regards,
Marcus