On Sat, Jan 24, 2015 at 7:42 AM, Rowan Collins <rowan.coll...@gmail.com> wrote: > On 24 January 2015 11:09:04 GMT, Robert Stoll <p...@tutteli.ch> wrote: > >>Besides, pretty much the same impact has the return type RFC now, >>because the manual should be updated accordingly to reflect the new >>syntax IMO. Sounds like lot of work but it should be possible to >>migrate the docs with a tool. > > As I said in another thread, updating the manual is nothing at all like > changing the language. It is a single, centrally-controlled set of content, > which doesn't have to be compatible with multiple environments, and has a > minimum requirement of internal consistency which has been met in some cases > with arbitrary conventions unrelated to the language. It may even be possible > to change the notation without changing the source, by altering the output > templates, but if not, an automated change to use a new convention more > similar to new language syntax is a no-brainer.
Assuming that we are using well-formed DocBook for the methodsynopsis (which at a glance we seem to do) then hopefully the doc renderer can take care of the change. It will need to change to use a chunking function, which I'm not familiar with yet. I'm certainly willing to look into this. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
