Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126101
Precedence: bulk
MIME-Version: 1.0
References: <CAOrgP8v0AGF10JGep-YaqC+w73gAjewUwjRN8-AbxmO3wG-iJA@mail.gmail.com>
 <CAGS0MVAJQ=J-EZWbmtamqrr-35icEjrEZv+5cZRpCqT=1_Yf6A@mail.gmail.com>
In-Reply-To: <CAGS0MVAJQ=J-EZWbmtamqrr-35icEjrEZv+5cZRpCqT=1_Yf6A@mail.gmail.com>
Date: Wed, 4 Dec 2024 14:41:40 -0300
Message-ID: <CAEwRQKam-4R1_6z4nq8davqvB8ibMBEsUEPo05QQZYgfgUSa8g@mail.gmail.com>
Subject: Re: [PHP-DEV] Multiple property assigning without constructor
To: Erick de Azevedo Lima <ericklima.comp@gmail.com>
Cc: Taras Chornyi <taras.chr@gmail.com>, internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
From: carlosv775@gmail.com (Vinicius Dias)

> But often classes need constructors only to set properties. In such cases, constructors become redundant.

Actually, the behavior is not the same and the constructors are not redundant.

Taking your example:
```
class Person
{
    public string $firstName;
    public int $age;
}

$person = new Person {
   firstName: "John",
   age: 42
};
```

This would allow the following:
```
$invalidPerson = new Person();
```

Now we have a person without name or age. But with constructors we
make sure that the object is always in a valid state:

```
class Person
{
    public function __construct(public string $firstName, public int $age)
    { }
}

$validPerson = new Person('Name', 40);
$invalidPerson = new Person(); // this is impossible. every person
needs firstName and age
```

I just wanted to point that out. :-)