Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10775
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20040625165048.25768.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <20040619160702.82169.qmail@pb1.pair.com> <5.1.0.14.2.20040623000747.02024828@127.0.0.1>
Date: Fri, 25 Jun 2004 18:51:37 +0200
Lines: 21
Subject: Re: [PHP-DEV] Re: throwing exceptions in __autoload
From: rashid@ds.pg.gda.pl ("Robert Janeczek")

> most cases, there aren't very good reasons to throw exceptions from it.
How
> come you can't declare the class when __autoload() is called but you can
do
> so later? In such a weird situation, you could declare a proxy object with
> the same name which relays all calls to the real class if/when you can
load it.
> So basically, I understand what you're saying, but I don't see a very
> compelling reason to work very hard now to make this work differently.

i`m working on application server for php. i need exception to continue
server running after a component couldn`t be found or properly loaded, or at
least close it with some trash cleaning. i wanted to write as few code in
__autoload as possible, but it seams that i`ll have to check all the
possibilities of crashing.

rash
ps. yes, i know php is supposed to work in a different way than java :] i
just love challenges ;)