Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:3166 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11224 invoked by uid 1007); 2 Jul 2003 14:37:34 -0000 Message-ID: <20030702143734.11223.qmail@pb1.pair.com> To: internals@lists.php.net Reply-To: "l0t3k" Date: Wed, 2 Jul 2003 10:37:49 -0400 Lines: 17 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Posted-By: 68.158.43.189 Subject: PHP5 - OO extensions and naming conventions. From: cshmoove@bellsouth.net ("l0t3k") IIRC there was an informal consensus to use studlyCaps as the official userland convention for OOP extensions (*) (leaving aside the case insensitivity of the language.) my question now concerns accessors. should we prefer properties over propertyGet()/propertySet() accessor functions ? would having both constitute bloat. i ask because im implementing a series of classes mirroring those in the Caffeinated Language (tm) so familiarity could be an asset. l0t3k (*) i wonder if this should be more formalized before the next major release. major extensions like dom/xsl are already using the current method->function_ name() convention.