Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60230 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89081 invoked from network); 20 Apr 2012 13:13:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Apr 2012 13:13:48 -0000 X-Host-Fingerprint: 208.107.13.98 host-98-13-107-208.midco.net Date: Fri, 20 Apr 2012 09:13:47 -0400 Received: from [208.107.13.98] ([208.107.13.98:15926] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 20/B3-63732-B01619F4 for ; Fri, 20 Apr 2012 09:13:47 -0400 Message-ID: <20.B3.63732.B01619F4@pb1.pair.com> To: internals@lists.php.net References: <9570D903A3BECE4092E924C2985CE485546B0737@MBX202.domain.local> User-Agent: slrn/pre1.0.0-18 (Linux) X-Posted-By: 208.107.13.98 Subject: Re: [PHP-DEV] RFC: Property get/set syntax From: weierophinney@php.net (Matthew Weier O'Phinney) On 2012-04-20, Christoph Hochstrasser wrote: > Hi, > > Are the dashes acceptable or undesirable? > > I think without dashes it is more in line with other keywords, like > "instanceof" or "insteadof". > > Because keywords are not case sensitive, one who likes them to be more > readable could write them camelCased, for example "readOnly", or > "writeOnly". If they are to be keywords, I'd argue we should use the dash variant -- the reason being that with the dash, there can be no conflict with existing constant, variable, or function names. I know I've had a fair number of each named both "readonly" and "writeonly". -- Matthew Weier O'Phinney Project Lead | matthew@zend.com Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc