In many of the C and C++ files I have seen macros like this:
#ifdef X #undef X // no statements in between #endif
I feel that, it's adequate to simply write:
Si la macro
X wasn't defined, then the
#undef should have no effect.
Lo es ok to put standalone
#undef, if I want to only indefinir a macro ? Does that make the coding practice bad in anyway ?
preguntado el 01 de febrero de 12 a las 03:02
See ISO C99 188.8.131.52 paragraph 2.
Una directiva de preprocesamiento del formulario
# undef identifier new-line
causes the specified identifier no longer to be defined as a macro name. It is ignored if the specified identifier is not currently defined as a macro name.
Incluso Visual C ++ 6 (which was notorious for bad standards compliance) allows this:
También puede aplicar el
#undefdirective to an identifier that has no previous definition. This ensures that the identifier is undefined. Macro replacement is not performed within
I'm sure it's an artifact of history. As mentioned in jdigital's answer, the 2nd edition of K&R says
It is not erroneous to apply #undef to an unknown identifier.
However, that sentence is not in the 1978 edition. I'm pretty sure pre-standard compilers would often throw an error if you tried to
#undef an undefined macro.
También el ANSI C Rationale says:
It is explicitly permitted to #undef a macro that has no current definition.
I'd imagine that if it was already universal practice, there would be no need to call it out in the rationale.
All that said, it's not necessary in modern code, but it doesn't really hurt either.
Kernighan and Ritchie (2nd edition) agree with you.
EDIT: quote from the source (section A12.3):
Una línea de control del formulario
causes the identifier's preprocessor definition to be forgotten. If is not erroneous to apply
#undefto an unknown identifier.