Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119676
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-206-g57c8fdedf8-fm-20230227.001-g57c8fded
Mime-Version: 1.0
Message-ID: <1d94e66d-f329-41f1-895b-c36e191f133b@app.fastmail.com>
In-Reply-To: 
 <CAC_PL4zjupNSx_qx9cESuu5jKRx1uSDiaO2GQyCKMikmAKRr6g@mail.gmail.com>
References: 
 <CAC_PL4zjupNSx_qx9cESuu5jKRx1uSDiaO2GQyCKMikmAKRr6g@mail.gmail.com>
Date: Thu, 09 Mar 2023 10:30:13 -0600
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] Two Issues regarding Named Parameters; want to understand the
 technicality
From: larry@garfieldtech.com ("Larry Garfield")

On Wed, Mar 8, 2023, at 6:26 PM, Hamza Ahmad wrote:

> In my second project, I did not receive a warning when I passed the
> wrong parameters. To give you an example, I have two constructors:
> 1.   ` public function __construct(int $date, int$month, int $year) `
> 2.   ` public function __construct(string ...$names) `
> When I initialized the latter object with the former object's
> signature i.e., `new LatterObject(date: 1, month: 1, year: 1970);
> `, I did not receive a warning of passing the wrong parameters.

Is the code in strict mode?  If not, then that is the expected behavior.  You should get a $names array that has 3 associative keys, each with a numeric value that's been cast to a string.

In strict mode, I would expect that to give a TypeError, but not in weak mode.

--Larry Garfield