3 ms·
While I'm fuzzy on the details now, one problem we had, back in the 1990s, was in C++ code which used comments with "\"s to make it look pretty. /// I am a
by dalke 13y ago
While I'm fuzzy on the details now, one problem we had, back in the 1990s, was in C++ code which used comments with "\"s to make it look pretty.
/// I am a comment! \\\
a = 5;
The SGI OCC compiler accepted it just fine, as did most of the other compilers. I wasn't until we compiled on HP, or perhaps AIX, that we had a compiler which elided the "\" + newline to give
/// I am a comment! \\a = 5;
and caused the downstream code to fail.
As for heisenbugs specifically, I agree with you. I just wanted to tell a story. :)
- cnvogel 13y agoI had a similar story I'd like to share. A colleague had written out the initialization data for some embedded component, and helpfully included the ASCII representation for some of the (mixed) binary/readable stuff we sent. So he wrote something along the lines of... unsigned char initdata[] = { 0x01, // some value, e.g. 513 0x02, // as 16bit, little endian 0x40, // ASCII @ 0x5c, // ASCII \ 0x42, // ASCII * 0x09, // number 9 (...) };
- mansr 13y agoC99 explicitly does \-splicing of lines before comment processing: //\ this is a comment /\ / this is also a comment GCC has an option (-Wcomment, enabled by -Wall) to warn about this and other likely mistakes involving comments (e.g. nested /* */ comments).