Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82982
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <024101d04ab8$b880a1a0$2981e4e0$@php.net>
References: <CA+9eiLsxSpbdaa7Bpci2PRXQMRkTUiwZphjQYv2iDyXLUhrMow@mail.gmail.com>
	<CA+9eiLuP_+WR+4Yb_HziFu=pznqc5sCXqCF3k1SaSrwamY2gUg@mail.gmail.com>
	<01c401d04a64$1df25470$59d6fd50$@php.net>
	<CA+9eiLtbKpbLXbyYn3P3rHXbW+qnzbikrrqrQad=EuO3bHiiaQ@mail.gmail.com>
	<024101d04ab8$b880a1a0$2981e4e0$@php.net>
Date: Tue, 17 Feb 2015 20:30:17 +0400
Message-ID: <CA+9eiLtfuTXPd7YcZcrEYKjox0DBbdwnLUwosU7h4GX-73bnuQ@mail.gmail.com>
To: francois <francois@php.net>
Cc: PHP Internals <internals@lists.php.net>, Nikita Popov <nikita.ppv@gmail.com>, 
	Guilherme Blanco <guilhermeblanco@gmail.com>, Pierrick CHARRON <pierrick@webstart.fr>, 
	Alexander Lisachenko <lisachenko.it@gmail.com>, Pierre Joye <pierre.php@gmail.com>, 
	Zeev Suraski <zeev@zend.com>, Andi Gutmans <andi@zend.com>, Joe Watkins <pthreads@pthreads.org>, 
	Yasuo Ohgaki <yohgaki@ohgaki.net>, Sebastian Bergmann <sebastian@php.net>, 
	Stanislav Malyshev <smalyshev@gmail.com>, Rasmus Lerdorf <rasmus@lerdorf.com>
Content-Type: multipart/alternative; boundary=001a11c3ea3ce0417b050f4b37f8
Subject: Re: [PHP-DEV] Re: Annotations in PHP7
From: dmitry@zend.com (Dmitry Stogov)

--001a11c3ea3ce0417b050f4b37f8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 17, 2015 at 4:50 PM, Fran=C3=A7ois Laupretre <francois@php.net>
wrote:

> HI Dmitry,
>
> Question : in which scope do you evaluate the PHP expression ?
>

We don't evaluate expressions. We just store them. Evaluation and/or
modification is a subject for future development.


>
> Example :
>
> <DbC.requires($a > 0);>
> <DbC.ensures(__RETURN__ > 0);>
>
> function foo($a)
> {
> ...
>
> How can you know from this that the first expression must be evaluated at
> function entry, that the second one must be interpreted when function
> exits, let alone the question of __RETURN__ replacement and external swit=
ch
> to authorize/disable DbC evaluations.
>

If we will support such DbC approach, then an additional extension may use
this attributes to insert their code into appropriate places of main
function.

Thanks. Dmitry.


> Several people rightly stated that expression would be computed at compil=
e
> time. That's a way to solve the scope question as it practically means th=
at
> expressions are evaluated in the global scope, but DbC must evaluate its
> expressions at runtime. Does it mean we should write '<DbC.requires('$a >
> 0')> ? Not very intuitive but that's probably the only solution.
>
> Something else : I am not sure I understand, but do you intend evaluating
> annotation expressions everytime you parse the file. Or would you provide=
 a
> global switch ?
>
> > Any one can use doc-block now and later, but php core won't parse
> doc-blocks. It's a task for external tools.
>
> I understand. Actually, DbC is not the perfect use case for annotations.
> It would be fine to find a good use case because neither of DbC, AOP,
> Doctrine, or phpdoc fit so well.
>
> There comes my last question : is it so interesting and mandatory to
> implement annotations in the core, instead of an extension which would
> parse doc blocks when needed, and would return bare strings through a
> reflection-like API ? I know most want to put annotations in the core, bu=
t
> what's the real benefit, if we don't consider performance ? Do we have us=
e
> cases comparing both approaches ?
>
> The fact that we voluntarily make it incompatible with phpdoc and doctrin=
e
> 'annotations' saddens me a bit too because people used to the current
> 'annotation' meaning will have to integrate that a new PHP native
> 'annotation' feature, totally different from what they've been using for
> years. And doctrine is not an edge-case. If there are good reasons, why
> not, but I don't see them yet.
>
> Regards
>
> Fran=C3=A7ois
>
>
>
>

--001a11c3ea3ce0417b050f4b37f8--