Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123549
Message-ID: <a4bda42c-877f-49fd-bfb8-053575efe684@processus.org>
Date: Fri, 7 Jun 2024 21:48:23 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] RFC proposal : "new" keyword shorthand
To: Larry Garfield <larry@garfieldtech.com>,
 php internals <internals@lists.php.net>
References: <CAMuyDGP58tTGWiTN=e22x7A5DXxE7UTZ1X2No+zcf6sYUc4wmg@mail.gmail.com>
 <fa48b5a2-61d0-4019-a173-f353088edffb@processus.org>
 <652c1a66-6702-4009-a4a0-d2221df00f69@app.fastmail.com>
Content-Language: fr-FR, en-US
In-Reply-To: <652c1a66-6702-4009-a4a0-d2221df00f69@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: pierre-php@processus.org (Pierre)

Le 07/06/2024 à 21:38, Larry Garfield a écrit :
> On Fri, Jun 7, 2024, at 7:20 PM, Pierre wrote:
>
>> I sincerely do not want to see a new operator for replacing the "new"
>> operator, because then we would have two different syntaxes which would
>> be semantically equivalent.
>>
>> Creating a new object, in most API design, is not something you do very
>> often, especially when working in a framework that does it for you
>> (dependency injection, etc...).
> This is not entirely true.  Creating a new service object, yes, you rarely never do that yourself.  Creating a new data object (value object, struct object, DTO, and a dozen other terms) is something that should happen more than most PHP developers currently do, because most of us have primitive obsession.  (Or array obsession.)
>
> Consider attributes: Any time you want to have an object as the value for one of the arguments to an attribute, you need a "new."  Any time you create a value object for a more strongly typed parameter than the horrid $options array, you'll be using "new."
>
> So I'm sympathetic to making that syntax easier, and would be OK with it if a workable syntax was found.  But so far in this thread, a workable syntax has not been found.
>
> I agree it's not the greatest usability concern in PHP right now, though.
>
> --Larry Garfield

I understand your point, but why replacing "new" which is basically an 
operator, with another operator ?

I do agree with you that when you use value objects, you need it a lot, 
but I'd much prefer having a JS like value objects initializer syntax, 
such as `Point {x: 1, y: 2}` syntax than creating another way to call 
the constructor, which already has a mastered and comprehensive syntax 
which is simply `new`.

As you said, it's not the greatest usability concern in PHP right now.

Pierre