Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:167 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79795 invoked from network); 23 Mar 2003 04:51:20 -0000 Received: from unknown (HELO cs78146114.pp.htv.fi) (62.78.146.114) by pb1.pair.com with SMTP; 23 Mar 2003 04:51:20 -0000 Received: from localhost (jani@localhost) by cs78146114.pp.htv.fi (8.11.6/8.11.6) with ESMTP id h2N4pKK29073; Sun, 23 Mar 2003 06:51:20 +0200 X-Authentication-Warning: cs78146114.pp.htv.fi: jani owned process doing -bs Date: Sun, 23 Mar 2003 06:51:20 +0200 (EET) Sender: jani@cs78146114.pp.htv.fi Reply-To: Jani Taskinen To: Sterling Hughes cc: internals@lists.php.net In-Reply-To: <1048386150.848.1293.camel@hasele> Message-ID: References: <1048367260.848.1147.camel@hasele> <20030323090240my5O%!@at.wakwak.com> <1048376595.847.1158.camel@hasele> <1048386150.848.1293.camel@hasele> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] default exceptions, interfaces, etc. From: sniper@iki.fi (Jani Taskinen) On 22 Mar 2003, Sterling Hughes wrote: >On Sat, 2003-03-22 at 21:33, Derick Rethans wrote: >> On Sun, 22 Mar 2003, Sterling Hughes wrote: >> >> > On Sat, 2003-03-22 at 19:02, Moriyoshi Koizumi wrote: >> > > Hi, >> > > >> > > As per naming convention, I think it'd be nice if the methods were >> > > named as: >> > > >> > > getmessage => get_message >> > > getcode => get_code >> > > >> > > If those are corrected, +1 for this feature. >> > > >> > >> > I was thinking of that - I would personally prefer get_message() and >> > get_code() naming, but that goes against pear's naming conventions, and >> > I want this to integrate well with pear (as a base class.) >> >> It's a PHP function, not PEAR code, so it should follow the PHP naming >> style. >> > >As I mentioned to Marcus, there are no naming conventions for OO code, >only procedural code (in PHP). Also, compliance with PEAR is a >pragmatic solution, because presumably all their code will be inheriting >from Exception. The largest, and the official OO library should be >in-sync with standard practices (and we have none yet regarding OO >code.) Even if we don't have specific rules (yet) for OO stuff, IMO, it should follow the existing rules. --Jani