8.7. Enabling and Disabling Complex Tracing Code
Problem
Youhave an object that contains complex tracing/debugging code. In fact, there is so much tracing/debugging code that to turn it all on would create an extremely large amount of output. You want to be able to generate objects at runtime that contain all of the tracing/debugging code, only a specific portion of this tracing/debugging code, or no tracing/debugging code. The amount of tracing code generated could depend on the state of the application or the environment in which it is running. The tracing code needs to be generated during object creation.
Solution
Use the TraceFactory class shown in Example 8-4, which implements the factory design pattern to allow creation of an object that either generates tracing informa-tion or does not.
Example 8-4. TraceFactory class
#define TRACE
#define TRACE_INSTANTIATION
#define TRACE_BEHAVIOR
using System.Diagnostics;
public class TraceFactory
{
public TraceFactory() {}
public Foo CreateObj()
{
Foo obj = null;
#if (TRACE)
#if (TRACE_INSTANTIATION)
obj = new BarTraceInst();
#elif (TRACE_BEHAVIOR)
obj = new BarTraceBehavior();
#else
obj = new Bar();
#endif
#else
obj = new Bar();
#endif
return (obj);
}
}The class hierarchy for the Bar, BarTraceInst, and BarTraceBehavior classes is shown next. The BarTraceInst class contains only the constructor tracing code, the BarTraceBehavior class contains tracing code only within specific methods, and the Bar class contains no tracing code:
public abstract ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access