Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78675
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.195 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54591A76.8070302@sugarcrm.com>
References: <CALW=WECCELQOZpqB3foM6T+Qz+0v3hWT-mdTgCmGApEG4vxNcg@mail.gmail.com>
	<CAGAGxbZfDd5QaQ5iW+_pJzcHDHQztG_H_9JVyv4XT4BDaLVczw@mail.gmail.com>
	<CADUqk8UNnSL7C5_RDoNNFsdpuBoAFwdmzanaF9+GkeLN_gQkhQ@mail.gmail.com>
	<CAEZPtU44YsM1s_zJqPhAEu6cbqxh4k=A35qOd_z=XWErNf5wPA@mail.gmail.com>
	<5457AF2F.90808@php.net>
	<5457BDB7.8070701@garfieldtech.com>
	<CAFMT4NrgLzzpMt5Vm_Q84hXJ65U2jjqtLFm=ALYqwtiyxp0LjA@mail.gmail.com>
	<CAEZPtU4urLHc9FM0GohQJwkZD-TYKTVuPXcUMXsG5cAScHz3mw@mail.gmail.com>
	<54589A8D.3020607@sugarcrm.com>
	<CAEZPtU5qfcjCrcWRKW+ETF4uBp46rwVbv9nCdJoSUF+M+wKQdA@mail.gmail.com>
	<CAEPJdumXG9TC7xG8-YmGbQiwPMzwYvE_jXWvOQuNmz+U_=+ZaQ@mail.gmail.com>
	<1C3F4FA3-ABD5-4F6F-A898-F63AC1C723D5@ajf.me>
	<54591A76.8070302@sugarcrm.com>
Date: Tue, 4 Nov 2014 22:03:08 +0200
Message-ID: <CALW=WEDyZZS4zzNSRyAWyW0WcAoOrZX1dDrP83krWVzQHWjy-Q@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Andrea Faulds <ajf@ajf.me>, Benjamin Eberlei <kontakt@beberlei.de>, Pierre Joye <pierre.php@gmail.com>, 
	Levi Morrison <levim@php.net>, PHP internals <internals@lists.php.net>, 
	Larry Garfield <larry@garfieldtech.com>
Content-Type: multipart/alternative; boundary=001a113f31c8b774c405070df3aa
Subject: Re: [PHP-DEV] Annotation PHP 7
From: ua.san.alex@gmail.com ("S.A.N")

--001a113f31c8b774c405070df3aa
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

If this is difficult, you can do in PHP 7.0 simple realization
annotation/facades, in versions 7.x to develop and refine.

Most importantly, define the syntax and semantics annotation/facades, for a
version of PHP 7.0

Demand in annotation/facades is very high, ~80% of all popular frameworks
their use, it is really what you need PHP developers.

2014-11-04 20:27 GMT+02:00 Stas Malyshev <smalyshev@sugarcrm.com>:

> Hi!
>
> > The approach for annotations that I like best would actually be not
> > annotations, but Python-style decorators. They=E2=80=99re very simple, =
but
> > very powerful. They would allow you to do annotations, but also add
> > extra functionality to functions.
>
> For python-style decorators, at least the way they work in Python, we'd
> need to organize our function tables differently, as Python just
> replaces the function with another one while decorating, and I'm not
> sure it'd be as easy to do with PHP.
>
> > Which would be equivalent to the following PHP code:
> >
> > $myfunc =3D function myfunc() { # function source code here }; $myfunc
> > =3D some_decorator($myfunc, foo, bar);
>
> Not really, because functions work differently in Python and in PHP. You
> can not just replace a function in class's function table with random
> closure in PHP, at least easily.
> You'd have to convert all such functions to closures (or something that
> can be both, maybe) and have the engine be aware that function table now
> can store closures. And, also, inheritance may get a bit weird there. It
> would be very powerful, but it may not be very simple to do.
>
> Also, it is a major overkill for what annotations are commonly used -
> attaching a piece of data to an entity. In Python, decorators are very
> powerful for modifying function behavior (i.e., attaching pre/post
> conditions to functions or doing some things phpunit does is really
> easy) but it is too much for just attaching data.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a113f31c8b774c405070df3aa--