Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29822 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66678 invoked by uid 1010); 27 May 2007 01:23:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 66663 invoked from network); 27 May 2007 01:23:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 May 2007 01:23:38 -0000 Authentication-Results: pb1.pair.com header.from=giunta.gaetano@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=giunta.gaetano@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.169 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: giunta.gaetano@gmail.com X-Host-Fingerprint: 66.249.92.169 ug-out-1314.google.com Linux 2.4/2.6 Received: from [66.249.92.169] ([66.249.92.169:2720] helo=ug-out-1314.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 71/0C-49291-89DD8564 for ; Sat, 26 May 2007 21:23:38 -0400 Received: by ug-out-1314.google.com with SMTP id m2so1098977uge for ; Sat, 26 May 2007 18:23:34 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=MZY30nZZSpqyJOH1Sajrf7FO1dcPyehpXL0NS96Boqv+6cEN1fxEgNsEF+lOQDJYx1L4KMMf5C6zfCZtARjb7ZLtZzQkt9Eg1diyag8ZdHl9RqG8JC2X8ndNkYtIijoHoi3ENitdC8ZzIJ26le9KE1xL6RbIR5//bpd3JyRgEyY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=CLleCHmRyTPbTcZB3+lhfXuQsD5VH8D0vRJqRdBNHjYUaELtZVL/lWCTHGzm34fzrBM6cVNtXOEznoAUnHTvAK4NLL2DS2Qvx994SYgOZ0ktyCcYf+WiOuNrDHpf+gjgR0lwvVrvBRmLCD16xsyUFWcO0wUf2UclAMmTPZEIFF8= Received: by 10.67.32.16 with SMTP id k16mr4076294ugj.1180229014429; Sat, 26 May 2007 18:23:34 -0700 (PDT) Received: from ?192.168.1.2? ( [151.66.58.95]) by mx.google.com with ESMTP id c22sm4630495ika.2007.05.26.18.23.32; Sat, 26 May 2007 18:23:33 -0700 (PDT) Message-ID: <4658DD8A.8050004@gmail.com> Date: Sun, 27 May 2007 03:23:22 +0200 User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: RE: Fixing PECL + Core From: giunta.gaetano@gmail.com (Gaetano Giunta) Just to add my experience (even though the original poster explicitly asked for single extensions not to be mentioned) from a not-completely-unrelated problem: some extensions have an "internal" version number that is not always updated when the userland API of said extension is changed - see eg. Json and the recent change of behavior on decoding scalar values. This makes it very hard for people maintaining php libraries to code defensively and test the version in use to enable workarounds: - the extension version number is useless (if not managed correctly) - the php version number is useless, since the extension might have been downloaded and compiled from pecl and not correspond to the version that is distributed with the core The only option left in this situation is to test the functionality needed first, then use it, much as it is done in js - a very sad state of things... (of course I would not recommend disabling upgrade / backport of a php extension from pecl as a solution) The fact that the extension lives in both pecl and core and the two might be slightly out of sync does not help at all when trying to find out the cause of regressions... Bye Gaetano