Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118362
Return-Path: <rowan.collins@gmail.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 66462 invoked from network); 7 Aug 2022 08:33:09 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 7 Aug 2022 08:33:09 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id CEE3F1804BC
	for <internals@lists.php.net>; Sun,  7 Aug 2022 03:34:07 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,
	RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS15169 209.85.128.0/17
X-Spam-Virus: No
X-Envelope-From: <rowan.collins@gmail.com>
Received: from mail-wr1-f48.google.com (mail-wr1-f48.google.com [209.85.221.48])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Sun,  7 Aug 2022 03:34:07 -0700 (PDT)
Received: by mail-wr1-f48.google.com with SMTP id h13so7917655wrf.6
        for <internals@lists.php.net>; Sun, 07 Aug 2022 03:34:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20210112;
        h=content-transfer-encoding:mime-version:message-id:references
         :in-reply-to:user-agent:subject:to:from:date:from:to:cc;
        bh=Uy5pL0sl8/h33SiA/McM0Xfy8oJENfUSuhdGOkdJy9g=;
        b=eBCGyS64oEgMOjlteEmDg0HBJRqpQGGpjtA5a+GqbK00AyDl6CyKZ5ihYUCyRcA+gN
         v9g2H/RubN4W3ZDOWoiRiK7bel1N3FsEJj/ARUWuE4pZLwMuwErd13x+sPHLzU34ri3e
         PL8Vx9Sk+QMIlceu2ByERDsgkVgbbTPAXRRmu/lYKlDbHX+OPwJKbC3+8ZCgMpaEtD+I
         0bi3ZJBZI5pQn7xyA+ETN9g2Y8WitJaGmgDoJ4Eb6u9t1Av+OQ306KO78D8+TygeLPnu
         QW8f/w9XHTqxQTeeoEPB1EYJS8LRdIvhl3TmYPrWcCZJhqHFk2fw9WbK9HqC5p0dvrx1
         kF3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=content-transfer-encoding:mime-version:message-id:references
         :in-reply-to:user-agent:subject:to:from:date:x-gm-message-state:from
         :to:cc;
        bh=Uy5pL0sl8/h33SiA/McM0Xfy8oJENfUSuhdGOkdJy9g=;
        b=Nj6UQKW3MErfZiY3vUTn75pz3pkNs5m1/wbiTyTjk6OfkpyM+0l6F5tPvnSCcCazia
         X794C0pg8zrBrYu+N9xllUYHrAoEq49Q1FvL4u1Yvy6Bdyw4GC8xftxUpyQi/ENanv0L
         u3bAJslroVl+ZkqomYiRNQS818JFY036T1zLUe3XF+ZxF58+w00ETHrYz/3FK9j2mvdg
         utSdSOs5vSohpeDMs0k84X8Og7P3YdMNL9CZOCnz5Tg7EhbHH/Z7VSCY4MHu6CwqOtbX
         9xecH214l2oaLsvoILxidPU+dbhUBOyi6ZdF+qYeQpPLnrrBiFITcr93ntZkleCwZIr9
         q47Q==
X-Gm-Message-State: ACgBeo2qX9d3oUvkEoMpp8NOYiSxI4GRYgic7Kw3rqC0V290AieGkWw7
	BZSZfp7pGQXUE17zyWjHm5wlK6A7eQ4=
X-Google-Smtp-Source: AA6agR5FMPttkWcpkS6KzcOrC/QMHVSvh5cadvqiHhAg8tVcxApn9OPmkvZUrgPBOE7vQaN5wqbAug==
X-Received: by 2002:a05:6000:2ab:b0:21e:2e68:52f4 with SMTP id l11-20020a05600002ab00b0021e2e6852f4mr8420188wry.236.1659868446047;
        Sun, 07 Aug 2022 03:34:06 -0700 (PDT)
Received: from [127.0.0.1] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37])
        by smtp.gmail.com with ESMTPSA id n19-20020a05600c3b9300b003a38606385esm27777149wms.3.2022.08.07.03.34.04
        for <internals@lists.php.net>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Sun, 07 Aug 2022 03:34:05 -0700 (PDT)
Date: Sun, 07 Aug 2022 11:34:04 +0100
To: internals@lists.php.net
User-Agent: K-9 Mail for Android
In-Reply-To: <CAKxcST_Mu3qDKKLgtsBBVAm=6mLirhjZ-88f+jjWeNhWyzO16A@mail.gmail.com>
References: <ec4bc6e5-39ac-4a36-9d63-cca8dc6a29a6@www.fastmail.com> <CABdc3WqQ-kLTa3C=61_=yW-yJZuP2p_QW1TNe12WuHHur7aHng@mail.gmail.com> <e122e44f-550e-4089-8100-a27df9f8c9fa@www.fastmail.com> <CAKxcST_Mu3qDKKLgtsBBVAm=6mLirhjZ-88f+jjWeNhWyzO16A@mail.gmail.com>
Message-ID: <A78DA1F7-1F74-4A94-962C-0EA5979431AD@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Asymmetric visibility
From: rowan.collins@gmail.com (Rowan Tommins)

On 5 August 2022 21:04:34 BST, Paul Dragoonis <dragoonis@gmail=2Ecom> wrote=
:
>2=2E when I opened the RFC and looked at the syntax, I wasnt able to
>intuitively (self documenting code) figure out what and why was going on=
=2E
>
>3=2E The syntax is heavily implicit as to what each keyword and syntax me=
ans,
>so the general PHP developer would struggle or mis understand what is goi=
ng
>on=2E


Can you expand on where you think the ambiguity / implicitness is? As I un=
derstand it, the RFC is proposing exactly three new combined access levels:

- "public private(set)"
- "public protected(set)"
- "protected private(set)"

Although aesthetically it will take a bit of getting used to, it seems to =
me pretty clear that the first means "mostly public, but private if you wan=
t to set it", and so on=2E

The only thing I can think of that could be described as "implicit" is tha=
t accessing a property by reference is considered a "set" operation, which =
I'm not sure how any implementation could avoid=2E

Regards,

--=20
Rowan Tommins
[IMSoP]