Question

What is role of comments

Answer 1

Comments are used to give a context to the reader of the code that what is the code about.

Answer 2

Comments are completely ignored by the compiler. They are used by the code-reader(human) to understand the concept/syntax of the code.

Answer 3

Comments in Code is very helpful specially when you are working on big projects then before every section of code you can write a Line in your own language even and mention what about this code actually and what's doing here. So, In future it will be easy for you to update this code easily.

Answer 4

Comments are used to give a context to the reader of the code that what is the code about.

Answer 5

Comments are often recommended when the code is specific to some particular business logic , or maybe complex that just by seeing the code someone else cannot understand it completely. It  can help to give more context on the code to a third person looking into code.

In general it is recommended to make code simple enough to understand and maintained by anyone in future without the need of additional comments added. But in specific cases we tend to write code which deviate from normal flows or add more complexity to the code, where comments can help a new developer to understand and maintain it. On a lighter note i have seen code comments like " god know why this is added" :)

Answer 6

comments are used to understand the executer what information are they giving. But, in some most of the cases they used to print the content/code .

Answer 7

Comments are explanatory statements that help the reader in understanding source code. They can be entered at any location in the program. They are ignored during program execution which means they are
not executable statements.

Answer 8

when someone refers your code or even you refer your code again after long time it becomes easy to understand and you can differentiate block of code accordingly

Answer 9

Better understanding of code and structure of programing.

Answer 10

Comments should identify the "why" of a design decision's code--never the "what".

Some pre-processing tools, such as doxygen or a code verification scanner, actually need directions "hidden" in comments so that the language compiler won't notice them.