Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46228 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45894 invoked from network); 29 Nov 2009 12:19:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Nov 2009 12:19:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=jess@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=jess@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.185 as permitted sender) X-PHP-List-Original-Sender: jess@zend.com X-Host-Fingerprint: 212.25.124.185 il-mr1.zend.com Received: from [212.25.124.185] ([212.25.124.185:54732] helo=il-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 36/CD-44817-4E6621B4 for ; Sun, 29 Nov 2009 07:19:50 -0500 Received: from il-gw1.zend.com (unknown [10.1.1.21]) by il-mr1.zend.com (Postfix) with ESMTP id 5567650476; Sun, 29 Nov 2009 14:06:16 +0200 (IST) Received: from [10.1.2.102] ([10.1.2.102]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 29 Nov 2009 14:19:45 +0200 Message-ID: <4B1266E0.7010405@zend.com> Date: Sun, 29 Nov 2009 14:19:44 +0200 User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: Pierre Joye CC: jvlad , internals@lists.php.net References: <61.CB.44817.91D421B4@pb1.pair.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Nov 2009 12:19:45.0572 (UTC) FILETIME=[3CA90E40:01CA70EE] Subject: Re: [PHP-DEV] php id string From: jess@zend.com (Jess Portnoy) Perhaps it would be wise to display both the build arch and the current arch on which its running? I used the Darwin/MAC universal build example before but even on Windows and *nix as well when you think about it, one can run a 32bit binary on a 64bit OS, usually provided the stack below [Apache, etc] is also 32 bit. So, unlike the PHP_COMPILER_ID check, which makes sense as the various VCs are declared as not quite compatible, I think in the case of different archs this would be a mistake, just displaying the gathered arch info I can see no harm in though... May the source be with you, Best regards, Jess Portnoy Pierre Joye wrote: > hi, > > This info is available in phpinfo on windows and I would like to add > it in the "php -v" output as well. I'm not sure how we can safely rely > on this info on other platforms but that's definitively something we > should try to do. > > Cheers, > On Sun, Nov 29, 2009 at 11:29 AM, jvlad wrote: > >> Hi all, >> >> Starting with version 5.3 php checks id string when it loads the extensions >> to match its own one and it also shows this string in PHP Extension Build >> line of phpinfo(). That's great. This line contains api#, threadsafe, and >> compiler. So it's almost all important thigs to check and make sure that a >> particular module is binary-compatible with php core. All things, except >> just one, the CPU. It's known that Windows runs on many CPUs, Solaris runs >> fine under sparc, sparc64, x86, and x86_64. Needless to mention linux and >> *bsd systems (I guess they are running on everything). Why not to add what >> phpinfo() shows in Architecture, to the id string? Are there any reasons not >> to do this? >> >> -jvlad >> >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> >> > > > >