Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64843
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50EF2634.9030008@sugarcrm.com>
References: <CAFDmeSSOEXqv+QHAq7Eu2nRz6dg8zTXPFDt7FdDV=Qk+2fuU3Q@mail.gmail.com>
 <CAEZPtU5E+us2na6jXKqP4u-Q-hUZHDS+ZGQv5y6h-YW=D3thhA@mail.gmail.com> <50EF2634.9030008@sugarcrm.com>
Date: Thu, 10 Jan 2013 22:49:24 -0500
Message-ID: <CAFp73XtEpOJQFxcsyP_nYhpkyOtS8dvg0jLUBzqxKqcQA5dShw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Pierre Joye <pierre.php@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec54fae3aa074d104d2fb2f7b
Subject: Re: [PHP-DEV] A remark about PHP's Vision and new things.
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

--bcaec54fae3aa074d104d2fb2f7b
Content-Type: text/plain; charset=UTF-8

Stas,

I totally agree and Pierrick and I faced all these problems during the
creation of patch.
If PHP doesn't all have support required for a given feature, let's just
not only discuss feature, but also the required support too. Named
parameters is a great example. I'd also name another one,
ReflectionNamespace; namespaces are converted to strings and attached to
their classes during compile time and you can never reflect over them to
grab for example their names.
I even mentioned to Andi back in 2010 that ZE gets re-written every 5
years. That happened in 2000, 2005 and we're now hitting walls because of
"monster" changes required to implement feature A or B. Maybe it's time to
consider a rewrite again?

Cheers,


On Thu, Jan 10, 2013 at 3:36 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:

> Hi!
>
> > I strongly suggest to anyone following the (too many) threads about
> > annotations to try the C# annotation and see what it allows. It goes
>
> As far as I can see, C# annotations rely on two very important things:
> 1. Compiler support. Compiler really knows a lot about what annotations do.
> 2. Extensive library support. Annotations themselves are just passive
> metadata, what makes them work is .net framework that uses them.
>
> This means to make annotations as useful in PHP we would have to have
> substantial support in the engine (including bytecode caching
> provisions, etc.) and some libraries that require very
> latest-and-greatest version of PHP.
>
> Another thing is that we're not having some features that are used
> extensively in C# annotations, main being named parameters support.
>
> I am saying this not to oppose the idea of annotations or the idea of
> looking into C# and other languages (actually, I think anybody who talks
> about it should look at least into what C# and Java do with it - and
> also what Python does, which is completely different direction, just to
> know other options). I'm just saying porting this to PHP may be less
> than straightforward.
>
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
Guilherme Blanco
MSN: guilhermeblanco@hotmail.com
GTalk: guilhermeblanco
Toronto - ON/Canada

--bcaec54fae3aa074d104d2fb2f7b--