[Steely Tom]

Magic numbers aside, I’m confused about how adding a “goto” to C++ code is an “improvement.”

[ShadowAce]

There's nothing wrong with goto if it is coded properly.

Using it just to create spaghetti is not coding properly. Using it to exit is, IMHO.

[so_real]

I'm not a big fan of "goto" statements either. But they do serve a purpose, and I'll give them a pass when used to fill the "abort on failure" situation. That being said, "do {} while(0);" with an error code set and a "break" on failure is, IMHO, more structured and readable than a "goto". I call it my "breakable IF statement".

[Montana_Sam]

...adding a "goto" to C++ code ...

Actually, the code is 'C', not 'C++' (quoting from the referenced email, the file name is "net/ipv6/ip6_output.c".

That being said, getting gracefully out of a deep dive into a multidimensional 'for' loop is sometimes best achieved with a 'goto'. Seldom, but occasionally. ;)