Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82432
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54DAFD32.3000005@gmail.com>
References: <CA+9eiLuNjTa8JzBgnZE5iuv5BZ4Kw4Ehk1ivxPUetNSmZ43JMw@mail.gmail.com>
	<54D7ED22.3080001@gmail.com>
	<CA+9eiLvn7BzfG5N+5Oca8pVO1OTzN9=jWof6NrVDfxvvu-XqPA@mail.gmail.com>
	<CAL=_i_m78Zo5euReKsvFfrLknFq7KEzoNnrrBefC987u+=+yHQ@mail.gmail.com>
	<CA+9eiLuUFiKwOR-BqQEmkQirpAMxgb0GE70Zz7h4WDsd1Me8FQ@mail.gmail.com>
	<CAGa2bXYDvdvRLiOpDk8EnvE00JE4x47SXB9fET4uO2Er_F6s_w@mail.gmail.com>
	<CAL=_i_=mGc_0u0YDCQ7Jiqn_ggyJmQSd_mk_snf7ArDpDXO53A@mail.gmail.com>
	<CA+9eiLur0DVGBNkzFkiTj3POL5B9H0D8=5wE-wuwN2O-FQZNyg@mail.gmail.com>
	<CAL=_i_m=XDKtc2iCSjoquaHkmX862gyMweKS5Xw4AS--oLj19w@mail.gmail.com>
	<CA+9eiLsX=mOOgXmNBKD1L6WKx2=Vy81mThaKa1XCjjAw6R=2vA@mail.gmail.com>
	<CAGa2bXYYp0WQmnTnbsHXzc8XGG0PxOVHu7XvwiMCSJiUWoKeCg@mail.gmail.com>
	<CAGa2bXbKs8cGRTQ1sfeRonnmVXtp7ftVDkz_ALmqr8OnczQxCg@mail.gmail.com>
	<CAGa2bXZ8Wy7bUYgtbajr+GkpQtQEjQLMbFT2mSB5OEnLO2mgfg@mail.gmail.com>
	<CAL=_i_kypYpa3t06peRKwtww=cbh+KhM+iAOtotDGNaFfJBuVA@mail.gmail.com>
	<54DAFD32.3000005@gmail.com>
Date: Wed, 11 Feb 2015 11:22:27 +0400
Message-ID: <CA+9eiLtswwOqku57nHLu8fmHOwzvVcqkHTehBQOPUqQb5P2BUw@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Joe Watkins <pthreads@pthreads.org>, Yasuo Ohgaki <yohgaki@ohgaki.net>, 
	=?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@tekwire.net>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0115f0489eb07e050ecaddf6
Subject: Re: [PHP-DEV] Design by Contract
From: dmitry@zend.com (Dmitry Stogov)

--089e0115f0489eb07e050ecaddf6
Content-Type: text/plain; charset=UTF-8

Hi Stas,

I agree, it may look weird at first, but if you familiar with concept it
looks more or less natural. It's implemented in D, Effiel, it was a
proposal for Java, etc

Anyway, we will have at least 3 competing proposals.

1) contracts in doc-commetns https://wiki.php.net/rfc/dbc

/**
 * @requires ($a >= 0)
 */
function foo($a) {
}

2) contracts as part of the language https://wiki.php.net/rfc/dbc2

function foo($a)
    require($a >= 0)
{
}

3) contracts in annotations

<<requires($a >= 0)>>
function foo($a) {
}

The fact that we are working on (2) now, doesn't mean we will select it as
a final solution. (3) is an interesting option as well.

Thanks. Dmitry.

On Wed, Feb 11, 2015 at 9:56 AM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> > Please steer clear of using the assert API, and in so doing avoid BC
> > concerns with the current assert API.
>
> The operator can be called something other than "assert", I'm sure the
> thesaurus has a lot of possibilities.
>
> > Please avoid adding a magic method and use the suggested syntax for
> > invariant.
> >
> > class Some {
> >     require(invariant-expr);
>
> I think reusing syntax for existing operator in completely unrelated
> context is a big mistake. Having code outside of functions is probably
> not the best idea too.
>
> --
> Stas Malyshev
> smalyshev@gmail.com
>

--089e0115f0489eb07e050ecaddf6--