Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63476 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54656 invoked from network); 16 Oct 2012 23:44:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Oct 2012 23:44:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=cpriest@zerocue.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=cpriest@zerocue.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zerocue.com designates 74.115.204.40 as permitted sender) X-PHP-List-Original-Sender: cpriest@zerocue.com X-Host-Fingerprint: 74.115.204.40 relay-hub204.domainlocalhost.com Received: from [74.115.204.40] ([74.115.204.40:30404] helo=relay-hub204.domainlocalhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7B/1B-29764-941FD705 for ; Tue, 16 Oct 2012 19:44:10 -0400 Received: from MBX202.domain.local ([169.254.169.44]) by HUB204.domain.local ([192.168.68.48]) with mapi id 14.02.0283.003; Tue, 16 Oct 2012 19:43:11 -0400 To: Stas Malyshev , Jazzer Dane CC: "internals@lists.php.net" Thread-Topic: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2 Thread-Index: Ac2oOZ3+vAOzWRcnRpOb6a/hOVK5+ADZjV8AAADsVgAAAC/7AAAAqNSAAACJGIAAACxngAAA4ZuAABKEX5A= Date: Tue, 16 Oct 2012 23:43:11 +0000 Message-ID: <9570D903A3BECE4092E924C2985CE485612B785B@MBX202.domain.local> References: <9570D903A3BECE4092E924C2985CE485612B53E4@MBX202.domain.local> <507D24E0.9070203@sugarcrm.com> <507D2C54.6030702@sugarcrm.com> <507D3459.3020900@sugarcrm.com> <507D3B6D.1090308@sugarcrm.com> In-Reply-To: <507D3B6D.1090308@sugarcrm.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.64.21] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2 From: cpriest@zerocue.com (Clint Priest) Stas, go back a few "revisions" of the RFC and you'll see there used to be = automatically implemented accessors which were voted out. The current RFC = does not reflect the current "fork" of the code, it did before I modified i= t with the consensus from around 10/12 before Nikita brought up some more t= houghts on the subject. I believe the general idea of the changes is documented at the bottom of th= e document in the change list, but you're free to go back to previous versi= ons of the RFC. > -----Original Message----- > From: Stas Malyshev [mailto:smalyshev@sugarcrm.com] > Sent: Tuesday, October 16, 2012 5:48 AM > To: Jazzer Dane > Cc: Clint Priest; internals@lists.php.net > Subject: Re: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2 >=20 > Hi! >=20 > > Stas, the proposed "solution" thus far is to make the getter or setter > > final and private and not have a body. This would naturally throw an > > exception if it was accessed from anywhere but the class it was defined= . > > The class it was defined in has to remember that it is virtually a > > read/write only accessor. >=20 > What you mean by "not have a body" - is there special syntax for body-les= s methods introduced? Then it should be in the RFC. How > it is implemented - what exactly is stored in the function table then? >=20 > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227