Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87140
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <55A3ADD5.1080106@lsces.co.uk>
References: <CAObuZdsA6T7uTCPignr_9g1bAbd83hsTrv9mAg7jU=oY96C9+Q@mail.gmail.com>
 <CALW=WECOo-JDWgHbmy=eUAVWCxt-0m_9sP-JeXe1hc0SokH37w@mail.gmail.com>
 <55A16375.4000707@php.net> <CAOsHV+sV2p7aBWOro=D5+xV+LZvNrt4Au3R3SqcJDy9qdPj8ig@mail.gmail.com>
 <55A220D8.3090004@gmail.com> <CAOsHV+tEjzAnG4ygRj1=0JgO4ps4AbWFQVHFex0+GuY44rdZbA@mail.gmail.com>
 <55A363A0.5060307@gmail.com> <CAEZPtU6+PNos4Cg8EwZjgL=ZJ0y-h_UWxAkKGsmWMJJS_QjYWA@mail.gmail.com>
 <55A39493.6020909@lsces.co.uk> <CADyq6s+T-79iKjNOCeWgpPe=cocEkoEYAqpK5vEWo9WPErVW1Q@mail.gmail.com>
 <55A39F18.70308@lsces.co.uk> <CADyq6s+HVkM0Ftq6d+9j8DvqhSQvSG=uBurXd+tnp2OLhvbyLg@mail.gmail.com>
 <55A3ADD5.1080106@lsces.co.uk>
Date: Mon, 13 Jul 2015 13:33:01 +0100
Message-ID: <CADyq6sJ-fr+sEDdq=KrD3DA-Lvfxm7b=KqH7+eiZtOBtmwN=pQ@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d041824f24eadfe051ac0ed94
Subject: Re: [PHP-DEV] PHP7 and types - and alternatives to annotation
From: ocramius@gmail.com (Marco Pivetta)

--f46d041824f24eadfe051ac0ed94
Content-Type: text/plain; charset=UTF-8

On 13 July 2015 at 13:23, Lester Caine <lester@lsces.co.uk> wrote:

> On 13/07/15 13:12, Marco Pivetta wrote:
> > It's actually the PhpDocumentor folks (and Mike van Riel in first place)
> > pushing forward PSR-5: there's nothing more "official" than that right
> now.
> > That's the current standardization path.
>
> docblock annotation has been the subject of RFC's as alternatives to
> other annotation/typing options, and that is the correct platform to
> carry out that debate rather than on third party tools/standards such as
> fig and phpdocumentor.


Yeap, and these RFCs were rejected due to the fact that for the purposes of
php-src it's just comments that can be read as strings via Reflection API.


> It is not only phdocumentor that uses docblock
> material, the IDE's I use have no problem with the current docblock
> material and so there has been no need until now to look at why only
> phpdocumentor2 has a problem with them ...


Most (all?) of those APIs/IDEs/tools are basing their implementation on
PHPDocumentor's documentation at
http://www.phpdoc.org/docs/latest/index.html, if not directly on
PHPDocumentor's components.

Not everything in PHP is specified by php-src, nor should be.
Actually, pretty much nothing in PHP userland is specified by php-src, and
it's probably for the best, since this way you get a choice.

In this case you have a simple choice:
 - not upgrading a stable tool
 - accepting that there are BC breaks due to the evolution of the ecosystem
in the past 10 years, and adapting an old codebase to 10 years of changes

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--f46d041824f24eadfe051ac0ed94--