Configuration specific code

Which language ?

When using C/C++ you can write:

#ifdef DEBUG// your debug statements#endif

and make sure that you define DEBUG when in debug mode, i.e. passing -DDEBUG to your compiler.

In principal I agree w/ nmi, but I've read somewhere that MSC uses _DEBUG instead of DEBUG. So there may be little variations in dependence of the compiler in use. (E.g. gcc uses DEBUG). For portability it would be best to unify these stuff in a prerequisites header file if possible.

Quote:

Original post by haegarr In principal I agree w/ nmi, but I've read somewhere that MSC uses _DEBUG instead of DEBUG. So there may be little variations in dependence of the compiler in use. (E.g. gcc uses DEBUG). For portability it would be best to unify these stuff in a prerequisites header file if possible.

Note that NMI mentioned to make sure he defines DEBUG. MSVC uses _DEBUG as the default, but you can change this very easily by modifying the defined variables in the preprocessor properties.

@joanusdmentia: Right you are.

However, it seems senseful to me to couple the inclusion/exclusion of the if clause as is requested in the original posting to the standard flags, instead of overhanding an own flag (what of course also can make sense). So I've suggested a prerequisites header file to overcome protability problems by unifying the possible "standard" compiler flags to one to be used throughout the sources.

Quote:

Original post by haegarr However, it seems senseful to me to couple the inclusion/exclusion of the if clause as is requested in the original posting to the standard flags, instead of overhanding an own flag (what of course also can make sense). So I've suggested a prerequisites header file to overcome protability problems by unifying the possible "standard" compiler flags to one to be used throughout the sources.

I find that a prerequisites header file of sorts to be more trouble than it's worth. You more often than not start loading it with all sorts of things that really shouldn't be there and makes your code dependant on an essentially unrelated header.

Not only that, but your prerequisites file needs to try and account for all the different 'standard' defines for different compilers to try and guess if you're running a debug build or not (admittadly there's prob only the 2 variations). It's far simpler to just say 'define this in your project for debug builds'.

Having said that, if you're only using the 1 compiler it doesn't really matter [smile]

Quote:

Original post by joanusdmentia You more often than not start loading it with all sorts of things that really shouldn't be there and makes your code dependant on an essentially unrelated header.

Of cource, one could do wrong things anywhere, and hence also in a prerequisites header. The inclusion of other header files (as you mentioned as an example) is such a trap, right you are.

I personally use a prerequisites header, including nothing more than (which is actually used by every compile unit). All the other stuff is pre-processor related: Determining the OS, debug/release stuff, compiler and compiler version, and the dynamic lib export stuff. Not all but most of this is used almost everywhere.

Quote:

Original post by joanusdmentia Not only that, but your prerequisites file needs to try and account for all the different 'standard' defines for different compilers to try and guess if you're running a debug build or not (admittadly there's prob only the 2 variations). It's far simpler to just say 'define this in your project for debug builds'.

Ok. There's nothing to say against this point of view. I'm using a scheme of assertions named "design by contract" (Meyer) that is to be switched on/off independently from debug/release mode. You see, I'm also already following this way ;-)

After all, its a question of personal preferences, but _if_ used, a prerequisites header should be designed to hold essentials only.