Re: Re: cvs: pear /DBA DBA.php DBA_Builtin.php DBA_Compat.phpDBA_Relational.php DBA_Simple.php DBA_Table.php package.xml /DBA/tests
benchmark.phpgraph_template simple.php
| From: | Pierre-Alain Joye | Date: | Sat, 22 Jun 2002 16:57:20 +0000 |
| Subject: | Re: Re: cvs: pear /DBA DBA.php DBA_Builtin.php DBA_Compat.phpDBA_Relational.php DBA_Simple.php DBA_Table.php package.xml /DBA/tests benchmark.phpgraph_template simple.php |
||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-7292@lists.php.net to get a copy of this message | ||
On Sat, 22 Jun 2002 17:16:34 +0200
alexander.merz@t-online.de (Alexander Merz) wrote:
> Tomas V.V.Cox wrote:
> > are specific cases where the developer could use the class in a wrong
> > way, so instead of just fail or change the whole API to use PEAR Error
> > (loosing by the way some usability) we trigger the warning "hey
> > developer fix the code".
>
> <?php
> include "PEAR.php";
>
> PEAR::raiseError("a warning", 999, PEAR_ERROR_TRIGGER, E_USER_WARNING);
> ?>
That will definitively not match the needs of Validate.
The only methods should use PEAR::raiseError is the multiple method when the load of an external
module failed, but not significant.
pa