Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:156
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: Moriyoshi Koizumi <moriyoshi@at.wakwak.com>
Cc: internals@lists.php.net
In-Reply-To: <20030323090240my5O%!@at.wakwak.com>
References: <1048367260.848.1147.camel@hasele>
	 <20030323090240my5O%!@at.wakwak.com>
Content-Type: text/plain
Organization: 
Message-ID: <1048376595.847.1158.camel@hasele>
Mime-Version: 1.0
Date: 22 Mar 2003 18:43:15 -0500
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] default exceptions, interfaces, etc.
From: sterling@bumblebury.com (Sterling Hughes)

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.)

-Sterling

> Moriyoshi
> 
> Sterling Hughes <sterling@bumblebury.com> wrote:
> 
> > Hi,
> > 
> > Attached is a patch (+ 2 files) that add a default "exception" class to
> > Zend 2.  I find this very useful when you just want to throw a simple
> > exception inside of a try {}, but you don't want to create a new
> > exception for each and every error.  I'll commit this tommorowish,
> > unless somebody objects.
> > 
> > -Sterling
> > -- 
> > "Whether you think you can or think you can't -- you are right." 
> >     - Henry Ford
-- 
"People can have the Model T in any colour -- so long as it's black." 
    - Henry Ford