Norman Vine writes:
but how about having the compile time option to turn it off
ie
#ifdef DO_TRACE // or any good memonic
#define DO_TRACE_READ(type) if(getAttribute(TRACE_READ)) trace_read(type)
#define DO_TRACE_WRITE(type) if (getAttribute(TRACE_WRITE))
trace_write(type)
David Megginson writes:
Norman Vine writes:
but how about having the compile time option to turn it off
ie
#ifdef DO_TRACE // or any good memonic
#define DO_TRACE_READ(type) if(getAttribute(TRACE_READ)) trace_read(type)
#define DO_TRACE_WRITE(type) if
David Megginson writes:
Norman Vine writes:
but how about having the compile time option to turn it off
ie
#ifdef DO_TRACE // or any good memonic
#define DO_TRACE_READ(type) if(getAttribute(TRACE_READ))
trace_read(type)
#define DO_TRACE_WRITE(type) if
Curtis L. Olson writes:
I would say that the safest way would be to actually profile this
to see.
Yes, it's probably time for a good profiling run -- identify the top
offenders and optimize them, like we did last time with the FGMatrix
class. I am very relucant to complicate code for
Norman Vine writes:
WHY do we we need this except when debugging ?
Does it detract from the SIM if this is removed from production
code ??
You need the trace feature for debugging user configuration, not just
C++ code. Again, think of FlightGear as analogous to a word processor
or
Norman Vine writes:
Of course please feel free to consider this just another of my 'rants' on
'the basic tenant of realtime programing'
I agree that we need to keep speed in our sights, but let's put this
in context. Here's a little program that I just wrote:
#include iostream
int
