RE: [PEAR-DEV] PEAR Error Management
| From: | Steven Levin | Date: | Tue, 24 Sep 2002 14:19:44 +0000 |
| Subject: | RE: [PEAR-DEV] PEAR Error Management | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-9416@lists.php.net to get a copy of this message | ||
Hello All,
I have been reading up on the Pear-Dev lists for a couple of weeks now
but this is my first post. I would also like to see a tutorial for the
PEAR_error class. I have been looking at some of the code in PEAR CVS
and it seems as though pear has a standard way of doing it. First
define all your error codes. Then extend PEAR_error and overide its
constructor. Finally implement is_error and errorMessage which seem to
be consistently similar among the developers. Is this true? I still
feel like I am missing something. Any help would be greatly
appreciated.
>> From: Sebastian Bergmann [mailto:sebastian@php.net]
>> Sent: Tuesday, September 24, 2002 8:12 AM
>>
>> For quite some time now, I haven't looked at the PEAR base class,
> and
>> never really at its facilities for error management.
>>
>> I want to use PEAR::raiseError() (I guess that I want that, actually
> :)
>> to trigger an error and send the error message by default to
>> error_log().
>>
>> How do I go about that?
>>
>
> I also think that a tutrial about all the nifty features is seriously
> lacking. I figured out some stuff by asking stig and reading the source
> of PEAR DB. But I still don't think I know how it all works nor should
> it be such an arcane and serect magic to begin with.
>
> Regards,
> Lukas
>
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
--
Steven Levin
Electronic Student Services
Appalachian State University
Phone: 828.262.2431
PhpWebsite Development Team
URL: http://phpwebsite.appstate.edu
Email: steven@tux.appstate.edu