Indentation and fail
Brought to you by:
jvarszegi
Menu
▾
▴
#2 Indentation and fail
(copied from "bug" 830372)
Great product, but there are two simple functionalities
that are in Debug/Trace that are lacking from your
package:
- indentation
- Fail(), i.e. an Assertion that throws an exception.
Indentation can be solved by useing your TraceLogger,
but that seems unnecessary to me if you'll just
implement it. (plus i'd rather the message indented, not
the entire event).
And I'd like my assertions to be thrown in my face when
I'm debugging, as with Debug.Fail.
juliob
Followups:
Comments
-------------------------------------------------------
-------------------------
Date: 2003-10-26 12:44
Sender: jvarszegi
Logged In: YES
user_id=835109
I will have to think about indentation a little bit. The
thing
is,
I BELIEVE that the way it's implemented in Trace is
inherently
unsuited for multithreaded apps: one thread can affect
the
indentation level for all threads. Maybe I'm wrong, and
they
store the indentation level in a LocalStoreDataSlot or
something. Anyway, I don't see harm in doing this, and
I will
see if I can think of a good way to do it on a per-thread
basis
(probably as an extra property of the current Context),
okay?
The Fail() suggestion is a slam-dunk. We're currently
getting
the actual project set up, as five people just joined up;
right
now we're setting up the source in CVS, etc. Sometime
this
week we should be able to get together a beta build of
the
next release, and I'll try to make sure these two things
are
considered, and if possible, put in. In the meantime, this
ticket will remain open.
BTW, I wouldn't consider these bugs, but new-feature
requests. Again, thanks a lot for the suggestions. -Jeff
Logged In: YES
user_id=890073
Another restriction of using TraceLogger to handle indentation
is that it doesn't mesh well with the Indent() command if
buffering is enabled. So I have to disable buffering to get it
to work.