Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64792
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mindplay.dk from 209.85.220.176 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAFp73XvQimu4z7VTJ065HJteeL65xMODpJGyRuz=jjSymKdvcg@mail.gmail.com>
References: <CADqTB_h4eh4mPi89uRps6vZWXjDEhUtcBopL7jmO-UgRuyf19w@mail.gmail.com>
	<50EBDEEE.8070605@sugarcrm.com>
	<CAOfKkdQXh53oxpCQ59R_hcws4Pd=q+O_VMOZ=tS+F2_7qof3RA@mail.gmail.com>
	<alpine.DEB.2.02.1301091204370.28951@whisky.home.derickrethans.nl>
	<50EDA1C5.4040500@sugarcrm.com>
	<CADyq6s+SUBGGgvLFxFLaN+mMMP8j1iWWmQdr+uxn1YDRkXwYNA@mail.gmail.com>
	<CAFp73XvQimu4z7VTJ065HJteeL65xMODpJGyRuz=jjSymKdvcg@mail.gmail.com>
Date: Wed, 9 Jan 2013 20:58:07 -0500
Message-ID: <CADqTB_iQD0gF70vHuegT3YyaxP3pO_jZGn=vix_6bmSxTYXg8A@mail.gmail.com>
To: "guilhermeblanco@gmail.com" <guilhermeblanco@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=bcaec54eed36a6ca3b04d2e5822e
Subject: Re: [PHP-DEV] [RFC] Reflection annotations reader
From: rasmus@mindplay.dk (Rasmus Schultz)

--bcaec54eed36a6ca3b04d2e5822e
Content-Type: text/plain; charset=ISO-8859-1

I'm going to address these question in the proposal I'm working on - once
it's all in writing, I will post for debate.

On Wed, Jan 9, 2013 at 2:57 PM, guilhermeblanco@gmail.com <
guilhermeblanco@gmail.com> wrote:

> - Should we support nested annotations?
>
> - How [Foo()] will be different from new Foo()? If they are not different,
> is there an alternative to not bloat lexical parsing?
>
> - How parameters would be injected? Is constructor the only way to inject
> parameters?
>
> - How would we handle optional parameters, like [Foo("bar", null, null,
> "woo")]?
>
> - Suppose you wanna fix the optional arguments by named parameters, like
> [Foo("bar", test="woo")]. Doesn't it diverge with PHP interests of not
> supporting parametrized arguments? Should we modify the former or the
> later? Personally I'm a fan of named parameters.
>
> - How would we deal with inheritance? Should a method, for example,
> inherit the same annotations from parent or not?
>
> - Suppose that you define annotations to fix the inheritance problem, how
> would it be?
>
> - How would we cast possible usages of an annotation to only class, method
> or property? Using annotations too?
>
> - How would it be the syntax to declare a new annotation?
>
> - Would it be possible to modify an annotation value using Reflection, for
> example?
>
> - How could it be handled on APC to minimize the performance impact?
>

--bcaec54eed36a6ca3b04d2e5822e--