Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52687 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58822 invoked from network); 1 Jun 2011 16:50:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2011 16:50:38 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.203 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.203 smtp203.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.203] ([67.192.241.203:43042] helo=smtp203.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B0/6A-32367-CDD66ED4 for ; Wed, 01 Jun 2011 12:50:38 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp10.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 9775B1B80D7; Wed, 1 Jun 2011 12:50:34 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp10.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 755621B80CA; Wed, 1 Jun 2011 12:50:33 -0400 (EDT) Message-ID: <4DE66DD8.7080804@sugarcrm.com> Date: Wed, 01 Jun 2011 09:50:32 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Dmitry Stogov CC: John Crenshaw , PHP internals References: <4DE61D77.7040506@zend.com> <4DE66D07.2060105@zend.com> In-Reply-To: <4DE66D07.2060105@zend.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Final version, RFC release process From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Before now each major (5.y+1) release introduced API changes. > We just couldn't introduce literal tables, interned strings, etc without > API changes. I think by API there it means PHP-level API, i.e. one exposed to the user, not binary API exposed to the extensions, which is meant by ABI. So what should be preserved is PHP function signatures, classes, syntax, INI settings, etc. but internals can change. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227