KingPresident
Member
Thank you.
Not hours, but days have been saved.
Not hours, but days have been saved.
Wish I could say "Your Welcome"
my boss and others told me to stop commenting my program rungs.
Commenting for the sake of comments can be as useless as no comments. If a line consist of you adding a factor to a variable and your comment is "Multiply with 2.8", then you are not helping anyone."right on. As long as you comment every rung of code you write, you and I will get along just fine."
Commenting for the sake of comments can be as useless as no comments. If a line consist of you adding a factor to a variable and your comment is "Multiply with 2.8", then you are not helping anyone.
So the purpose of comments should be exactly that: the purpose of the code. Not what you are doing, but why.
- Write the EXHAUSTIVE comments on rungs at the end of the program or subroutine or AOI.
- THEN write the summary comment (Brief) described above, and reference the longer description at the end of the program. Sort of like footnotes?
- Write the EXHAUSTIVE comments on rungs at the end of the program or subroutine or AOI.
- THEN write the summary comment (Brief) described above, and reference the longer description at the end of the program. Sort of like footnotes?
That is an interesting idea. You find that the end works better than the beginning just to avoid extra scrolling at the top of the program?