Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63421 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 896 invoked from network); 15 Oct 2012 16:03:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Oct 2012 16:03:39 -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.80 as permitted sender) X-PHP-List-Original-Sender: cpriest@zerocue.com X-Host-Fingerprint: 74.115.204.80 relay-hub206.domainlocalhost.com Received: from [74.115.204.80] ([74.115.204.80:48190] helo=relay-hub206.domainlocalhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7F/7A-42204-9D33C705 for ; Mon, 15 Oct 2012 12:03:39 -0400 Received: from MBX202.domain.local ([169.254.169.44]) by HUB206.domain.local ([192.168.68.50]) with mapi id 14.02.0283.003; Mon, 15 Oct 2012 12:02:43 -0400 To: Levi Morrison CC: Etienne Kneuss , "internals@lists.php.net" Thread-Topic: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2 : Interfaces Thread-Index: Ac2qzmY/IrEbFiHmS8CRVRSeKx1+9gALDjGAAAenA5D//84PgIAAPMQw///LEgD//9RQfw== Date: Mon, 15 Oct 2012 16:02:42 +0000 Message-ID: <56FF073D-826C-444F-8843-9739E568919E@zerocue.com> References: <9570D903A3BECE4092E924C2985CE485612B6466@MBX202.domain.local> <9570D903A3BECE4092E924C2985CE485612B655A@MBX202.domain.local> <9570D903A3BECE4092E924C2985CE485612B6654@MBX202.domain.local>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: 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 : Interfaces From: cpriest@zerocue.com (Clint Priest) Because fundamentally interfaces are designed to explain a way of communica= ting and properties are symmetrical and non-observable. The implementing class cannot "know" when a property has changed. -Clint On Oct 15, 2012, at 9:37 AM, "Levi Morrison" wrot= e: >> I *think* we are on the same page here, though I'm not sure what 'user' = is referring to (user of interface "implementer") or (user of class B). In= any case, I don't believe that your class B would be allowed at present, b= ut if it is, then it should not be allowed because defining a property to s= atisfy the requirements of an accessor is not right. >=20 > According to whom? In my opinion, not allowing a property to satisfy > the requirement of an accessor is wrong.