What is correct way of putting comments into code for C/C++...

/* ▒███▒ ███ █▓██ ░███░ █▒██▒ ░███░ █████ ███ █▒██▒ █▒ ░█ ▓▓ ▒█ █▓ ▓█ █▒ ▒█ ██ █ █▒ ▒█ █ █▓ ▓█ ██ █ █▒░ █ █ █ █ █ █ █ █ █ █ █ ░███▒ █████ █ █ ▒████ █ ▒████ █ █ █ █ ▒█ █ █ █ █▒ █ █ █▒ █ █ █ █ █ █░ ▒█ ▓▓ █ █▓ ▓█ █░ ▓█ █ █░ ▓█ █░ █▓ ▓█ █ ▒███▒ ███▒ █▓██ ▒██▒█ █ ▒██▒█ ▒██ ███ █ █ █ █ */

\x6b\x65\x6b\

It's not guaranteed how characters beyond 0x7f are going to be displayed (.nfo style shit generally relies on plain old codepage 437, use anything else and it'll look like random crap).

Pic related is a great example of self-documenting code where comments arent' necessary in the first place.

Attached: hurr_fizzbuzz.png (621x942, 34.22K)

Typically in the header file, I'll document each of the functions, there arguments, any restrictions, and return value. In the source file, functions are only commented if they have a complicated procedure to follow. Inside of functions comment things that aren't obvious in what you are doing. Finally, I like to break some functions up with an abstract description of what is trying to be done in the following code.
In addition to these comments, you should be writing "self documenting code."

That's not self documenting.

You put quotation marks around it to turn it into a no-op string literal.
That doesn't work if you already use string literals in your code but real programmers don't work with text anyway.

That's fucking perfect. You are hired. Welcome to the team

Attached: 15104322882630.jpg (750x562, 76.21K)

It was more of a LARP tbh, though it can be done in UTF8 as well as CP437.
It is simple to convert between codepages, either in the terminal display or file format itself.

Attached: stop.jpg (500x335, 18.7K)

what's the candy it looks really good but im allergic to peanuts