Re: Exception / trace member

From: Date: Sat, 24 Jan 2004 15:23:54 +0000
Subject: Re: Exception / trace member
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-7314@lists.php.net to get a copy of this message
Hello Marcus, == Quote from Marcus Boerger (helly@php.net)'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

« previous php.internals (#7314) next »