g++ -Wreorder 的意义何在?

What#39;s the point of g++ -Wreorder?(g++ -Wreorder 的意义何在?)
本文介绍了g++ -Wreorder 的意义何在?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

g++ -Wall 选项包括 -Wreorder.该选项的作用如下所述.我不清楚为什么有人会关心(尤其是在 -Wall 中默认打开它).

<上一页>-Wreorder(仅限 C++)当代码中给出的成员初始化器的顺序不正确时发出警告匹配它们必须执行的顺序.例如:结构 A {诠释我;诠释 j;A(): j (0), i (1) { }};编译器会将 i 和 j 的成员初始化器重新排列为匹配成员的声明顺序,发出警告影响.此警告由 -Wall 启用.

解决方案

考虑:

结构 A {诠释我;诠释 j;A() : j(0), i(j) { }};

现在 i 被初始化为某个未知值,而不是零.

另外,i 的初始化可能会产生一些副作用,这对顺序很重要.例如

A(int n) : j(n++), i(n++) { }

The g++ -Wall option includes -Wreorder. What this option does is described below. It is not obvious to me why somebody would care (especially enough to turn this on by default in -Wall).

-Wreorder (C++ only)
  Warn when the order of member initializers given in the code does not
  match the order in which they must be executed.  For instance:

    struct A {
      int i;
      int j;
      A(): j (0), i (1) { }
    };

  The compiler will rearrange the member initializers for i and j to
  match the declaration order of the members, emit-ting a warning to that
  effect.  This warning is enabled by -Wall.

解决方案

Consider:

struct A {
    int i;
    int j;
    A() : j(0), i(j) { }
};

Now i is initialized to some unknown value, not zero.

Alternatively, the initialization of i may have some side effects for which the order is important. E.g.

A(int n) : j(n++), i(n++) { }

这篇关于g++ -Wreorder 的意义何在?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

Rising edge interrupt triggering multiple times on STM32 Nucleo(在STM32 Nucleo上多次触发上升沿中断)
How to use va_list correctly in a sequence of wrapper functions calls?(如何在一系列包装函数调用中正确使用 va_list?)
OpenGL Perspective Projection Clipping Polygon with Vertex Outside Frustum = Wrong texture mapping?(OpenGL透视投影裁剪多边形,顶点在视锥外=错误的纹理映射?)
How does one properly deserialize a byte array back into an object in C++?(如何正确地将字节数组反序列化回 C++ 中的对象?)
What free tiniest flash file system could you advice for embedded system?(您可以为嵌入式系统推荐什么免费的最小闪存文件系统?)
Volatile member variables vs. volatile object?(易失性成员变量与易失性对象?)