Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63661 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7390 invoked from network); 27 Oct 2012 08:01:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Oct 2012 08:01:48 -0000 Authentication-Results: pb1.pair.com header.from=php@bof.de; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=php@bof.de; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain bof.de designates 80.242.145.70 as permitted sender) X-PHP-List-Original-Sender: php@bof.de X-Host-Fingerprint: 80.242.145.70 mars.intermailgate.com Received: from [80.242.145.70] ([80.242.145.70:59044] helo=mars.intermailgate.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F7/67-51104-9E49B805 for ; Sat, 27 Oct 2012 04:01:46 -0400 Received: (qmail 14858 invoked by uid 1009); 27 Oct 2012 10:01:41 +0200 Received: from 209.85.223.170 by mars (envelope-from , uid 89) with qmail-scanner-1.25-st-qms (clamdscan: 0.96.2/15512. spamassassin: 3.3.1. perlscan: 1.25-st-qms. Clear:RC:1(209.85.223.170):. Processed in 0.096725 secs); 27 Oct 2012 08:01:41 -0000 X-Antivirus-MYDOMAIN-Mail-From: php@bof.de via mars X-Antivirus-MYDOMAIN: 1.25-st-qms (Clear:RC:1(209.85.223.170):. Processed in 0.096725 secs Process 14850) Received: from mail-ie0-f170.google.com (gmail@bof.de@209.85.223.170) by mars.intermailgate.com with RC4-SHA encrypted SMTP; 27 Oct 2012 10:01:41 +0200 Received: by mail-ie0-f170.google.com with SMTP id c12so5638086ieb.29 for ; Sat, 27 Oct 2012 01:01:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.0.140 with SMTP id 12mr4442506ige.63.1351324899676; Sat, 27 Oct 2012 01:01:39 -0700 (PDT) Received: by 10.50.150.228 with HTTP; Sat, 27 Oct 2012 01:01:39 -0700 (PDT) Received: by 10.50.150.228 with HTTP; Sat, 27 Oct 2012 01:01:39 -0700 (PDT) In-Reply-To: <508AF476.9040804@sugarcrm.com> References: <508A67E6.2000405@zerocue.com> <508AF476.9040804@sugarcrm.com> Date: Sat, 27 Oct 2012 10:01:39 +0200 Message-ID: To: Stas Malyshev Cc: internals , Clint Priest Content-Type: multipart/alternative; boundary=e89a8f646e0d9f107504cd05d832 Subject: Re: [PHP-DEV] [RFC] Property Accessors v1.2 : Internal Accessor Method Visibility / Callability From: php@bof.de (Patrick Schaaf) --e89a8f646e0d9f107504cd05d832 Content-Type: text/plain; charset=ISO-8859-1 > > - i.e. name them __prop_get_xxx, __prop_set_xxx, and so on. > > I think it'd more natural to make it __set__PROPNAME. Though __set_state > is a static method, so maybe we can live with it - except that you won't > be able to declare property named $_state. Needing an "except" is inelegant, if it can be avoided up front. Also, having __prop_get_XXX etc. is a bit more descriptive to somebody later "wondering" what these methods are - prop alludes to properties, which is what the methods are about. I can already see the stack overflow subject, "what are these __prop methods in new PHP" :) best regards Patrick --e89a8f646e0d9f107504cd05d832--