Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63548 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65520 invoked from network); 19 Oct 2012 23:08:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Oct 2012 23:08:27 -0000 Authentication-Results: pb1.pair.com header.from=cpriest@zerocue.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=cpriest@zerocue.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zerocue.com designates 74.115.204.41 as permitted sender) X-PHP-List-Original-Sender: cpriest@zerocue.com X-Host-Fingerprint: 74.115.204.41 relay-hub205.domainlocalhost.com Received: from [74.115.204.41] ([74.115.204.41:5132] helo=relay-hub205.domainlocalhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2D/47-22055-A6DD1805 for ; Fri, 19 Oct 2012 19:08:26 -0400 Received: from MBX214.domain.local ([fe80::cd17:7c48:f248:828e]) by HUB205.domain.local ([192.168.68.49]) with mapi id 14.02.0283.003; Fri, 19 Oct 2012 19:07:21 -0400 To: "internals@lists.php.net" Thread-Topic: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords Thread-Index: Ac2uToWHS3qoQEyGSzmw4/EGCBpx3g== Date: Fri, 19 Oct 2012 23:07:21 +0000 Message-ID: <9570D903A3BECE4092E924C2985CE485612C2595@MBX214.domain.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.64.23] Content-Type: multipart/alternative; boundary="_000_9570D903A3BECE4092E924C2985CE485612C2595MBX214domainloc_" MIME-Version: 1.0 Subject: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords From: cpriest@zerocue.com (Clint Priest) --_000_9570D903A3BECE4092E924C2985CE485612C2595MBX214domainloc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I had thought of a deviation on some of the ideas presented to get rid of r= ead-only/write-only while still keeping the ability to maintain their effec= t, if we so decide that the feature is wanted. Here it is: class TimePeriod { private $Seconds; public $Hours { get() { return $this->Hours; } final set NULL; } } It's close to what's been suggested but is pretty clear that there IS NO SE= TTER it could not be called within the class and since its final it cannot = be over-ridden. I've included this in the change tracking document. Thoughts? -Clint --_000_9570D903A3BECE4092E924C2985CE485612C2595MBX214domainloc_--