Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52187
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.184 cause and error)
Message-ID: <4DC88602.30400@lsces.co.uk>
Date: Tue, 10 May 2011 01:25:38 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.18) Gecko/20110320 SUSE/2.0.13-1.2 SeaMonkey/2.0.13
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
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> <BANLkTikH4H140xh8YLL_J+3dUS6UQAozhw@mail.gmail.com>
In-Reply-To: <BANLkTikH4H140xh8YLL_J+3dUS6UQAozhw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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: lester@lsces.co.uk (Lester Caine)

guilhermeblanco@gmail.com wrote:
> 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. =)
>
> Here is the direct link: https://wiki.php.net/rfc/annotations
But there is nothing there that explains why this is any use where we are not 
compiling code ... and are all things we are already doing with comment blocks 
... which CAN be stripped to speed up operation once in a production 
environment. A compiler simply strips the unnecessary stuff when building the 
running code, how do you propose PHP does that ? If I want compiled code then I 
can use any number of other languages, PHP simply runs what I have in the file.

> 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 cache
>>> - 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 docblock
>> 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 tools
>> 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 persuaded
>> 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=contact
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