2 ms·
When you say "the most common case", I assume you mean "the most common case now", and not in 1992 when this paper was written. The abstract does start "We bel
by eesmith 8y ago
When you say "the most common case", I assume you mean "the most common case now", and not in 1992 when this paper was written.
The abstract does start "We believe that a C programmer's impulse to use #ifdef in an attempt at portability is usually a mistake" so it's fair to assume that they were not trying to cover other uses of #ifdef.
That said, your points weren't completely ignored. Page 193 mentions #ifdef use in debug builds in the text starting "An optional feature such as debugging assistance ...".
The part about "additional room in your data structures" follows under the guideline "Such declarations, in turn, preferably should be confined to header (.h) files, to minimize the temptation to introduce #ifdef into main-line code".