Utilities for converting from C/C++ include guards to #pragma once and back again
Include guards suck. They’re tiring to type and tedius to update. Worse, the task of updating boilerplate leaves room for copy/paste errors, or other mistakes. #pragma once is simpler and less error prone. That’s why you should convert to #pragma once.
Alas, though #pragma once is available on all the most commonly used compilers, it’s not available on every compiler. Perhaps one day you’ll add support for a platform with a barebones compiler with no support for #pragma once and you’ll have to convert back. That’s ok. It’s easy!
There are three main tools provided by guardonce:
First, check your project for broken headers. To recursively search your project directories for the names of all files that lack proper include guards, use the following command, substituting your project’s directory for the quoted string:
checkguard -r "source_directory"
By default, checkguard is very forgiving. It accepts either #pragma once or anything that looks like an include guard. If you know that all your guards should match some format, you can be more strict by using -p to specify a pattern to check against.
If certain files are not supposed to have include guards, feel free to leave them be. Files without include guards are ignored by this next step.
Now, all that remains is converting the headers to use #pragma once:
guard2once -r "source_directory"
You’re done! Double check that the result matches your expectations and start using #pragma once in your new code. Know that if you ever need to switch back, it’s as simple as:
once2guard -r "source_directory"
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|File Name & Checksum SHA256 Checksum Help||Version||File Type||Upload Date|
|guardonce-2.1.0-py2.py3-none-any.whl (13.3 kB) Copy SHA256 Checksum SHA256||py2.py3||Wheel||Feb 15, 2017|
|guardonce-2.1.0.tar.gz (8.3 kB) Copy SHA256 Checksum SHA256||–||Source||Feb 15, 2017|