Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52718 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43284 invoked from network); 1 Jun 2011 22:24:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2011 22:24:39 -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 74.125.82.54 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: 74.125.82.54 mail-ww0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:36878] helo=mail-ww0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 43/57-32367-42CB6ED4 for ; Wed, 01 Jun 2011 18:24:37 -0400 Received: by wwd20 with SMTP id 20so313313wwd.11 for ; Wed, 01 Jun 2011 15:24:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=CeWWHuSaruK9j+HF7qCHQgy7rUn3jbTz271MLGq+rAA=; b=kCQ7cOp6SkP1KOEEibPXuHHBlEEf7zv+XC04JoYRZnF8iQCR8vNUFZXq/X54C6S97k nVb7JwYvGXwfvMv8dVCBlgOOiTTMY1lSs0nIg8C57HJt5v6UFvgzUP37wUUuVMF4Tluv 8Ji7O1qzS2lAHOVMELMw/30jfWAL8neOi3dhc= 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:content-transfer-encoding; b=M0yT/LWXG6zi0NAriCpwF+ofi7hLv6HZl8yB911VwxVULAKz5aq7Fd1PPKfdfIvhFU QBtJ+vcaXg70M5bCrc2gGxsYknYzUKriK4aZ2S+9hfWovwCtsB/e5Mol2p5upJI26DF3 ciHeeVm5QlcmtkxNxRqx+kCqC4LC2l9bRntnM= MIME-Version: 1.0 Received: by 10.216.15.137 with SMTP id f9mr11426wef.62.1306967073008; Wed, 01 Jun 2011 15:24:33 -0700 (PDT) Received: by 10.216.253.168 with HTTP; Wed, 1 Jun 2011 15:24:32 -0700 (PDT) In-Reply-To: <887FE7CFF6F8DE4BB3A9535F53AFD06A492FB8AD@il-ex2.zend.net> References: <4DE61D77.7040506@zend.com> <4DE66D07.2060105@zend.com> <887FE7CFF6F8DE4BB3A9535F53AFD06A492FB8AD@il-ex2.zend.net> Date: Thu, 2 Jun 2011 00:24:32 +0200 Message-ID: To: Zeev Suraski Cc: Dmitry Stogov , John Crenshaw , PHP internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Final version, RFC release process From: pierre.php@gmail.com (Pierre Joye) On Thu, Jun 2, 2011 at 12:10 AM, Zeev Suraski wrote: >> However, what you refer to is about internals API. We can (and did a >> lot) break ABI between x.y and x.y+1 and should really avoid breaking AP= I >> (read: signatures, source compatibility) if possible. > > I think we need to clear it up in the RFC. =A0My take: > > - Switch from talking about 'ABI' to 'extension API' > - Divide the extension API into source-level and binary-level > - For x.y+1, make it clear that there's no need to retain binary-level ex= tension API, and that source-level extension API is a 'should' and not a 'm= ust'. On it, adding the reference to ABI/API definition as well. --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org