TICS Coding Standard Viewer 
TIOBE Software Quality Framework
Print-friendly version
©TIOBE Software www.tiobe.com
 
ASML C Coding Standard
Search

Category: Lexical Elements

Synopsis:Rules about keywords, literals, identifiers and comments


Description:

Coding Rules

NameCheckedSynopsis
6.4.b Checked automatically with code checker The tab character (0x09 ASCII) shall not be used.
6.4.1.a Checked automatically with code checker C keywords are reserved for use as keywords and shall not be used otherwise.
6.4.1.b Checked automatically with code checker Only with a very good reason, the asm keyword may be used to insert assembly language directly into the translator output.
6.4.1.1.a Checked automatically with code checker Do not use C++ keywords.
6.4.1.1.b Checked automatically with code checker Do not use C++ alternative representations that are not part of the C keywords (see also 6.4.1.a).
6.4.2.a Checked automatically with code checker Identifiers shall satisfy the standard C syntax for identifiers.
6.4.2.b Checked automatically with code checker Identifiers shall not be defined with one or more leading underscores (_).
6.4.2.d Checked automatically with code checker Don't use extern variable declarations in header files, except for consts.
6.4.4.b Checked automatically with code checker Use suffix 'L' instead of 'l' to avoid confusion
6.4.4.1.a Checked automatically with code checker Only decimal or hexadecimal notation may be used for integer constants.
6.4.4.1.b Checked automatically with code checker Use clear constant values. Small letters shall not be used, expecially to avoid confusion between l (letter l) and 1 (digit one). The letter U shall be written in uppercase to be consistent with the case of the letter L.
6.4.4.3.a Checked automatically with code checker Only the first entry in an enumerator shall be explicitly defined using '='.
6.4.4.4.a Checked automatically with code checker Only ANSI defined escape sequences shall be used.
6.4.5.a Checked automatically with code checker A character string literal token shall not be adjacent to a wide string literal token.
6.4.9.a Checked automatically with code checker Comments in the form of opening (/*) and closing (*/) shall not be nested.
6.4.9.c Checked automatically with code checker Do not use mixed comments.