Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110793 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 96616 invoked from network); 30 Jun 2020 12:36:41 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Jun 2020 12:36:41 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 477F41804E2 for ; Tue, 30 Jun 2020 04:25:35 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE 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: Received: from mail-vs1-f42.google.com (mail-vs1-f42.google.com [209.85.217.42]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 30 Jun 2020 04:25:34 -0700 (PDT) Received: by mail-vs1-f42.google.com with SMTP id e15so10983574vsc.7 for ; Tue, 30 Jun 2020 04:25:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=IDVDaqhmOvUiM5YhDLyCL0Md8hE6gSHFyPwqsr1bRUA=; b=V9lQU9R819zBUMWoP4LUCam74OCbntNDqx5HTDp4PtY3epkMGpHV5PA9Uqw1Hl/DIK /O2bLc1KY7Je7Cum/xC7K/l8BWiqO9b+aQIgYiOhvkaJnv4YYgHkWFJe+8s6NMcGk8tf ndOJU8BLF90KRDTir1n5P8QO6DuoMW1k83zigGy7exoV7ck7pkmFYAsPecwft3bGYSaX +qin6Aq8bLs74DJnVAb4XTvCDeVKRVzLiJRa7bKxykZsEH7a8B82MIlKdSQGg4y4B7y3 U1sFytn4v1nF+k05hFkJV8clXKP77ddSL0lvqmxmVAs41p4PDJAQ6O/ALIlI8aFwgJ+V +jpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=IDVDaqhmOvUiM5YhDLyCL0Md8hE6gSHFyPwqsr1bRUA=; b=Gf1/yzH6V80Jm7omEq/UCmiQwO6GJss2uH5gWppW3ycF/d6mrd+LycDYZ02mQOlSWh aoDtDIkPTtdReg+ybsjKJx8fpr8jsvIhFB/prTM9P/iued/LTDkqKBgnTs7I69jpDYxx UBbwT5HI7kSKni83QBCdjfUPtfE6v2OPgsrRedVxqkSxne2im6cGHZRTYMcEvHedTDKw /e6HvsbGysYKyKYkFMfSAZm4nsBqerg28gZVuncv2LNBeQzBQ9uqki1joJaZv5U6eFWc Lh9C0PrrXUvBNcAvnvVvJg5RT6UdVp/ApKi3bVJ14GilIFvEu49x4eTVvJyihZK9Yozl 9IOg== X-Gm-Message-State: AOAM531byNjaJ5iB6FYKHcpWgIiFkGK3PSIOHXCM28PrMvILHgcLWjou /k+vX0hGxrHQON2iLcEo8yRQ3SI9HCo1CwEVm1Z4YA== X-Google-Smtp-Source: ABdhPJwYOtSjJQ+s3jPhgcXXZiHUd4Mx2zgbj+AdvjFSLsiglVFE1P1PiwbiIFoRvAmhZwY+TqqwCTvEWPo+RXDZ9o4= X-Received: by 2002:a67:ecc4:: with SMTP id i4mr13178590vsp.228.1593516332219; Tue, 30 Jun 2020 04:25:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 30 Jun 2020 12:25:21 +0100 Message-ID: To: =?UTF-8?B?QW5kcsOpIFLDuG1ja2U=?= Cc: PHP Internals List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Property write visibility From: Danack@basereality.com (Dan Ackroyd) On Mon, 29 Jun 2020 at 10:42, Andr=C3=A9 R=C3=B8mcke wrote: > > I'd like to start discussion on a new RFC proposing a way to be able to > (optionally) specify property > write visibility, separate from read: > > https://wiki.php.net/rfc/property_write_visibility > From the RFC: "Attempting to pass a property value outside of allowed writable scope as a reference, results in an error." This part could probably do with having some details for it. Also, any implementation of that rule might need to be checked for performance issues. cheers Dan Ack