Comment by AndriyKunitsyn
4 days ago
The whole point of C/C++ is knowing your environment. It's not Java, it's not TypeScript. It's one level above assembly, and if you change the compiler and things break, then it's your fault.
If the standards still don't have a proper replacement for include guards, then too bad for the standards. The C++ standard wasn't aware of multithreading before C++11, this didn't stop people from writing multithreaded programs.
As to why - #pragma once is just cleaner to look at.
> the standards still don't have a proper replacement for include guard
It does with modules... and in ten year if modules support is widespread, I'll consider stoping using pragma once.