How Close Is Existing C/C++ Code to a Safe Subset?
Journal of Cybersecurity and Privacy · 28.12.2023 · 4 (1) · 1-22
DOI: 10.3390/jcp4010001 ↗Kurz gefasst
Fachartikel in der Zeitschrift Journal of Cybersecurity and Privacy, online erschienen am 28.12.2023. Verfasst von Christian DeLozier. Die Arbeit wurde bisher 4-mal zitiert (Crossref) und nennt 35 Literaturangaben. Der Volltext ist frei zugänglich (Open Access, CC BY 4.0).
Abstract (Originalsprache)
Using a safe subset of C++ is a promising direction for increasing the safety of the programming language while maintaining its performance and productivity. In this paper, we examine how close existing C/C++ code is to conforming to a safe subset of C++. We examine the rules presented in existing safe C/C++ standards and safe C/C++ subsets. We analyze the code characteristics of 5.8 million code samples from the Exebench benchmark suite, two C/C++ benchmark suites, and five modern C++ applications using a static analysis tool. We find that raw pointers, unsafe casts, and unsafe library functions are used in both C/C++ code at large and in modern C++ applications. In general, C/C++ code at large does not differ much from modern C++ code, and continued work will be required to transition from existing C/C++ code to a safe subset of C++.
Zitieren
APA
DeLozier, C. (2023). How Close Is Existing C/C++ Code to a Safe Subset?. Journal of Cybersecurity and Privacy, 4(1), 1-22. https://doi.org/10.3390/jcp4010001
Vancouver
DeLozier C. How Close Is Existing C/C++ Code to a Safe Subset?. Journal of Cybersecurity and Privacy. 2023;4(1):1-22. doi:10.3390/jcp4010001
BibTeX
@article{DeLozier2023,
author = {DeLozier, Christian},
title = {How Close Is Existing C/C++ Code to a Safe Subset?},
journal = {Journal of Cybersecurity and Privacy},
year = {2023},
volume = {4},
number = {1},
pages = {1--22},
doi = {10.3390/jcp4010001}
}
EUVIMED