At 07:17 AM 10/24/2003 -0700, Eduardo R. Maciel wrote:
Hi,
I agree with Dan´s opinion.
Watching from a point of view of a developer working
on PHP Object Oriented aplications, libs, frameworks,
etc, there is no sense on things like this. Or it IS
object oriented or it IS NOT. Partiality alway
Hi,
I agree with Dan´s opinion.
Watching from a point of view of a developer working
on PHP Object Oriented aplications, libs, frameworks,
etc, there is no sense on things like this. Or it IS
object oriented or it IS NOT. Partiality always run
into complications. And that was what happen on P
Hi Andi-
Yes, that explains things and makes perfect sense if you are just
writing your
own web application. Now, consider the new __autoload functionality from
a PEAR
or other large API/library developer standpoint.
The new __autoload functionality lets us:
- Keep library usage/installation s
Dan,
__autoload() is the last chance to load a class which is needed before
erroring out and terminating the script. By design, if you don't take
advantage of this last chance the script will error out. Therefore,
throwing an exception inside the __autoload() function should not be
catchable b
Hello Dan,
Sunday, October 12, 2003, 7:34:59 AM, you wrote:
> This behaviour isn't a show stopper. It's just the inconsistency that
> bugs me.
yes!
> I'm left wondering what other ways the engine might handle my exceptions
> that
> I might not expect, like...
> try {
> function __autoload($
Marcus-
Here are just some interesting observations with __autoload() and
exceptions:
Currently, an empty php file with just "throw new Exception();" will
dump out an
error like so: *Fatal error*: Uncaught exception 'exception' with
message 'Unknown exception' in
/server/http/sites/db.wep.net/
