In many header files from the starter code, the header guard (#ifndef ... #define) is placed after the header file's #includes. This shouldn't be a problem as long as all of the included files have header guards, but it goes against the general convention of placing header guards before any other code.
Category: code style Priority: low
In many header files from the starter code, the header guard (
#ifndef ... #define) is placed after the header file's#includes. This shouldn't be a problem as long as all of the included files have header guards, but it goes against the general convention of placing header guards before any other code.