Is #pragma once a safe include guard?

c++ include-guards
Ryan Emerle picture Ryan Emerle · Apr 24, 2009 · Viewed 176k times · Source

I've read that there is some compiler optimization when using #pragma once which can result in faster compilation. I recognize that is non-standard, and thus could pose a cross-platform compatibility issue.

Is this something that is supported by most modern compilers on non-windows platforms (gcc)?

I want to avoid platform compilation issues, but also want to avoid the extra work of fallback guards:

#pragma once
#ifndef HEADER_H
#define HEADER_H

...

#endif // HEADER_H

Should I be concerned? Should I expend any further mental energy on this?

Answer

Motti picture Motti · Dec 22, 2009

#pragma once does have one drawback (other than being non-standard) and that is if you have the same file in different locations (we have this because our build system copies files around) then the compiler will think these are different files.

Related questions

C++ #include guards

SOLVED What really helped me was that I could #include headers in the .cpp file with out causing the redefined error. I'm new to C++ but I have some programming experience in C# and Java so I could be missing …

Read More
Header guards in C++ and C

At LearnCpp.com | 1.10 — A first look at the preprocessor. Under Header guards, there are those code snippets: add.h: #include "mymath.h" int add(int x, int y); subtract.h: #include "mymath.h" int subtract(int x, int y); main.…

Read More
Why aren't my include guards preventing recursive inclusion and multiple symbol definitions?

Two common questions about include guards: FIRST QUESTION: Why aren't include guards protecting my header files from mutual, recursive inclusion? I keep getting errors about non-existing symbols which are obviously there or even weirder syntax errors every time I write …

Read More