Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82143 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87758 invoked from network); 8 Feb 2015 15:44:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Feb 2015 15:44:04 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:1662] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B1/E0-15550-34487D45 for ; Sun, 08 Feb 2015 10:44:04 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 8597D4B008C; Sun, 8 Feb 2015 16:40:32 +0100 (CET) Reply-To: To: "'Yasuo Ohgaki'" , "'guilhermeblanco'" Cc: "'PHP Internals'" References: In-Reply-To: Date: Sun, 8 Feb 2015 16:43:58 +0100 Message-ID: <03f301d043b6$0e79b330$2b6d1990$@tekwire.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGgxP9HPTh52uHWkGo6jLSeXRdtNAH7rYnxAohJhz6dIbTEgA== Content-Language: fr X-Antivirus: avast! (VPS 150208-0, 08/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: Design by Contract From: francois@tekwire.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : yohgaki@gmail.com [mailto:yohgaki@gmail.com] De la part de Yasuo = Ohgaki > > Since people's preferences are diverse. It might be a good idea having = pre-vote > for designs, then we may have final vote with single design. > > We need some consensuses even for pre-vote. > > What do you think? What I think is that I have written a 600-line RFC, that you refuse to = comment because you still hope you can impose a D-like syntax by another = way. I don't agree on a pre-vote on design and, then, care about = details, because that's just an artefact to get an agreement on D-like = syntax before people can read and understand my proposal, and without = exploring the implications of your design. Here is a fair way to proceed: I have written an RFC, trying to explore = honestly every aspects of the design I'm proposing. Now, either you = agree, or you write yours with the same goal in mind. Then, we may = choose. That's the rule. Saying 'I don't like that' without proposing an = alternative is not the right way. I won't help you get an a-priori = approval, just to say thereafter that, whatever problem we find, we must = stick with this design because it was pre-approved. If you write an RFC = and people approve it, that's OK. Anyway, as I think DbC can be implemented without any change in the = core, I'll probably implement it by myself as a zend extension. So, you = can do what you want in PHP 7. Regards Fran=C3=A7ois