Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81945
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <022801d0415a$027e0620$077a1260$@tekwire.net>
References: <CA+9eiLuNjTa8JzBgnZE5iuv5BZ4Kw4Ehk1ivxPUetNSmZ43JMw@mail.gmail.com>
	<01d601d04146$6fbda4c0$4f38ee40$@tekwire.net>
	<CA+9eiLvQroYuUW_dVr+r5c=O=1aQ3upfahVUd1e-9qpLQRrxUw@mail.gmail.com>
	<020c01d0414b$2c3a1120$84ae3360$@tekwire.net>
	<CAEZPtU41ud0JSzfc6axnzdKCNJ48-LBCx=zuiFVpQ1mNdTK-kA@mail.gmail.com>
	<022801d0415a$027e0620$077a1260$@tekwire.net>
Date: Thu, 5 Feb 2015 20:36:11 +0400
Message-ID: <CA+9eiLtThKhB13=1O8iRgWXKkOZ0ZxAaz-0P69dnN_ngOOJtTA@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@tekwire.net>
Cc: Pierre Joye <pierre.php@gmail.com>, Yasuo Ohgaki <yohgaki@ohgaki.net>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11339f8ae0f24f050e59e6f9
Subject: Re: [PHP-DEV] Design by Contract
From: dmitry@zend.com (Dmitry Stogov)

--001a11339f8ae0f24f050e59e6f9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

phpdoc is annotation as well, but to split it into specific attributes we
have to write specialized parsers.
Other languages support annotation or attributes that may be used more
easily.

http://docs.hhvm.com/manual/en/hack.attributes.php

Thanks. Dmitry.

On Thu, Feb 5, 2015 at 6:40 PM, Fran=C3=A7ois Laupretre <francois@tekwire.n=
et>
wrote:

> De : Pierre Joye [mailto:pierre.php@gmail.com]
>
> >> Yes, it makes phpdoc more tied to the engine but is it a problem ?
> >
> > And here I have to jump in and say: don't.
> > And remind about one of the exact purposes of annotations.
>
> Sorry, I am not sure I understand.
>
> If you're talking about the link between the engine and phpdoc comments, =
I
> agree. It is not a job for the PHP engine. It is a job for a script
> pre-processor, contained in an extension, and called BEFORE the file star=
ts
> to be parsed by the engine, not after the AST is generated. It is very ea=
sy
> to pre-process PHP scripts and insert PHP code for DbC checks, while doin=
g
> the same using an AST and generated opcodes looks much harder to me.
>
> As I told Alexander, in my opinion, phpdoc blocks already provide a lot o=
f
> useful DbC information. My objective is to extend the syntax to support
> more complex directives, which are still legitimate phpdoc information. I
> see both concepts as closely related. One is generating documentation, on=
e
> is generating runtime checks, but both use the same information.
>
> About annotations, I don't know much about it, as I was naively thinking
> that phpdoc '@' directives were annotations, but I understand I was
> probably wrong. The only concern I have about introducing a new annotatio=
n
> syntax is BC break.
>
> Cheers
>
> Fran=C3=A7ois
>
>

--001a11339f8ae0f24f050e59e6f9--