Conditional compilation
In computer programming, conditional compilation is a compilation technique which results in an executable program that is able to be altered by changing specified parameters. This technique is commonly used when these alterations to the program are needed to run it on different platforms, or with different versions of required libraries or hardware.
Many programming languages support conditional compilation. Typically compiler directives define or "undefine" certain variables; other directives test these variables and modify compilation accordingly. For example, not using an actual language, the compiler may be set to define "Macintosh" and undefine "PC", and the code may contain:
(* System generic code *)
if mac != Null then
(* macOS specific code *)
else if pc != Null
(* Windows specific code *)
In C and some languages with a similar syntax, this is done using an '#ifdef' directive.
A similar procedure, using the name "conditional comment", is used by Microsoft Internet Explorer from version 5 to 9 to interpret HTML code. There is also a similar proprietary mechanism for adding conditional comments within JScript, known as conditional compilation.[1]
Criticism
When conditional compilation depends on too many variables, it can make the code harder to reason about as the number of possible combinations of configuration increases exponentially.[2][3][4] When conditional compilation is done via a preprocessor that does not guarantee syntactically correct output in the source language, such as the C preprocessor, this may lead to hard-to-debug compilation errors,[5][6][7] which is sometimes called "#ifdef hell."[8][9]
References
- ↑ "Conditional Compilation". Microsoft Corporation. http://msdn2.microsoft.com/en-us/library/ahx1z4fs(VS.80).aspx.
- ↑ Gazzillo, Paul; Wei, Shiyi (2019-05-27). "Conditional Compilation is Dead, Long Live Conditional Compilation!" (in en). 2019 IEEE/ACM 41st International Conference on Software Engineering: New Ideas and Emerging Results (ICSE-NIER). Montreal, QC, Canada: IEEE Press. pp. 105–108. doi:10.1109/ICSE-NIER.2019.00035. ISBN 978-1-7281-1758-4. https://www.paulgazzillo.com/papers/icse19nier.pdf. Retrieved 2023-01-21.
- ↑ Meinicke, Jens; Thüm, Thomas; Schröter, Reimar; Benduhn, Fabian; Leich, Thomas; Saake, Gunter (2017). Meinicke, Jens; Thüm, Thomas; Schröter, Reimar et al.. eds (in en). Quality Assurance for Conditional Compilation. Cham: Springer International Publishing. pp. 131–139. doi:10.1007/978-3-319-61443-4_12. ISBN 978-3-319-61443-4. https://doi.org/10.1007/978-3-319-61443-4_12. Retrieved 2023-01-21.
- ↑ "compiler - How does conditional compilation impact product quality, security and code complexity?" (in en). https://softwareengineering.stackexchange.com/questions/405980/how-does-conditional-compilation-impact-product-quality-security-and-code-compl.
- ↑ Le, Duc; Walkingshaw, Eric; Erwig, Martin (2011-09-18). "#ifdef confirmed harmful: Promoting understandable software variation". 143–150. doi:10.1109/VLHCC.2011.6070391. ISBN 978-1-4577-1246-3. https://ieeexplore.ieee.org/document/6070391.
- ↑ "conditional compilation - Why should #ifdef be avoided in .c files?" (in en). https://stackoverflow.com/questions/1851181/why-should-ifdef-be-avoided-in-c-files.
- ↑ "c++ - Dos and Don'ts of Conditional Compile" (in en). https://stackoverflow.com/questions/4469645/dos-and-donts-of-conditional-compile.
- ↑ Preschern, Christopher (2019-07-03). "Patterns to escape the #ifdef hell". New York, NY, USA: Association for Computing Machinery. 1–12. doi:10.1145/3361149.3361151. ISBN 978-1-4503-6206-1. http://preschern.azurewebsites.net/2019-os-specific-code.pdf.
- ↑ "Living in the #ifdef Hell" (in en-GB). 28 October 2015. http://www.cqse.eu/en/news/blog/living-in-the-ifdef-hell/.
 |  |
