blocks|key|1324927|text|保持一致，无论是哪一个都无关紧要。此外，如果出于某种原因，您必须使用某个调试标识符与另一个程序或工具进行互操作，这很容易做到|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1324928|#ifdef+THEIRDEBUG
#define+MYDEBUG
#endif+//and+vice-versa|code-block|syntax|javascript|1324929|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Be consistent and it doesn't matter which one. Also if for some reason you must interop with another program or tool using a certain DEBUG identifier it's easy to do

<pre><code>#ifdef THEIRDEBUG
#define MYDEBUG
#endif //and vice-versa
</code></pre>

blocks|key|1324980|text|Visual+Studio定义标准当您指定/MTd或/MDd选项时，NDEBUG将禁用标准C断言。在适当的时候使用它们，例如，如果你想让你的调试代码与MS+CRT+debugging+techniques保持一致，就使用_DEBUG；如果你想让你的调试代码与NDEBUG保持一致，就使用assert()。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1324981|如果您定义了自己的调试宏(并且不破解编译器或C运行时)，请避免以下划线开头的名称，因为它们是保留的。|1324982|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/visualstudio/debugger/crt-debugging-techniques^0|L|4|Q|4|Y|6|32|6|3L|6|3Z|8|23|R|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@$9|12|A|13|1|14]]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

Visual Studio defines <code>_DEBUG</code> when you specify the <code>/MTd</code> or <code>/MDd</code> option, <code>NDEBUG</code> disables standard-C assertions. Use them when appropriate, ie <code>_DEBUG</code> if you want your debugging code to be consistent with the <a href="https://docs.microsoft.com/en-us/visualstudio/debugger/crt-debugging-techniques" rel="noreferrer">MS CRT debugging techniques</a> and <code>NDEBUG</code> if you want to be consistent with <code>assert()</code>.

If you define your own debugging macros (and you don't hack the compiler or C runtime), avoid starting names with an underscore, as these are reserved.

blocks|key|1109879|text|宏NDEBUG控制assert()语句是否处于活动状态。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1109880|在我看来，这与任何其他调试是分开的-所以我使用NDEBUG之外的其他东西来控制程序中的调试信息。我使用的不同，取决于我使用的框架；不同的系统有不同的启用宏，我使用任何合适的。|1109881|如果没有框架，我会使用没有前导下划线的名称；这些下划线倾向于保留给“实现”，并且我试图避免名称冲突的问题-当名称是宏时更是如此。|1109882|entityMap^0|1|6|9|8|0|N|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

The macro <code>NDEBUG</code> controls whether <code>assert()</code> statements are active or not.
In my view, that is separate from any other debugging - so I use something other than <code>NDEBUG</code> to control debugging information in the program. What I use varies, depending on the framework I'm working with; different systems have different enabling macros, and I use whatever is appropriate.
If there is no framework, I'd use a name without a leading underscore; those tend to be reserved to 'the implementation' and I try to avoid problems with name collisions - doubly so when the name is a macro.

blocks|key|1109941|text|我依赖NDEBUG，因为它是唯一一个其行为在编译器和实现之间都是标准化的(请参阅标准assert宏的文档)。负逻辑是一个小的可读性加速，但它是一个常见的习惯用法，你可以很快适应。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1109942|依赖于像_DEBUG这样的东西就是依赖于特定编译器和库实现的实现细节。其他编译器可能会也可能不会选择相同的约定。|1109943|第三种选择是为您的项目定义自己的宏，这是非常合理的。拥有自己的宏为您提供了跨实现的可移植性，并允许您独立于断言启用或禁用调试代码。不过，一般来说，我建议不要在编译时启用不同类别的调试信息，因为这会增加您必须构建(和测试)的配置数量，但好处可能很小。|1109944|对于这些选项中的任何一个，如果您使用第三方代码作为项目的一部分，您必须知道它使用的是哪种约定。|1109945|entityMap^0|3|6|0|4|6|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|U|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|M|$]]

I rely on <code>NDEBUG</code>, because it's the only one whose behavior is standardized across compilers and implementations (see documentation for the standard assert macro). The negative logic is a small readability speedbump, but it's a common idiom you can quickly adapt to.

To rely on something like <code>_DEBUG</code> would be to rely on an implementation detail of a particular compiler and library implementation. Other compilers may or may not choose the same convention.

The third option is to define your own macro for your project, which is quite reasonable. Having your own macro gives you portability across implementations and it allows you to enable or disable your debugging code independently of the assertions. Though, in general, I advise against having different classes of debugging information that are enabled at compile time, as it causes an increase in the number of configurations you have to build (and test) for arguably small benefit.

With any of these options, if you use third party code as part of your project, you'll have to be aware of which convention it uses.

blocks|key|1109997|text|不幸的是，DEBUG负载过重。例如，建议始终为发布构建生成并保存一个pdb文件。这意味着-Zx标志和-DEBUG链接器选项之一。而_DEBUG涉及运行时库的特殊调试版本，例如对malloc和free的调用。然后，NDEBUG将禁用断言。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1109998|entityMap^0|5|5|18|3|1E|6|1T|6|2G|6|2N|4|2Y|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|G|$]]

Unfortunately <code>DEBUG</code> is overloaded heavily. For instance, it's recommended to always generate and save a pdb file for RELEASE builds. Which means one of the <code>-Zx</code> flags, and <code>-DEBUG</code> linker option. While <code>_DEBUG</code> relates to special debug versions of runtime library such as calls to <code>malloc</code> and <code>free</code>. Then <code>NDEBUG</code> will disable assertions.

Which preprocessor define should be used to specify debug sections of code?

Use <code>#ifdef _DEBUG</code> or <code>#ifndef NDEBUG</code> or is there a better way to do it, e.g. <code>#define MY_DEBUG</code>?

I think <code>_DEBUG</code> is Visual Studio specific, is NDEBUG standard?

_DEBUG vs NDEBUG

应该使用哪个预处理器定义来指定代码的调试部分？使用#ifdef _DEBUG或#ifndef NDEBUG，或者有更好的方法，例如#define MY_DEBUG我认为_DEBUG是Visual Studio特有的，NDEBUG是标准的吗？

问_DEBUG vs NDEBUG
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问_DEBUG vs NDEBUGEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问_DEBUG vs NDEBUG
EN