Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64705 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1293 invoked from network); 8 Jan 2013 21:51:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jan 2013 21:51:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=listas@rafaeldohms.com.br; spf=fail; sender-id=fail Authentication-Results: pb1.pair.com header.from=listas@rafaeldohms.com.br; sender-id=fail Received-SPF: fail (pb1.pair.com: domain rafaeldohms.com.br does not designate 209.85.220.180 as permitted sender) X-PHP-List-Original-Sender: listas@rafaeldohms.com.br X-Host-Fingerprint: 209.85.220.180 mail-vc0-f180.google.com Received: from [209.85.220.180] ([209.85.220.180:55781] helo=mail-vc0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 41/07-16636-0D49CE05 for ; Tue, 08 Jan 2013 16:51:12 -0500 Received: by mail-vc0-f180.google.com with SMTP id p16so935419vcq.11 for ; Tue, 08 Jan 2013 13:51:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=WELQq9tLSf/JvkwRa02IgooM9fGbkqEmtvPwPCTU3Mw=; b=JYJbp+dgBXFndqLNvcdqfjd4W/vMSZ2cf393eVM0pMeSy0zOJPtGNij03agufjZuWj a1xzIjspgkdgrG5OtmBj5W1wKOzuroBCP/fWsuky5a+d6kkHX/9VinSnePlsnk3HWraZ WIKeh44D0qmKWeBdxlKivP9QW7Gx0gg5PJ/XJVW1Rcl+ruKVVaqtLLA+AZbPLzbZx0zn ydYViPNbD2eVQcdzz1KzXd62y3SeK/Tn7lWVNxv2l29/pvFMTepSo75mFKOXgzpOZr7d M1XIjPYyvGEOjdYTjpjgxtZ7nxjm1rTDbmf2BlJJdazUy3UJ7TIZcSDpE1CfftbK/oMC D3Kg== MIME-Version: 1.0 Received: by 10.58.134.16 with SMTP id pg16mr6391287veb.12.1357681869187; Tue, 08 Jan 2013 13:51:09 -0800 (PST) Received: by 10.220.58.207 with HTTP; Tue, 8 Jan 2013 13:51:08 -0800 (PST) In-Reply-To: <50EC917C.3070805@sugarcrm.com> References: <50EBDEEE.8070605@sugarcrm.com> <50EC6569.6030202@sugarcrm.com> <50EC917C.3070805@sugarcrm.com> Date: Tue, 8 Jan 2013 22:51:08 +0100 Message-ID: To: Stas Malyshev Cc: Pierre Joye , Pierrick Charron , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e0129492087e95704d2cdf16c X-Gm-Message-State: ALoCoQnWKcqs3oclVyhX78uRr6X2553xwrpR8AmqTQREISolQWcY0yt9tI/KphgNf14p2/dHqCmq Subject: Re: [PHP-DEV] [RFC] Reflection annotations reader From: listas@rafaeldohms.com.br (Rafael Dohms) --089e0129492087e95704d2cdf16c Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 8, 2013 at 10:37 PM, Stas Malyshev wrote: > Hi! > > > Everyone I talked to who implemented annotations in docblocks did it > > as hack because there is no native support. This is not something that > > belongs to docblocks. It would be nice if you could take a look at the > > c# doc, there are really good concepts there. > > I know why they did it, and we already discussed that stuff in the last > annotation discussion. What I mean here is that presenting it as if the > notion of meaningful comments is completely unheard of in PHP and nobody > expects it is just wrong. Maybe it was so years ago, but it is > definitely not true now - de-facto meaningful comments *are* the > standard now, and have a lot of use, and nobody with any experience is > surprised by them. Regardless of *why* is it so, it is a fact. > > Stas, That still does not make it the right place. Annotations went into docblocks because it was the only place reflection could provide the needed information at runtime. Just because we now treat docblocks as 1st class citizens does not mean annotations should be there. Does that mean that annotations should be in docblocks and not in core for the reason of "we all know docblocks exist". I would seriously expect at the very least a stronger reason. These were some of the ones i heard before: 1. The syntax is crap: this is solvable, let's find the right syntax 2. PHP does not need it: i think we have proven the use already, every major FW has a implementation of this, there is clearly demand. So if we are going to get anywhere with this discussion I suggest getting back to the original RFC and working on solving the issues instead of discussing developer folklore. -- Rafael Dohms PHP Evangelist and Community Leader http://doh.ms http://wwwamsterdamphp.nl --089e0129492087e95704d2cdf16c--