Skip to content

Commit e771bbc

Browse files
committed
wording
1 parent 895556a commit e771bbc

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

docs/preprocessor/hash-warning-directive-c-cpp.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,24 @@
11
---
22
description: "Learn more about: #warning directive (C/C++)"
33
title: "#warning directive (C/C++)"
4-
ms.date: "11/08/2023"
4+
ms.date: 10/15/2025
55
f1_keywords: ["#warning"]
66
helpviewer_keywords: ["#warning directive", "preprocessor, directives", "warning directive (#warning directive)"]
77
---
88
# #warning directive (C/C++)
99

10-
The **#warning** directive emits a user-specified warning message at compile time, and doesn't stop compilation. This directive is available starting in C23 and C++23.
10+
The **#warning** directive emits a user-specified warning message at compile time. It doesn't stop compilation. This directive is available starting in C23 and C++23.
1111

1212
## Syntax
1313

1414
> **#warning** *token-string*
1515
1616
## Remarks
1717

18-
The warning message that this directive emits includes the *token-string* parameter. The *token-string* parameter isn't subject to macro expansion and can be optionally enclosed in quotes. This directive is used to inform the developer of a nonfatal issue that may occur, or to disseminate important information. The following example shows how to use the **#warning** directive:
18+
The warning message is the *token-string* parameter. The *token-string* parameter isn't subject to macro expansion and can be optionally enclosed in quotes.\
19+
Use this directive to inform the developer of a nonfatal issue or to communicate other important information during compilation.
20+
21+
The following example shows how to use the **#warning** directive:
1922

2023
```cpp
2124
#if defined(_LEGACY_FEATURE_FLAG)

0 commit comments

Comments
 (0)