Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110029
To: Maciej Sobaczewski <sobak@php.net>, internals@lists.php.net,
 Nikita Popov <nikita.ppv@gmail.com>
References: <CAF+90c8m-CB3ZxAHeoOJVxJGhysLfZqpz3mq475GPnMEDA6iqQ@mail.gmail.com>
 <65803616-5117-e9f2-ba31-f2f8c323dfe9@php.net>
Message-ID: <efa9a260-1ce8-a84b-32fc-7cd45454c274@gmx.de>
Date: Wed, 6 May 2020 09:43:51 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <65803616-5117-e9f2-ba31-f2f8c323dfe9@php.net>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [RFC] Named arguments
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 06.05.2020 at 08:25, Maciej Sobaczewski wrote:

> I'm on the fence when it comes to the feature itself so I will skip that
> part entirerly but I'd like to draw attention to one more problem. Many
> PHP Manual translations translate the parameter names, too - both in
> text, as well as in the function/method signatures themselves.
>
> We would need to fix every such occurence for every language (at least
> active ones but there are still couple of them). Otherwise documentation
> will become highly misleading.
>
> Most people probably use IDEs of course but it still doesn't change the
> fact that the manual cannot be totally out of sync with what could
> become the language syntax.

I hope that we will be able to generate the <methodsynopsis> elements
automatically from the stubs (which would likely require some more
meta-information in the doc blocks).  These could then automatically be
injected into the docs.  Of course, someone would have to contribute the
required scripts. :)

=2D-
Christoph M. Becker