Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81083
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.41 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <4D7DEFFA-90BC-4117-956E-70B1A02A9C96@gmail.com>
References: <002601cff777$eb923430$c2b69c90$@tutteli.ch>
	<CAFMT4NqJDcek6itqAUt2iOyHd2icc-tDdWsEjiRYvG1YFcc5cw@mail.gmail.com>
	<000601cff80a$972e0250$c58a06f0$@tutteli.ch>
	<5458937F.9020304@sugarcrm.com>
	<CAPwsocFQHPDFBVtW5FBCGkz_cy-LB0AzJ48qYJ9zxafAh-G1LQ@mail.gmail.com>
	<545910F1.8030904@sugarcrm.com>
	<859A97F0-7C58-406A-857B-557F8AA657AD@ajf.me>
	<545917A2.6000206@lerdorf.com>
	<CAFMT4No6jp=KVQzRbWU7ZKBiLVtZekwmj45p-Up4EgLDyVf2ZA@mail.gmail.com>
	<545977E1.2060700@sugarcrm.com>
	<CAFMT4NrXXw9Tj2MwR47g9XpxtiuFDM00z3v1QQNTSEjmOfH2Mg@mail.gmail.com>
	<54599A0F.2060400@sugarcrm.com>
	<CAFMT4NqCJzPEFJHt4hokj2MOG-JPHBae_2eVfx_OAybJTkC8Rw@mail.gmail.com>
	<001801d037c6$2a7976c0$7f6c6440$@tutteli.ch>
	<4D7DEFFA-90BC-4117-956E-70B1A02A9C96@gmail.com>
Date: Sat, 24 Jan 2015 10:10:51 -0700
Message-ID: <CAFMT4Nq+Zmft2baqn5aYxoQJ4hTb1-pa4tDff3BaesSZCRHf2A@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: Robert Stoll <php@tutteli.ch>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Types on the right or on the left
From: levim@php.net (Levi Morrison)

On Sat, Jan 24, 2015 at 7:42 AM, Rowan Collins <rowan.collins@gmail.com> wr=
ote:
> On 24 January 2015 11:09:04 GMT, Robert Stoll <php@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 c=
hanging the language. It is a single, centrally-controlled set of content, =
which doesn't have to be compatible with multiple environments, and has a m=
inimum requirement of internal consistency which has been met in some cases=
 with arbitrary conventions unrelated to the language. It may even be possi=
ble to change the notation without changing the source, by altering the out=
put 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.