Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110777
MIME-Version: 1.0
References: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
 <CAGgaK7LP5foae=zV7gKPhax4Sgp1D6BtQwPmwbe3CpPjpwqi+A@mail.gmail.com>
In-Reply-To: <CAGgaK7LP5foae=zV7gKPhax4Sgp1D6BtQwPmwbe3CpPjpwqi+A@mail.gmail.com>
Date: Mon, 29 Jun 2020 16:13:24 +0200
Message-ID: <CAHRtwKbu0f6tN63RByFhWrgPKivihpdCW9maEW9QEDx1+j3n0A@mail.gmail.com>
To: Max Semenik <maxsem.wiki@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001b7ebd05a939aa11"
Subject: Re: [PHP-DEV] [RFC] Property write visibility
From: andre.romcke@gmail.com (=?UTF-8?B?QW5kcsOpIFLDuG1ja2U=?=)

--0000000000001b7ebd05a939aa11
Content-Type: text/plain; charset="UTF-8"

>
>
>> I agree that there is a use case for it, however I don't think the
> proposed syntax `public:private` is intuitive. Maybe we can come up with
> something better?
>

Would something closer to Swift be better? If so I expanded the RFC with
that syntax option as well:

class User {
    public private(set) int $id;
    public protected(set) string $name;

    public function __construct(int $id, string $name) {
        $this->id = $id;
        $this->name = $name;
    }}

--0000000000001b7ebd05a939aa11--