Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82390 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40812 invoked from network); 10 Feb 2015 17:59:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Feb 2015 17:59:28 -0000 X-Host-Fingerprint: 79.94.237.143 143.237.94.79.rev.sfr.net Received: from [79.94.237.143] ([79.94.237.143:14703] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A9/21-32490-DF64AD45 for ; Tue, 10 Feb 2015 12:59:26 -0500 To: internals@lists.php.net Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes References: <54D7ED22.3080001@gmail.com> Date: Tue, 10 Feb 2015 18:59:19 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable Message-ID: User-Agent: Opera Mail/1.0 (Win32) X-Posted-By: 79.94.237.143 Subject: Re: [PHP-DEV] Design by Contract From: bensor987@neuf.fr ("Benoit SCHILDKNECHT") Hi Yasuo, Le Tue, 10 Feb 2015 07:25:00 +0100, Yasuo Ohgaki a = = =E9crit: > Updated wiki page. > https://wiki.php.net/rfc/dbc2 While I agree this RFC is going in the right direction, I don't like the= = use of "require" and "return". They are already used for something completely different, I think it wil= l = make the code more difficult to understand (for beginners) and parse (fo= r = external programs). IDE will have some difficulties too. I've discussed = = about it with some PHP developers who work with me, and they all agree. If it was me, I would use "pre" and "post", "in" and "out" or "requires"= = and "ensures". I understand that creating more keywords isn't something = = pleasant, but it would make the code more readable and logical. Regards, Benoit.