Re: Any Suggestion How To Accomplish A Debug Macro?

["J-P. Rosen" <rosen@adalog.fr>]

Le 30/12/2014 23:11, Randy Brukardt a écrit :
> But I don't think there is much reason (outside of the memory-constrained 
> embedded system, or the system that has to be formally proved or validated) 
> to ever removing the tracing. It's important to be able to turn it off, of 
> course, but the runtime cost of it being off is so minimal (primarily 
> caching/paging effects) that removing it isn't worth the effort. (And if you 
> plan to keep it around forever, you'll spend more time making the traces 
> make sense in the future -- which typically pays off very quickly.)

I fully agree with that.
In AdaControl, there is a sophisticated tracing capability, and it's
enabled with a command line option. If a user has a problem, he just has
to rerun the program with -x and send me the output - that's usually
enough to identify the problem. I can't tell how much time it saved me.
And since AdaControl spends about 65% of its time in ASIS, the cost of
testing a boolean is neglectible.
-- 
J-P. Rosen
Adalog
2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX
Tel: +33 1 45 29 21 52, Fax: +33 1 45 29 25 00
http://www.adalog.fr