13 comments

[ 3.2 ms ] story [ 30.5 ms ] thread
I do this to embed shell commands at the beginning of short one-file C/C++ programs to execute when hitting an F key in my text editor. I usually put very basic compile-and-run commands. It's wrapped in #if and #endif which are comments in many shells. I end the commands with exit so it doesn't try to execute the code as commands.
This is why you should only use /* */ as your comment style.
Quite a time ago, my colleague accidentally committed a Youtube url to our Java codebase (middle-click accidental paste, no code review at that time). We had some laughing moments when we discovered it, as it was compelling evidence that he was watching videos during work, and even we knew what he was watching at that time.
Of all the (ahem, not as many as hoped) things C++ got right, // comments are one of the best ones

And I'm glad it now is part of C as well

I remember working on some code back in ’99 when the other dev on the project used // comments in C code which, it turned out, were supported by the C compiler we were using, but which broke the embedded SQL preprocessor.
Clearly, the "http:" is parsed as a label (for goto), and the subsequent "//", as a C++ or C99 comment. This shouldn't give you more than a moment's pause if you know C.
You can only have one URL for each scheme though, else your compiler will report something like

error: redefinition of label 'https'

This puzzle would become extra trivial with syntax highlighting.
Nice.

Another neat comment-based construct is the good old:

  //*
     foo
  /*/
     bar
  //*/
It yields 'foo' as is, and 'bar' if the first slash is removed.
At least when using -Wall the compiler will give you the warning

  <source>:5:5: warning: label 'https' defined but not used [-Wunused-label]
as a hint.
That's exactly how we found an accidental copy/paste of an internal URL in our source code.
Wouldn't there be a warning about an unused goto label