Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46227 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43010 invoked from network); 29 Nov 2009 11:43:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Nov 2009 11:43:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.44 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.160.44 mail-pw0-f44.google.com Received: from [209.85.160.44] ([209.85.160.44:50611] helo=mail-pw0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 98/3D-44817-47E521B4 for ; Sun, 29 Nov 2009 06:43:49 -0500 Received: by pwj15 with SMTP id 15so1777140pwj.23 for ; Sun, 29 Nov 2009 03:43:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=BnKVs5Te9atVBHmqU9m86Kl5CyJ8U4mNzhoKILPWC8k=; b=WGlQmw4V40GZ5G1wEPtqHqfAIjaYB2KUYsM4QF3LfB4PDpRoVbCy9QiYbH3MstsOkV tjie7U1xyUQPxwQS6ea3jGx2Xpv/06UMsKCvsTE+3wNSESRa2kLJ1QaDB1qdVdO0wUcZ XY0Cw3PFynwgM0Pvku9idLdQTUyY1WHXfaBUc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XVEmxdxJluFbQHGtUGvGVyo5D/QRIT2HWlTsdjSQmWqpbzoLeJEUe3epoagZ53l2us TEW1UnuE78aXELpR48WME+psqPOb9xOhbv+TTdIMtttw/ueP78Ghq+NXJgZT0PdR5a7G ILvluhIpSBvjdISnQXjheX0OLpljUSqlY1P/A= MIME-Version: 1.0 Received: by 10.142.248.5 with SMTP id v5mr301858wfh.272.1259495025210; Sun, 29 Nov 2009 03:43:45 -0800 (PST) In-Reply-To: <61.CB.44817.91D421B4@pb1.pair.com> References: <61.CB.44817.91D421B4@pb1.pair.com> Date: Sun, 29 Nov 2009 12:43:45 +0100 Message-ID: To: jvlad Cc: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] php id string From: pierre.php@gmail.com (Pierre Joye) 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 > > -- Pierre http://blog.thepimp.net | http://www.libgd.org