Remove #pragma once warnings

c++ pragma gcc-warning
thedarkside ofthemoon picture thedarkside ofthemoon · Apr 17, 2014 · Viewed 23k times · Source

I am using #pragma once in my .cpps and .hpps and because of that I get a warning for each file that uses it. I have not found any option to disable this kind of warning, only the thing of #ifndef MY_FILE_H #define MY_FILE_H /*...*/ #endif.

So would you recommend me to replace each #pragma once with ifndefs?

in header:

#define MYFILE_H
// all the header

and in the other files:

#ifndef MYFILE_H
#include "myfile.hpp"
#endif
// the rest of the file

What do you think, is it better to use it like this? Or there is an option to disable the #pragma once warnings in GCC, that I do not know?

Answer

ChronoTrigger picture ChronoTrigger · Apr 17, 2014

The common approach is to place the guard in the .h file only:

#ifndef MYFILE_H
#define MYFILE_H
// all your myfile.hpp here
#endif

or

#pragma once
// all your myfile.hpp here

The rest of files (other .cpp) should do nothing regarding the guards. You should not get warnings by doing this.

Related questions

Disable single warning error

Is there a way to disable just a single warning line in a cpp file with visual studio? For example, if I catch an exception and don't handle it, I get error 4101 (unreferenced local variable). Is there a way to …

Read More
What does "#pragma comment" mean?

What does #pragma comment mean in the following? #pragma comment(lib, "kernel32") #pragma comment(lib, "user32")

Read More
How to disable #pragma warnings?

While developing a C++ application, I had to use a 3rd party library which produced a huge amount of warnings related with a harmless #pragma directive being used. ../File.hpp:1: warning: ignoring #pragma ident In file included from ../File2.hpp:47, …

Read More