Hello Stephane,

maybe i could make getTrace a protected or even public method in 5.1 but at
the moment it is impossible. The whole thing of handling the exceptions is
very complex and any change may result in the whole exception/catching
facility being bork and trowing around SEGVs. Then we didn't add finally or
catch all because we already had far too much problems. And now we are in
feature freeze mode there is no chance of such features. If we would add one
of them we'd need to start with another b1 because the impact is to high if
you go and change compiler and/or executor.

Anyway having soemone like you to play with all the things to their deepst
tricks is a good thing only you currently need to live with what we have
until you find real bugs. So please continue investigating and maybe you
need to collect all of your ideas for developing after 5.0 is out.

marcus

Saturday, January 24, 2004, 4:23:54 PM, you wrote:

> Hello Marcus,

> == Quote from Marcus Boerger ([EMAIL PROTECTED])'s article
>> i had reasons to make that property private. You may use getTrace() to
>> read the contents and if you must overwrite it because you want to misuse
>> the whole thing then you can overwrite the read access method, too. This
>> should be enough, right?

> Except if I misunderstood your answer, but getTrace() is final, so I
> can't overwrite it. This was in fact the idea of my original message, by
> putting methods final (and most of Exception are) you can't overwrite
> them, limiting by this fact its use.

> A second idea of my original message was to force Exception to be the
> base class of all exceptions, to allow to write generic code that catches
> all exceptions (to mimic "finally" clauses).
> There were no reactions on that, but according to our exchanges, I
> assume you would not do that (you're more on proposing things rather than
> imposing them, right?). So what about implementing a "catch(...)" or a
> "finally" clause?

> Regards,
> Stephane




-- 
Best regards,
 Marcus                            mailto:[EMAIL PROTECTED]

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to