Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64855
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50EFC482.6020801@b1-systems.de>
References: <CAAyV7nEWD7SYjjN_kia9rSknjL2BKi157G1r5VJPfTkHB4Y5ww@mail.gmail.com>
 <50EDBEA5.1050201@sugarcrm.com> <CAAyV7nHoMwM=Ge8+97mmUiNR1+ChCq3mW+Dgx0r9Hc=yn6Q8=w@mail.gmail.com>
 <50EE5DAF.2080901@sugarcrm.com> <CAAyV7nFG++8WNpyCk1gByVk3aLSh7CzR1F0fmn2M43thXZQKKQ@mail.gmail.com>
 <50EF2195.3080907@sugarcrm.com> <CAAyV7nE27JqMEBSd_0b0QYk1OjErHyR_PpvZoBD-fVdAPuDNTQ@mail.gmail.com>
 <CANVTSm5afTqJuYCm+q2Qb2vzyWYQxJuYRwsZW++RRdbbLZNXBA@mail.gmail.com>
 <50EF49AF.9050801@b1-systems.de> <48412E0A-3FCC-440D-8479-39B666EB7213@gmail.com>
 <CAFt2z-m9p0+=ryazD+b779AojdvKCiG3uSBEuLcTuw_1WxJCSQ@mail.gmail.com> <50EFC482.6020801@b1-systems.de>
Date: Fri, 11 Jan 2013 03:14:24 -0600
Message-ID: <CAFt2z-nyUzgXoFrreP-=kvtcKwRfjE-yvzx99bKRD0mBP0kL+g@mail.gmail.com>
To: Ralf Lang <lang@b1-systems.de>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d0447f420f600b804d2ffb9ed
Subject: Re: [PHP-DEV] Re: Was Reflection annotations reader - We Need A Vision
From: dukeofgaming@gmail.com (dukeofgaming)

--f46d0447f420f600b804d2ffb9ed
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jan 11, 2013 at 1:51 AM, Ralf Lang <lang@b1-systems.de> wrote:

> Am 11.01.2013 05:55, schrieb dukeofgaming:
> > I have a question, maybe it is dumb: why not those opposed to using
> > annotations just... refrain from using them?
> >
>
> Although I am not the least against annotations, there are valid and
> good technical reasons why one does not want to have a feature in the
> language.
>
> As Rasmus said, the code for annotations also needs to interface with
> opcode caches and other core and close-to-core technologies. This will
> require additional development and maint. time/manpower. This is a
> finite resource, there is a tradeoff between expensive new language
> features like annotations and other stuff which needs to be done. You
> can probably not have both at the same time.
>

I understand, those arguments make sense. Wouldn't it be good to just
document these sort of blockers in the RFC without rejecting the proposal?,
who knows, someone can come and have a solution for each one of these in
one form or other.


>
> > Finally, I remember the lack of support for development has been a
> > problem... so why not call out for support to the community?, from GSoC
> to
> > PHP gurus litterate on Comp Sci and software engineering and
> architecture?
>
> I think this has been done before and most who stay and contribute over
> time have come here by their own means.
>

By the way, even if it is not to work on a particular features, maybe call
for more help on maintenance?


>
> --
> Ralf Lang
> Linux Consultant / Developer
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--f46d0447f420f600b804d2ffb9ed--