Quote:Original post by Promit

As for pragma once, there's nothing wrong with it as long as you use it and include guards together.

Quote:Original post by Adam Hamilton

Quote:Original post by Promit

As for pragma once, there's nothing wrong with it as long as you use it and include guards together.

Then what is the point of using #pragma once if you are going to put include guards in unless your hard drive and computer are really, really slow.

Quote:Original post by Adam Hamilton
But you missed my point entirely. I know that #pragma once yields better performance on VS compilers and include guards are treated as special on GCC but in this post by jonahrowley the performance boost would be minimal as the file is most likely cached.

Which is why I said you can drop the #pragma once and I think would be advisable for writing cross compiler code. Why bother with if/else just for the include guard when the performance gain is minimal.

But I may be wrong as I have never actually wrote a huge project and tested compile times using both the include guard method and the #pragma once method.

Quote:Original post by Adam Hamilton
I don't know why my point isn't getting across

If you are writing cross compiler code, only use include guards.
If you don't care about targeting a multitude of compilers and you are using VS, use #pragma once

But for heavens sake. DONT put them both in. It just rings of stupidity

Quote:Original post by Adam Hamilton
I have never written cross compiler code...