Is #pragma once a safe include guard?

by

#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.

More Related Contents:

  1. Why aren’t my include guards preventing recursive inclusion and multiple symbol definitions?
  2. C++ #include guards
  3. Header guards in C++ and C
  4. Purpose of Header guards
  5. in C++ , what’s so special about “_MOVE_H”?
  6. Why isn’t C/C++’s “#pragma once” an ISO standard?
  7. Naming Include Guards
  8. Best Tips for documenting code using doxygen? [closed]
  9. Set local environment variables in C++
  10. When and why would you use static with constexpr?
  11. Void Pointer Arithmetic
  12. Benefits of using reserve() in a vector – C++
  13. error for hash function of pair of ints
  14. Does C++11 change the behavior of explicitly calling std::swap to ensure ADL-located swap’s are found, like boost::swap?
  15. How does “using std::swap” enable ADL?
  16. C++ Serialization Performance
  17. What should the ‘pop()’ method return when the stack is empty? [duplicate]
  18. Is it possible to use threads to speed up file reading?
  19. “APIENTRY _tWinMain” and “WINAPI WinMain” difference
  20. Loading a dll from a dll?
  21. Reading a Matrix txt file and storing as an array
  22. How to set, clear, and toggle a single bit?
  23. Why calling main() is not allowed in C++
  24. How are the __cplusplus directive defined in various compilers?
  25. Why is pow(int, int) so slow?
  26. Display QImage with QtGui
  27. Pass by pointer & Pass by reference [duplicate]
  28. Checking if all elements of a vector are equal in C++
  29. Is it safe to reinterpret_cast an enum class variable to a reference of the underlying type?
  30. How to draw a point (on mouseclick) on a QGraphicsScene?

Leave a Comment