Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82387
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain yahoo.fr from 212.27.42.2 cause and error)
Reply-To: <nf.laupretre@yahoo.fr>
To: "'Alexander Lisachenko'" <lisachenko.it@gmail.com>
Cc: "'internals'" <internals@lists.php.net>,
	"'Dmitry Stogov'" <dmitry@zend.com>,
	<yohgaki@ohgaki.net>
Date: Tue, 10 Feb 2015 18:00:36 +0100
Message-ID: <05bf01d04553$177610c0$46623240$@yahoo.fr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AdBFUwoTTp1PuUIFQU6lMLYq+JQ2sQ==
Content-Language: fr
Subject: RE: [PHP-DEV] Design by Contract
From: nf.laupretre@yahoo.fr ("F & N Laupretre")

Hi Alexander,

> De : Alexander Lisachenko [mailto:lisachenko.it@gmail.com]
>=20
> This is built on top of reflection+annotation+parser extension.
> Why not to implement this for PHP? From my point of view, this is just =
an
> additional feature, that can be used by limited number of developers.

I like the idea. IMO, DbC directives should be defined outside of =
function body. I proposed doc blocks because it exists and is already =
parsed but a generic syntax for annotations along with a full API to =
interact with extensions would be much better.

Most important : if we define that, for example, everything outside of a =
class/function enclosed in [], is an annotation, it is easy to enhance =
PHP 5 to ignore such syntax, without having to backport the whole =
feature. So, people can start using it for PHP 7 and keep the =
possibility to run their code under PHP 5. That's something that would =
be much harder with the current dbc2 proposal.

I will modify my RFC (https://wiki.php.net/rfc/dbc) to open it to any =
sort of annotations.

Do you think you have enough time to write something in due time ? Ask =
for help if you need.

Regards

Fran=C3=A7ois