Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52307 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43012 invoked from network); 11 May 2011 17:11:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 May 2011 17:11:41 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.186 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.26.186 c2beaomr08.btconnect.com Received: from [213.123.26.186] ([213.123.26.186:35797] helo=mail.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 44/11-36343-B43CACD4 for ; Wed, 11 May 2011 13:11:40 -0400 Received: from host81-138-11-136.in-addr.btopenworld.com (EHLO _10.0.0.4_) ([81.138.11.136]) by c2beaomr08.btconnect.com with ESMTP id CTN06518; Wed, 11 May 2011 18:11:36 +0100 (BST) Message-ID: <4DCAC347.9090305@lsces.co.uk> Date: Wed, 11 May 2011 18:11:35 +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 References: <4DC826B1.4090806@lerdorf.com> <4DC82A36.8090604@lerdorf.com> <4DC83401.2090202@sugarcrm.com> <4DC8D122.3050507@lsces.co.uk> <4DC8F125.2010503@toolpark.com> <4DC8FB1A.7040206@lerdorf.com> <4DC98100.6080806@oracle.com> <4DC9827B.6080409@lsces.co.uk> <4DC9AEF8.5070701@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mirapoint-IP-Reputation: reputation=Good-1, source=Queried, refid=tid=0001.0A0B0301.4DCAC347.00CB, actions=tag X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.5.11.154521:17:7.586, ip=81.138.11.136, rules=__MOZILLA_MSGID, __HAS_MSGID, __SANE_MSGID, __USER_AGENT, __MIME_VERSION, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __CT, __CT_TEXT_PLAIN, __CTE, __ANY_URI, __FRAUD_BODY_WEBMAIL, __CP_URI_IN_BODY, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0204.4DCAC348.0133,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine X-Junkmail-IWF: false Subject: Re: [PHP-DEV] annotations again From: lester@lsces.co.uk (Lester Caine) guilhermeblanco@gmail.com wrote: > Hi Lester, > > On Tue, May 10, 2011 at 6:32 PM, Lester Caine wrote: >> Ferenc Kovacs wrote: >>> >>> sorry my FUD counter just overflowed with your last comment. >> >> Sorry you feel that way, but obviously there are more people with my view >> that we simply do not agree on IF annotation should be implemented. I'm a >> lot more comfortable with something that works WITH what we already have >> rather than going off on yet another tangent. Tidying existing docblock >> content to an updated format makes a lot more sense then having to do a >> wholesale re-write many thousands of files. Adding another copy of much of >> the same data in a complete different format is equally insane? > > Documentation != Annotation. > > A documentation is something that is human readable and understandable > bu humans, but not for applications. > An annotation is a behavioral functionality that is between human > readable and machine readable. > It's the starting point for AOP, which allows you to intercept > execution. I won't enter in details because I assume you have enough > experience to know how does it work. I feel that enough people have explained why the current docblock standard should not be replaced by yet another layer, but I have yet to see something 'annotation' related that has not already been used for several years within the docblock wrapper format. I come from BCB where compiler commands have always been in comments so it's natural for me anyway. >> PDO is another case in point - that is still not accepted and fully >> functional as a replacement for the genric drivers ... ADOdb still provides >> a valid abstraction layer, and if you must use PDO then it just loads that >> instead of the generic one ... and it runs just as fast on either. PDO is >> functional, but needs more work, however there are few people that find the >> need for improving it? > > PDO is horrible. You have to implement workarounds for almost every driver > For example Oracle driver... I already reported to Chris tons of > issues (bug ids) that even include patches for each situation and I > saw a *VERY* few bugs fixed. > I know he has priorities and etc, but it seems that you flood your > mouth to talk about PDO, but actually, writing abstraction drivers > around it is very painful. Something we can agree on! PDO was never the right solution to any problem, and had the time been spent on bringing the ADOdb accelerator code into PHP properly I can't help feeling we would have something much better today. I still use ADOdb and have since day one, and cringe when people ask why it hasn't been replaced by PDO ... when I can run the same test suite in ADOdb using a native and the equivalent PDO driver then things may be better, but you still need ADOdb to handle the SQL abstraction anyway. -- 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