Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116599
MIME-Version: 1.0
References: <02ba01d7ecbc$c0e13370$42a39a50$@webkr.de> <61b198a6.1c69fb81.e6b7e.7577SMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <61b198a6.1c69fb81.e6b7e.7577SMTPIN_ADDED_MISSING@mx.google.com>
Date: Thu, 9 Dec 2021 10:19:27 +0100
Message-ID: <CADK1yXJo-_bVEFN02Xckv+aejQ4z6=6rboikoWtAGbDQpS-shQ@mail.gmail.com>
To: Mark Randall <marandall@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008ca41505d2b31cb8"
Subject: Re: [PHP-DEV] Re: Allow default parameters before non-default ones?
From: deleugyn@gmail.com (Deleu)

--0000000000008ca41505d2b31cb8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 9, 2021 at 6:48 AM Mark Randall <marandall@php.net> wrote:

> On 09/12/2021 05:22, Andr=C3=A9 H=C3=A4nsel wrote:
> > This is very useful because I can add an optional parameter to a functi=
on
> > and prevent users of my function from using the parameter in a position=
al
> > way. This way I don't have to make a compatibility promise to never
> change
> > the position of this parameter.
>
>
> I would much prefer we could find a way to give this proper support
> rather than a hack.
>
> I frequently use large numbers of named arguments and would very much
> like to be able to knock out the ability to use positional arguments,
> thus ensuring I can change the order (e.g. inserting a new argument
> after a related one) without a BC break.
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>
If this were to happen, would it be an attribute to be added to the
functions, a new keyword to declare named-parameter functions only or a
different way to declare parameters? Are there other options?

--=20
Marco Aur=C3=A9lio Deleu

--0000000000008ca41505d2b31cb8--