# Similarities and differences between pragma once and ifndef

To prevent the same file from being included multiple times

1 # ifndef Mode
2 # pragma once Method

There is no big difference between compilers that support these two methods, but there are still some minor differences between the two.
Method 1:
# Ifndef _ SOMEFILE_H __
# Define _ SOMEFILE_H __
... // Some declaration statements
# Endif

Method 2:

# Pragma once
... // Some declaration statements

# The ifndef method depends on the macro name and cannot conflict with each other. This not only ensures that the same file is not included multiple times, but also ensures that two files with identical content are not accidentally included at the same time. Of course, the disadvantage is that if the macro names of different header files are accidentally "crashed", the header files may obviously exist, but the compiler can hardly find the declaration.

# Pragma once is guaranteed by the compiler: the same file will not be contained multiple times. Note that the "same file" here refers to a physical file, not two files with the same content. The advantage is that you don't have to think about a macro name any more. Of course, there won't be any strange problems caused by the macro name collision. The disadvantage is that if a header file has multiple copies, this method cannot ensure that it is not repeatedly included. Of course, repeat inclusion is easier to detect and correct than the "no declaration found" problem caused by macro name collision.

The first method is supported by the language, so the portability is good. The second method can avoid name conflicts.

In fact, we usually include # include "stdafx. h", where the code is

# Pragma once

# Include "targetver. h"

# Include <stdio. h>
# Include <tchar. h>

But you don't have to worry about repeated calls to stdio. h, because the content in stdio. h is

# If _ MSC_VER> 1000
# Pragma once
# Endif

# Ifndef _ INC_STDIO
# Define _ INC_STDIO

...