Joshua,
If you disable Trace in the config file, the call to the Trace methods are
still made, however I suspect each method exits shortly after figuring out
it is turned off in the config file.
If you compile your project without defining the TRACE conditional constant,
then the calls to the Trace methods themselves are not in the compiled code.
You can use the Project Properties to define or not define the TRACE
conditional compilation constant.
Do you have any data on what the perf impacts are for code that includes
Trace calls but has them disabled in the config? Obviously, if its a game
engine, I would use Debug (or turn Trace of at compile time) and if it's a
win app running on a newer machine I wouldnt care that much about the perf
impacts. But what if it is something in the middle?
Joshua,
I don't have any data on the subject, as you say. As you say it depends on
the app.
I would try it both compiled with and without & see. I would think most of
the time you would want to compile with and use the config file to control
it.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
