Date of Original Version

7-2015

Type

Conference Proceeding

Rights Management

© Flávio Medeiros, Christian Kästner, Márcio Ribeiro, Sarah Nadi and Rohit Gheyi; licensed under Creative Commons License CC-BY

Abstract or Description

The C preprocessor has received strong criticism in academia, among others regarding separation of concerns, error proneness, and code obfuscation, but is widely used in practice. Many (mostly academic) alternatives to the preprocessor exist, but have not been adopted in practice. Since developers continue to use the preprocessor despite all criticism and research, we ask how practitioners perceive the C preprocessor. We performed interviews with 40 developers, used grounded theory to analyze the data, and cross-validated the results with data from a survey among 202 developers, repository mining, and results from previous studies. In particular, we investigated four research questions related to why the preprocessor is still widely used in practice, common problems, alternatives, and the impact of undisciplined annotations. Our study shows that developers are aware of the criticism the C preprocessor receives, but use it nonetheless, mainly for portability and variability. Many developers indicate that they regularly face preprocessor-related problems and preprocessor-related bugs. The majority of our interviewees do not see any current C-native technologies that can entirely replace the C preprocessor. However, developers tend to mitigate problems with guidelines, even though those guidelines are not enforced consistently. We report the key insights gained from our study and discuss implications for practitioners and researchers on how to better use the C preprocessor to minimize its negative impact.

DOI

10.4230/LIPIcs.ECOOP.2015.999

Creative Commons


This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS
 

Published In

Proceedings of the European Conference on Object-Oriented Programming (ECOOP), 2015, 999-1022.