Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110030
MIME-Version: 1.0
References: <CAF+90c8m-CB3ZxAHeoOJVxJGhysLfZqpz3mq475GPnMEDA6iqQ@mail.gmail.com>
 <65803616-5117-e9f2-ba31-f2f8c323dfe9@php.net>
In-Reply-To: <65803616-5117-e9f2-ba31-f2f8c323dfe9@php.net>
Date: Wed, 6 May 2020 09:50:57 +0200
Message-ID: <CAEPJdunBi5Ri+Oby-VAZnnoF8FJSWFREr98PGbR-MjHo1T1n=g@mail.gmail.com>
To: Maciej Sobaczewski <sobak@php.net>
Cc: PHP Internals <internals@lists.php.net>, Nikita Popov <nikita.ppv@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ef07a305a4f60626"
Subject: Re: [PHP-DEV] Re: [RFC] Named arguments
From: kontakt@beberlei.de (Benjamin Eberlei)

--000000000000ef07a305a4f60626
Content-Type: text/plain; charset="UTF-8"

On Wed, May 6, 2020 at 8:25 AM Maciej Sobaczewski <sobak@php.net> wrote:

> Hi Nikita!
>
> W dniu 05.05.2020 o 15:51, Nikita Popov pisze:
> > Hi internals,
> >
> > I've recently started a thread on resurrecting the named arguments
> proposal
> > (https://externals.io/message/109549), as this has come up tangentially
> in
> > some recent discussions around attributes and around object ergonomics.
> >
> > I've now updated the old proposal on this topic, and moved it back under
> > discussion: https://wiki.php.net/rfc/named_params
> >
> > Relative to the last time I've proposed this around PHP 5.6 times, I
> think
> > we're technically in a much better spot now when it comes to the support
> > for internal functions, thanks to the stubs work.
> >
> > I think the recent acceptance of the attributes proposal also makes this
> a
> > good time to bring it up again, as phpdoc annotations have historically
> had
> > support for named arguments, and this will make migration to the
> > language-provided attributes smoother.
> >
> > Regards,
> > Nikita
> >
>
>
> 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.
>

Can you give some examples? I checked a bunch of common functions in
ext/standard, DateTime and PDO and all languages except Turkish seem to use
exactly the same argument names as the english manual. Maybe there are
individual runaways?

In any case, the Turkish manual would have to change. It is misleading
anyways, because for each of these ReflectionParameter::getName() would
return the actual parameter name at runtime.

>
> 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.
>
> Cheers,
> Maciej.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--000000000000ef07a305a4f60626--