search for: n3376

...ION OF 'UNINTENDED FALL-THROUGH IN SWITCH STATEMENTS' DIAGNOSTIC IN CLANG* Related functionality in clang introduces several diagnostic messages and a syntax for intended fall-through annotation, based on C++11 attributes ([dcl.attr], http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3376.pdf, 7.6). The [[clang::fallthrough]] attribute should be applied to a null statement placed in a point of execution where fall-through to the next switch label occurs, e.g.: switch (n) { case 0: ... // no break here case 1: // warning: unannotated fall-through between switch labels...

...alized value as a function argument is undefined behaviour on the spot, regardless of what the callee does (even if it never references that argument). > > Cite reference? No? Then you're guessing ;) This is a rule in C++ that I'm not sure also applies to C. The applicable text from N3376 is: "When a function is called, each parameter shall be initialized with its corresponding argument." [expr.call]/4 the initialization performs lvalue-to-rvalue conversion, which is what ultimately triggers explicit UB: "If the object to which the glvalue refers is not an...

On 24/11/2012, at 10:21 PM, Nick Lewycky wrote: > > Passing an uninitialized value as a function argument is undefined behaviour on the spot, regardless of what the callee does (even if it never references that argument). Cite reference? No? Then you're guessing ;) > > That aside, there is no way that 'i' has the same value, since it has no value. This is definitely

...AGNOSTIC IN CLANG* >>> >>> Related functionality in clang introduces several diagnostic messages >>> and a syntax for intended fall-through annotation, based on C++11 >>> attributes ([dcl.attr], >>> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3376.pdf, 7.6). >>> >>> The [[clang::fallthrough]] attribute should be applied to a null >>> statement placed in a point of execution where fall-through to the next >>> switch label occurs, e.g.: >>> >>> switch (n) { >>> case 0: >>&g...