Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73406 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 83591 invoked from network); 25 Mar 2014 02:36:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Mar 2014 02:36:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.115 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.115 smtp115.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.115] ([108.166.43.115:57687] helo=smtp115.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B0/42-06865-9BBE0335 for ; Mon, 24 Mar 2014 21:36:42 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 254FA1B99C7; Mon, 24 Mar 2014 22:36:39 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id C07691B943D; Mon, 24 Mar 2014 22:36:38 -0400 (EDT) Message-ID: <5330EBB6.5060306@sugarcrm.com> Date: Mon, 24 Mar 2014 19:36:38 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Gary Mort , "internals@lists.php.net" References: <532FF7B9.5040700@hoa-project.net> <1395653827.9365.9.camel@guybrush> <1395654744.9365.17.camel@guybrush> <1395655474.9365.25.camel@guybrush> <5330E32A.8090605@gmail.com> In-Reply-To: <5330E32A.8090605@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP Specification From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > What would be the process for that? The RFC process covers adding new > features and removing deprecated features. Just start creating it and if the process will be needed, it can emerge among the people that are doing it. When something that is fit for review would be ready, we may use this list and the wiki or other tools to review it (I'd advise to publish it on a platform that allows comments, such as github or google docs) and then use RFC-like process to gain acceptance. But first somebody needs to actually do it. > Alternative implementations are great for discovering bugs in the > reference implementation. Not sure in which way another implementation should be helpful in discovering bugs in the PHP engine - could you give some examples of such bugs? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227