I certainly hope that they're fixed in time for 1.5.2 if it's not on the agenda to be fixed by then, what can I do to help?
On Wed, May 7, 2008 at 6:07 PM, pakmannen <
jens.ljungblad@...> wrote:
I second this. I haven't used Zend_Db before but recently started to look
into it, and had this happen to me.
Also, would be great if something was done about the autoloader throwing
warnings when a class isn't found. Very annoying in a developer environment
when you are using more than one autoloader.
Think these issues will be fixed in time for 1.5.2?
/Jens Ljungblad
JDempster wrote:
>
> Hi All,
>
> I've wasted so much time creating row classes and not finding out about a
> parse errors all because line 119 of Zend_Db_Table_Rowset_Abstract and
> it's
> shut up operator.
>
> See
http://framework.zend.com/issues/browse/ZF-2724
>
> My application would just silently die without any errors in my php.log or
> in the output. Very very frustrating.
>
> Can some one explain to me why they are there, why there is such a
> reliance
> on Zend_Loader. Why can't it just try to create the object and have any
> class auto loads deal with it, including user auto loads. Using
> Zend_Loader
> in this way put a reliance on Zend_Loader and with the @ sign break my app
> without me knowing where the problem occurs.
>
> What can be done to solve this? I've tried removing the @ sign and all
> seems
> to work fine. The same problem exists in other classes.
>
> --
> /James
>
>
View this message in context: http://www.nabble.com/Error-supression-on-calls-to-loadClass-across-ZF-obscuring-parse-errors-tp17103401p17109864.html
Sent from the Zend Framework mailing list archive at Nabble.com.
