Re: #defines used properly to select code blocks
todma wrote:
This is on the subject of '#defines'....Macros that are 'abused' to
provide constants in programs.
What about selection of code blocks to include in compilations?
Conditional compilation is a good means of offuscation, but
not a very good solution for other things.
I have two classes that have a similar #ifdef INCLUDE_DEBUGGING_CODE
and desire them to be independent, and local to the class.
The most obvious solution is to always include the debugging
code, using some sort of run-time option to turn it on or
off.
Since there are better ways to define constants, how about code block
exclusions?
The best solution with regards to conditional compilation is
to not do it. There are other cases where macros are
indicated however, and logging (debugging code) almost
always uses them, if only to be able to insert __LINE__ and
__FILE__ automatically.
--
James Kanze (Gabi Software) email: james.kanze@gmail.com
Conseils en informatique orient?e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S?mard, 78210 St.-Cyr-l'?cole, France, +33 (0)1 30 23 00 34
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]