Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78400 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80763 invoked from network); 27 Oct 2014 18:31:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Oct 2014 18:31:49 -0000 Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.218.53 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 209.85.218.53 mail-oi0-f53.google.com Received: from [209.85.218.53] ([209.85.218.53:63879] helo=mail-oi0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 99/C4-56216-49F8E445 for ; Mon, 27 Oct 2014 13:31:48 -0500 Received: by mail-oi0-f53.google.com with SMTP id v63so3802007oia.40 for ; Mon, 27 Oct 2014 11:31:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=wm34d+eqD86KUPKMjjOiP73z9l76jMkB9TCoj86olSw=; b=OnqAOVl8uDddCtcaUX/p2jKA94F6j+Qsi9NoktAY7AGjBwUfcBRZU7eaopT6CoA+2N YhNv9FKtMypPnVJcl6C4og5Rmr2ZjLK3oK8YjnFn8ztGnk5cpfaW7n+piOIe/r4bOxHw cNIZlwPDIG83okrLXyV/91EprSDX0tb802FlrxLGZ09F70LDkcJgDdDIP20T0EfSed/n HE2XurNF2ZJIr1ILTvkD/hGaPEk3lFnYuuX2IzF0jzzVDedVPCKLC1Ih0WTSYfC4b2j1 DlucUoIjtY/kzp2lKLS5kgUsCDMWhgR65hCeqQwnPtaaIKrCxMDAKvCMSR9xl5pQsLBA Ywfw== X-Gm-Message-State: ALoCoQn6GzJhdwKDxzA5X0VaDa8VMSBGiSgehTKvLF9z2FS0Pa9nYzfdp+njafsY4ECsLfpSjjslwBjm89pm5v3ea/px90Oh/m0pKH7drxY3HrQzSKfZ+zvS1BRnI988pCAcvEMcTQpgaA9evi1zmoyCXjira0mclw== MIME-Version: 1.0 X-Received: by 10.182.171.1 with SMTP id aq1mr3032534obc.64.1414434705742; Mon, 27 Oct 2014 11:31:45 -0700 (PDT) Received: by 10.60.70.41 with HTTP; Mon, 27 Oct 2014 11:31:45 -0700 (PDT) In-Reply-To: <6E04B9BE-854E-4112-8C74-7D90BD8BFE95@ajf.me> References: <6E04B9BE-854E-4112-8C74-7D90BD8BFE95@ajf.me> Date: Mon, 27 Oct 2014 22:31:45 +0400 Message-ID: To: Andrea Faulds Cc: PHP Internals Content-Type: multipart/alternative; boundary=e89a8ff1ca0431b35c05066bbe31 Subject: Re: [PHP-DEV] [RFC] Readonly Properties From: dmitry@zend.com (Dmitry Stogov) --e89a8ff1ca0431b35c05066bbe31 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Andrea, I don't have strong opinion about this proposal. It doesn't make any harm to the engine, and it really may speed-up code especially written for read-only properties. On the other hand you introduce new orthogonal to private/protected/public visibility rule, and I'm not sure if this complication is good for language. Why did you disable read-only static methods? (I just didn't get it). Thanks. Dmitry. On Fri, Oct 24, 2014 at 3:36 AM, Andrea Faulds wrote: > Good evening once again, > > Here=E2=80=99s another RFC: https://wiki.php.net/rfc/readonly_properties > > It proposes, with a working implementation, a modifier for properties tha= t > makes them readable and writeable from different scopes. > > Since I am a big proponent of including specification patches in new RFCs= , > I have decided to put my money (or rather, time) where my mouth is and I > have actually written a specification patch before writing an RFC. I woul= d > love to see this become the new standard for RFCs affecting the language. > > If you are curious at all about the behaviour, I suggest perusing the > fairly comprehensive set of twelve tests included in the main patch to > php-src. > > Thanks! > -- > Andrea Faulds > http://ajf.me/ > > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --e89a8ff1ca0431b35c05066bbe31--