At 03:23 PM 1/24/2004 +, Stephane Drouard 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
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
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
>
Hello Stephane,
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?
Friday, January 23, 2004, 10:54:53 AM,
Hello Marcus,
Hum... you fixed the issue but not really in the way I expected it. Now my code does
not work...
My message was not only to report a bug, but to ask *not* to fix it as expected.
Particularly to put the "trace" member as protected, (or "getTrace()" as virtual and
not final).
Reme
Hello Stephane,
> if this is really the case, well then i am the one to blame. I'll have a
> look.
i looked into it - you were right - and i fixed it. Could you please test
current HEAD to verify i have fixed all issues? That would give me a better
feeling. And thanks for noticing this.
marcus
Hello Stephane,
if this is really the case, well then i am the one to blame. I'll have a
look.
Thursday, January 22, 2004, 3:46:13 PM, you wrote:
> The current implementation of class Exception has a private "trace"
> member, which is used to store the backtrace. But if you throw an
> exception
The current implementation of class Exception has a private "trace" member, which is
used to store the backtrace. But if you throw an exception of a derived class of
Exception, print_r() displays an empty "trace:private" member, as well as a "trace"
(public) member that really holds the backtrac
