Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63589 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70483 invoked from network); 21 Oct 2012 15:34:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2012 15:34:10 -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.54 as permitted sender) X-PHP-List-Original-Sender: cpriest@zerocue.com X-Host-Fingerprint: 74.115.204.54 relay-hub202.domainlocalhost.com Received: from [74.115.204.54] ([74.115.204.54:30138] helo=relay-hub202.domainlocalhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C4/B3-22055-FE514805 for ; Sun, 21 Oct 2012 11:34:09 -0400 Received: from MBX202.domain.local ([169.254.127.11]) by HUB202.domain.local ([192.168.68.46]) with mapi id 14.02.0318.004; Sun, 21 Oct 2012 11:34:04 -0400 To: Levi Morrison CC: Nikita Popov , "internals@lists.php.net" Thread-Topic: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords Thread-Index: Ac2uToWHS3qoQEyGSzmw4/EGCBpx3gAZ7FCAAANTAQAAAzhVAAA8TcGAAAARlYAACBu8AA== Date: Sun, 21 Oct 2012 15:34:03 +0000 Message-ID: <9570D903A3BECE4092E924C2985CE4856140CF5D@MBX202.domain.local> References: <9570D903A3BECE4092E924C2985CE485612C2595@MBX214.domain.local> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.64.26] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords From: cpriest@zerocue.com (Clint Priest) I think that seems to be the consensus at this point, anyone disagree? > -----Original Message----- > From: Levi Morrison [mailto:morrison.levi@gmail.com] > Sent: Sunday, October 21, 2012 10:26 AM > To: Amaury Bouchard > Cc: Nikita Popov; Clint Priest; internals@lists.php.net > Subject: Re: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords >=20 > > If for some reason you need to enforce that nobody inherits it and > > sets the property, then declaring a setter and issuing an error or > > exception would suffice. >=20 > I meant to say declaring a `private or final setter`. Noticed that after= I sent it.