This PR contains the changes to deal with issue #115
Additionally, whilst already dealing with the headers, I updated the header guards where necessary. This entailed making the guard names consistent with the filenames, and introducing a consistent formatting for the comment on the #endif at the end of each header. The formatting is #endif // Name_of_header_guard, i.e. two spaces after endif followed by the comment.
Software compiles and runs, though I have not tested running any actual railway operations after this change. However, as it only touches the header includes for the language server, this really shouldn't change anything about that.
This PR contains the changes to deal with issue #115
Additionally, whilst already dealing with the headers, I updated the header guards where necessary. This entailed making the guard names consistent with the filenames, and introducing a consistent formatting for the comment on the
#endifat the end of each header. The formatting is#endif // Name_of_header_guard, i.e. two spaces after endif followed by the comment.Software compiles and runs, though I have not tested running any actual railway operations after this change. However, as it only touches the header includes for the language server, this really shouldn't change anything about that.
Closes #115