On 13 July 2015 at 13:23, Lester Caine <les...@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/
