Hello Stanislav,
me neither, I just wanted to clarify :-)
marcus
Monday, September 10, 2007, 6:48:14 PM, you wrote:
>> I guess the point is that ppl might want to have interfaces use different
>> approach than they want class to. For instance classes get filenames with
>> just the classname f
I guess the point is that ppl might want to have interfaces use different
approach than they want class to. For instance classes get filenames with
just the classname followed by '.php' while interfaces might get a prefix
'i_' or a different extension like '.inc'.
Well, since now autoloader does
Hello Stanislav,
Saturday, September 8, 2007, 1:50:24 AM, you wrote:
>> Actually, an autoload handler should never emit errors or throw
>> exceptions. With handlers registered through SPL, it is already the
>> case. When using an __autoload() functions, raising an error when a
>> symbol is not fo
Actually, an autoload handler should never emit errors or throw
exceptions. With handlers registered through SPL, it is already the
case. When using an __autoload() functions, raising an error when a
symbol is not found is useless because we know that the PHP
interpreter will do it. So, I propose
Hi,
> From: Dmitry Stogov [mailto:[EMAIL PROTECTED]
>
> The patch provides an additional boolean argument to
> __autoload() that say if class is really required. In case if
> it false, user code shouldn't emit errors or throw exceptions.
Actually, an autoload handler should never emit errors
