Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78635
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.44 as permitted sender)
MIME-Version: 1.0
Reply-To: marcio3w@gmail.com
In-Reply-To: <CAOsHV+uyATXewB4t60zKTpbERGq=qRLJJNPMuMjoc8vaRHKjJA@mail.gmail.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>
	<CAEbg-4bP8wYV6C-rEpJfDeasf_tkzAjABXqrVO5ibM7RJk3rYA@mail.gmail.com>
	<CAOsHV+uyATXewB4t60zKTpbERGq=qRLJJNPMuMjoc8vaRHKjJA@mail.gmail.com>
Date: Tue, 4 Nov 2014 10:18:54 -0300
Message-ID: <CAOsHV+tuxJ6d16pC6UW2_UPvWeieByhypzt99L_xLqn0j-Q_iw@mail.gmail.com>
To: 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=001a11c364741b06980507084e51
Subject: Fwd: [PHP-DEV] Annotation PHP 7
From: marcio.web2@gmail.com (Marcio Almada)

--001a11c364741b06980507084e51
Content-Type: text/plain; charset=UTF-8

Hi!

> PHP7 has a wonderful parser, maybe it's possible to provide a general
> syntax for annotations with userland hooks for arbitrary data. This
> approach can give a tool for framework developers to define a node visitor
> for annotations. Alternative way is to define simple key-value storage and
> access it via Reflector->getAnnotations().

I've been maintaining this annotations library
https://github.com/marcioAlmada/annotations,
it uses json parser as the interpreter for it's DSL to declare annotations.
One of the key features is to allow this key-value storage Alexander
pointed out. The main focus
is to allow annotations to be declared without the need for a concrete
class for each annotation
though it doesn't impedes that.

I'm wondering if it would be a good idea to unite maintainers of userland
annotations libraries
and grab the good parts of each project so we can have a merged RFC on this
subject?

Huge +1 for this discussion too. PHPNG seems like a good milestone to have
this core annotations.


2014-11-04 9:27 GMT-03:00 Alexander Lisachenko <lisachenko.it@gmail.com>:

Hi!
>
> It would be nice to take "paving the walkways" approach, but last time
> > we tried, IIRC we've got into something very over-engineered. Maybe if
> > we try again with more restricted scope (i.e. not trying to put a DSL
> > for describing arbitrarily complex data structures into it :) it would
> > be more successful this time.
> >
>
> PHP7 has a wonderful parser, maybe it's possible to provide a general
> syntax for annotations with userland hooks for arbitrary data. This
> approach can give a tool for framework developers to define a node visitor
> for annotations. Alternative way is to define simple key-value storage and
> access it via Reflector->getAnnotations().
>
> I want to put my huge +1 vote on annotations support in the core, because
> Go! AOP uses annotations a lot for defining metadata and markers in the
> code and provides an engine for advanced programming patterns and method
> interception. Doctrine is good library, but this can be better on core
> level.
>

--001a11c364741b06980507084e51--