Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60296 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71637 invoked from network); 24 Apr 2012 22:20:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Apr 2012 22:20:08 -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:15614] helo=relay-hub205.domainlocalhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 40/C2-54790-517279F4 for ; Tue, 24 Apr 2012 18:20:07 -0400 Received: from MBX202.domain.local ([169.254.19.147]) by HUB205.domain.local ([192.168.69.5]) with mapi id 14.01.0355.002; Tue, 24 Apr 2012 18:20:02 -0400 To: Stas Malyshev CC: "internals@lists.php.net" Thread-Topic: [PHP-DEV] RFC: Property get/set syntax (added isset/unset and references) Thread-Index: Ac0iFMmMOMpsT+bxSO2aogP0/HTvvQATR7eAAAGTzKA= Date: Tue, 24 Apr 2012 22:20:02 +0000 Message-ID: <9570D903A3BECE4092E924C2985CE48555BECE65@MBX202.domain.local> References: <9570D903A3BECE4092E924C2985CE48555BEC3C2@MBX202.domain.local> <4F96E3F1.2000005@sugarcrm.com> In-Reply-To: <4F96E3F1.2000005@sugarcrm.com> 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: Property get/set syntax (added isset/unset and references) From: cpriest@zerocue.com (Clint Priest) I will double-check (that it doesn't) but it should not per the spec, in th= e case of an interface this is not an automatic implementation but instead = a 'must-have' declaration, which could later become an automatic implementa= tion when defined within a class which implements that interface. -----Original Message----- From: Stas Malyshev [mailto:smalyshev@sugarcrm.com]=20 Sent: Tuesday, April 24, 2012 12:34 PM To: Clint Priest Cc: internals@lists.php.net Subject: Re: [PHP-DEV] RFC: Property get/set syntax (added isset/unset and = references) Hi! > These would also include automatic implementations which call the=20 > respective functions on the backing field. I could see only allowing=20 > isset/unset automatic implementations if get/set were also specified=20 > as automatic implementations. Another thing about that. The "automatic implementation" creates variable s= tarting with __. When exactly this happens - if all bodies are not defined?= Any of the bodies are not defined? What if I implement interface like this= : interface iSampleInterface { public $MyProperty { get; set; } } Does this produce automatic __MyProperty or not? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227