You could solve this with a little more inconvient coding yes?
Function exception($line, $file) {
$exp = new Zend_Exception();
$exp->setLine($line);
$exp->setFile($file);
}
Throw Zend::exception(__LINE__, __FILE__);
--
John Coggeshall
Team Lead NA Pro. Services
Zend Technologies
> -----Original Message-----
> From: Bill Karwin [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 18, 2006 11:44 AM
> To: Nico Edtinger
> Cc: Aleksey V. Zapparov; Zend Framework General
> Subject: Re: [fw-general] Re: Do we really need Zend::exception()?
>
> Nico Edtinger wrote:
> > With Zend::exception() we avoid loading all those exception classes
> > that are only needed if an error occurs, which should be an
> exception.
> > So instead of loading these files or at least stat()ing it with an
> > opcode cache we waste some lines in a file that's loaded
> anyway. That
> > has nothing to do with bugs in any class.
>
> But it's a good point that this method causes stack traces to
> become obfuscated. It reports the __FILE__ and __LINE__ of
> the exception as occurring in Zend::exception, because that's
> where the exception is actually thrown.
>
> Regards,
> Bill Karwin
