Marcus Boerger wrote:
Hello Andrey,
Tuesday, April 5, 2005, 5:21:17 PM, you wrote:
Stanislav Malyshev wrote:
GB>>call stack, as if the user had inserted the call to the new
GB>>__autoload() before the last closing }.
Too much magic, IMO. All you need to know is the list of functions, you
don't n
Hello Andrey,
Tuesday, April 5, 2005, 5:21:17 PM, you wrote:
> Stanislav Malyshev wrote:
>> GB>>call stack, as if the user had inserted the call to the new
>> GB>>__autoload() before the last closing }.
>>
>> Too much magic, IMO. All you need to know is the list of functions, you
>> don't need
Stanislav Malyshev wrote:
GB>>call stack, as if the user had inserted the call to the new
GB>>__autoload() before the last closing }.
Too much magic, IMO. All you need to know is the list of functions, you
don't need any 'stack' since they do not call each one.
Stanislav,
a stack is a list and
GB>>call stack, as if the user had inserted the call to the new
GB>>__autoload() before the last closing }.
Too much magic, IMO. All you need to know is the list of functions, you
don't need any 'stack' since they do not call each one.
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PR
Marcus Boerger wrote:
Hello Greg,
Monday, April 4, 2005, 2:04:47 PM, you wrote:
Andrey Hristov wrote:
Stanislav,
Greg probable means something like a stack trace of the autload callbacks
that were called. This will be a nice addition just like Exception
stacktraces
are (I wish there were stacktra
Hello Greg,
Monday, April 4, 2005, 2:04:47 PM, you wrote:
> Andrey Hristov wrote:
>> Stanislav,
>> Greg probable means something like a stack trace of the autload callbacks
>> that were called. This will be a nice addition just like Exception
>> stacktraces
>> are (I wish there were stacktraces
Hello Greg,
Monday, April 4, 2005, 2:04:47 PM, you wrote:
> Andrey Hristov wrote:
>> Stanislav,
>> Greg probable means something like a stack trace of the autload callbacks
>> that were called. This will be a nice addition just like Exception
>> stacktraces
>> are (I wish there were stacktraces
Andrey Hristov wrote:
Stanislav,
Greg probable means something like a stack trace of the autload callbacks
that were called. This will be a nice addition just like Exception
stacktraces
are (I wish there were stacktraces for Fatal errors).
yes, a stack trace would be ideal - I knew there was a na
Stanislav Malyshev wrote:
GB>>I meant a logic error - as in the user forgot to use a
GB>>DIRECTORY_SEPARATOR and so can't find any of the classes, not an
GB>>obvious PHP error.
OK - then how exactly you want the error message look like? How the engine
is going to guess if it was DIRECTORY_SEPARATO
GB>>I meant a logic error - as in the user forgot to use a
GB>>DIRECTORY_SEPARATOR and so can't find any of the classes, not an
GB>>obvious PHP error.
OK - then how exactly you want the error message look like? How the engine
is going to guess if it was DIRECTORY_SEPARATOR missing or the class wa
Stanislav Malyshev wrote:
GB>>3. If a library has an obscure bug in __autoload, the only error message
GB>>the user will see is:
GB>>
GB>>"undefined class "
GB>>
GB>>If __autoload() is going to gain the ability to be defined for a
GB>>library, then the error messages must be enhanced as well.
GB>>3. If a library has an obscure bug in __autoload, the only error message
GB>>the user will see is:
GB>>
GB>>"undefined class "
GB>>
GB>>If __autoload() is going to gain the ability to be defined for a
GB>>library, then the error messages must be enhanced as well.
Shouldn't that bug resul
12 matches
Mail list logo
