close
C# Online.NET Visual C# Developer Center
Search

ECMA-334: 9.5 Pre-processing directives

C# Language Specification
© 2006 ECMA International

9.5 Pre-processing directives

The pre-processing directives provide the ability to skip conditionally sections of source files, to report error and warning conditions, and to delineate distinct regions of source code. [Note: The term "pre-processing directives" is used only for consistency with the C and C++ programming languages. In C#, there is no separate pre-processing step; pre-processing directives are processed as part of the lexical analysis phase. end note]

pp-directive::
pp-declaration
pp-conditional
pp-line
pp-diagnostic
pp-region
pp-pragma

The following pre-processing directives are available:

symbols (§9.5.3).

A pre-processing directive always occupies a separate line of source code and always begins with a # character and a pre-processing directive name. White space can occur before the # character and between the # character and the directive name.

A source line containing a #define, #undef, #if, #elif, #else, #endif, or #line directive can end with a single-line comment. Delimited comments (the /* */ style of comments) are not permitted on source lines containing pre-processing directives.

Pre-processing directives are not tokens and are not part of the syntactic grammar of C#. However, preprocessing directives can be used to include or exclude sequences of tokens and in that way can affect the meaning of a C# program. [Example: When compiled, the program

#define A
#undef B
 
class C
{
#if A
  void F() {}
#else
  void G() {}
#endif
#if B
  void H() {}
#else
  void I() {}
#endif
}

results in the exact same sequence of tokens as the program

class C
{
  void F() {}
  void I() {}
}

Thus, whereas lexically, the two programs are quite different, syntactically, they are identical. end example]