Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110781
MIME-Version: 1.0
References: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
 <CAGgaK7LP5foae=zV7gKPhax4Sgp1D6BtQwPmwbe3CpPjpwqi+A@mail.gmail.com>
 <CAHRtwKbu0f6tN63RByFhWrgPKivihpdCW9maEW9QEDx1+j3n0A@mail.gmail.com>
 <5ef9f918.1c69fb81.58a86.e504SMTPIN_ADDED_MISSING@mx.google.com> <CADK1yXLFzqGcxHS4a0ow9Fwnb3MND1ujRG=R5-GDvt4KOOtVGg@mail.gmail.com>
In-Reply-To: <CADK1yXLFzqGcxHS4a0ow9Fwnb3MND1ujRG=R5-GDvt4KOOtVGg@mail.gmail.com>
Date: Mon, 29 Jun 2020 12:16:32 -0300
Message-ID: <CAEsg9X0QPFfZtOuDNX0m+iG033WU2OEDWj1-t6PLHiCfQWLThA@mail.gmail.com>
To: Deleu <deleugyn@gmail.com>
Cc: Mark Randall <marandall@php.net>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000016f64d05a93a8cfd"
Subject: Re: [PHP-DEV] [RFC] Property write visibility
From: david.proweb@gmail.com (David Rodrigues)

--00000000000016f64d05a93a8cfd
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

With all possibilities maybe we have:

- public set:private unset:private isset:private get:private

set:private could be readed like "set is private".

Where:

- public is "general visibility" for set, unset, isset and get;
- set: affects write visibility;
- unset: affects unset() visibility;
- isset: affects isset() visibility;
- get: affects read visibility;

In this case, maybe we should think on possibility of usage like:

class A {
    get:public $x;
}

That determines that $x is private, except by get.

In counterpart, I do not know if it makes sense for isset mode, because if
we have get:public, and $x is accessible, so it is isset by nature.


Atenciosamente,
David Rodrigues


Em seg., 29 de jun. de 2020 =C3=A0s 12:03, Deleu <deleugyn@gmail.com> escre=
veu:

> As a user, I would prefer the original proposed syntax `public:private` o=
r
> the Swift syntax `public private(set)` than the alternative syntax `publi=
c
> int $x {protected set; protected unset;}`.
>
> On Mon, Jun 29, 2020 at 4:22 PM Mark Randall <marandall@php.net> wrote:
>
> > On 29/06/2020 15:13, Andr=C3=A9 R=C3=B8mcke wrote:
> > > Would something closer to Swift be better? If so I expanded the RFC
> with
> > > that syntax option as well:
> >
> > Borrowing from the various accessors RFCs:
> >
> > public int $x {
> >    protected set;
> >    protected unset;
> > }
> >
> > Then a future RFC can build upon it by adding the override functions
> > while keeping the same base syntax.
> >
> > Mark Randall
> >
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: https://www.php.net/unsub.php
> >
> >
>
> --
> Marco Aur=C3=A9lio Deleu
>

--00000000000016f64d05a93a8cfd--