Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84094
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.47 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <54F28864.7000007@gmail.com>
References: <CAGa2bXbX3uPbSsgrEMqktD=X6S6xGqTkfHdqSZotkZ9kKifDhA@mail.gmail.com>
 <54F28864.7000007@gmail.com>
Date: Sun, 1 Mar 2015 13:25:22 +0900
Message-ID: <CAGa2bXb6-dWCt0F-iF+4qdv_VwoD3naPmNWd=EOSBnmFwwbzzQ@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11470c5ad6991e0510327f82
Subject: Re: [PHP-DEV] [RFC] Design by Contract - Vote only RFC
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11470c5ad6991e0510327f82
Content-Type: text/plain; charset=UTF-8

Hi Stas,

On Sun, Mar 1, 2015 at 12:32 PM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> > https://wiki.php.net/rfc/introduce_design_by_contract
> >
> > This is vote only RFC for 2 competing Design by Contract(DbC) RFCs.
> > Please comment if you have any for this RFC.
>
> I don't see why the first one needs any vote. It is supposed to be
> implemented as an extension, so why not go and implement an extension,
> and put it in PECL, and then propose it for core inclusion, if it proves
> popular?
>

It's possible option with PHP7's AST.


>
> As for the second one, do we really need the syntax change that would
> just move asserts to before { instead of after? If we already have
> zero-cost asserts, why just not use them?


Assertion only DbC has limitations.

 - Invaliants
 - Postconditions

Without native DbC support, it ends up with messy code which is harder to
read. Less code readability decreases maintainability. Therefore, it
increases chance
of bugs. This is the reason why there are languages/extensions for DbC in
other
languages.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11470c5ad6991e0510327f82--