Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82451
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.220.51 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAL=_i_mV4GHs1eXq=Bhuj-asMdOZ-SXASfcJW2Qf1c4gV8qaTA@mail.gmail.com>
References: <CA+9eiLuNjTa8JzBgnZE5iuv5BZ4Kw4Ehk1ivxPUetNSmZ43JMw@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>
	<CA+9eiLtswwOqku57nHLu8fmHOwzvVcqkHTehBQOPUqQb5P2BUw@mail.gmail.com>
	<54DB0BC0.20304@gmail.com>
	<54DB0E55.9000207@gmail.com>
	<CAL=_i_mV4GHs1eXq=Bhuj-asMdOZ-SXASfcJW2Qf1c4gV8qaTA@mail.gmail.com>
Date: Wed, 11 Feb 2015 08:14:12 +0000
Message-ID: <CAL=_i_=Nv8BYWW1naRMaLETBj4oqdtrYYnM-0uRddtLYeDtZ=Q@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Dmitry Stogov <dmitry@zend.com>, 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=047d7bd77068ad1361050ecb9636
Subject: Re: [PHP-DEV] Design by Contract
From: pthreads@pthreads.org (Joe Watkins)

--047d7bd77068ad1361050ecb9636
Content-Type: text/plain; charset=UTF-8

> OTOH, don't our new parsing improvements allow us to handle syntax like
this without introducing a keyword that would be forbidden as
class/function name

Not that I am aware of, the AST stuff didn't touch the parser like that, it
has the same limitations it had before AFAIK.

Cheers
Joe

On Wed, Feb 11, 2015 at 8:12 AM, Joe Watkins <pthreads@pthreads.org> wrote:

> > Just a thought - what about something like __pre/__post? We own __*, so
> no BC problems.
>
> I'm not married to the words being used, at all.
>
> I think this is a good idea, we would need __pre, __post , and
> __invariant, or some combination of three.
>
> Any objection to using __ prefixed names, and any other suggestion for
> them, or just use the above ?
>
> Cheers
> Joe
>
>
> On Wed, Feb 11, 2015 at 8:09 AM, Stanislav Malyshev <smalyshev@gmail.com>
> wrote:
>
>> Hi!
>>
>> >> function foo($a)
>> >>     require($a >= 0)
>> >> {
>> >> }
>> >
>> > This is a step better but still we have the similar issues with
>> > readability, to which reuse of 'require' is added.
>>
>> Just a thought - what about something like __pre/__post? We own __*, so
>> no BC problems.
>> OTOH, don't our new parsing improvements allow us to handle syntax like
>> this without introducing a keyword that would be forbidden as
>> class/function name? The context is pretty unambiguous here.
>> --
>> Stas Malyshev
>> smalyshev@gmail.com
>>
>
>

--047d7bd77068ad1361050ecb9636--