|
|
|
|
|
by letsgetphysITal
2933 days ago
|
|
Swearing in general doesn't damage morale, but swearing at and verbally abusing someone does very much so. That's exactly the kind of treatment that would lead me, if I were a developer, to walk away from the project. In fact, here's an edit which gets his point over in less words, and more clearly: "Honestly, this looks questionable to me. [U]sing a union to do type punning is the traditional AND STANDARD way to do type punning in gcc. In fact, it is the documented way to do it for gcc. The fact is that gcc documents type punning through unions as the "right way". You may disagree with that, but using the [C] standard to push it - the same standard that came up with the completely mis-guided aliasing rules - is not a valid argument. his is why we use -fwrapv, -fno-strict-aliasing etc. The standard simply is not important, when it is in direct conflict with reality and reliable code generation. So what's the _real_ reason for avoiding union aliasing?" No swearing, no abuse, all points covered, less typing required. No talk of splinters. |
|
The chances that you get to hear things from the source and never hear things in a way you don't like is almost zero. You have to make a decision.