File: avoid-unconditional-preprocessor-if.rst

package info (click to toggle)
swiftlang 6.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,519,992 kB
  • sloc: cpp: 9,107,863; ansic: 2,040,022; asm: 1,135,751; python: 296,500; objc: 82,456; f90: 60,502; lisp: 34,951; pascal: 19,946; sh: 18,133; perl: 7,482; ml: 4,937; javascript: 4,117; makefile: 3,840; awk: 3,535; xml: 914; fortran: 619; cs: 573; ruby: 573
file content (32 lines) | stat: -rw-r--r-- 1,310 bytes parent folder | download | duplicates (12)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
.. title:: clang-tidy - readability-avoid-unconditional-preprocessor-if

readability-avoid-unconditional-preprocessor-if
===============================================

Finds code blocks that are constantly enabled or disabled in preprocessor
directives by analyzing ``#if`` conditions, such as ``#if 0`` and ``#if 1``,
etc.

.. code-block:: c++

    #if 0
        // some disabled code
    #endif

    #if 1
       // some enabled code that can be disabled manually
    #endif

Unconditional preprocessor directives, such as ``#if 0`` for disabled code
and ``#if 1`` for enabled code, can lead to dead code and always enabled code,
respectively. Dead code can make understanding the codebase more difficult,
hinder readability, and may be a sign of unfinished functionality or abandoned
features. This can cause maintenance issues, confusion for future developers,
and potential compilation problems.

As a solution for both cases, consider using preprocessor macros or defines,
like ``#ifdef DEBUGGING_ENABLED``, to control code enabling or disabling.
This approach provides better coordination and flexibility when working with
different parts of the codebase. Alternatively, you can comment out the entire
code using ``/* */`` block comments and add a hint, such as ``@todo``,
to indicate future actions.