Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52185
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=eTZUw8p5F9H5ggSOGwnfAIXPodBjIHEvMg+Y9cy0thDNfXMB5pALHkZuHwwmGg+E9N
         QYDO71pW4JMC1EhJWdjSnA3p8stSJpuUV35koEKAEijGusBDRvskxWDDqX8LiVLjg6TA
         CSi0Egr2x09dlyYAObdQMq6R6TjB5DftfY/2k=
MIME-Version: 1.0
In-Reply-To: <4DC85FBE.2060005@lsces.co.uk>
References: <BANLkTinO0h7020fs+PLjM0fUmMjQXoTsyw@mail.gmail.com>
 <BANLkTim8p7A5+svvjZw6rc_KE+tBMnOsjw@mail.gmail.com> <4DC826B1.4090806@lerdorf.com>
 <BANLkTikpLY+AntSrNi91rzGNZi4FkPrSwA@mail.gmail.com> <4DC82A36.8090604@lerdorf.com>
 <BANLkTi=aLVw8KqOV_jb9dBm=XqX6TqTVwA@mail.gmail.com> <4DC85FBE.2060005@lsces.co.uk>
Date: Mon, 9 May 2011 20:27:02 -0300
Message-ID: <BANLkTikH4H140xh8YLL_J+3dUS6UQAozhw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Please let's not bitch about lazy users not learning C
 to implement THEIR missing feature. (Was Re: [PHP-DEV] 5.4 again)
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

Hi Lester,

I updated the RFC. I may have missed one thing or two, but overall
idea and how code behave is there.
This question is answered on wiki RFC. =3D)

Here is the direct link: https://wiki.php.net/rfc/annotations

Regards,

On Mon, May 9, 2011 at 6:42 PM, Lester Caine <lester@lsces.co.uk> wrote:
> guilhermeblanco@gmail.com wrote:
>>
>> What I thought it could be changed is:
>> - Allow PHP to support it natively and also take advantage of opcode cac=
he
>> - Make API cleaner
>
> Guilherme you still also have to explain WHY we need this. I have a
> perfectly functional documentation and hinting setup working from docbloc=
k
> entries in several years worth of code. Rewriting all of that would have =
to
> have some reason, and working with two systems in parallel does not make
> sense. My current method of working is well supported in phpeclipse while
> your new offering will require some major work in phpeclipse and other to=
ols
> simply to access it? More work for other open source developers who again
> probably don't need it. So as far as I am concerned I need to be persuade=
d
> why this code needs to be IN the core code when I for one can't see any
> reason to use it. Just because COMPILED languages have it is not a reason=
 to
> load an interpreted language with it. Adding it as a removable extension
> might make more sense to me, just as much of the less used code can be
> disabled if we want. And I was coding in C/C++ long before I switched TO =
PHP
> to get away from the problems of using compiled languages for dynamic web
> based systems.
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=3Dcontact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk//
> Firebird - http://www.firebirdsql.org/index.php
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--=20
Guilherme Blanco
Mobile: +55 (16) 9215-8480
MSN: guilhermeblanco@hotmail.com
S=C3=A3o Paulo - SP/Brazil