Timeline for Is there a method for differentiating informative comments from commented out code?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 6, 2019 at 18:09 | comment | added | IanF1 | @cmaster Ah I see, I think I misunderstood the question. I provided a simple way of formatting the comments in such a way that they can be easily parsed for type, which isn't what was asked for. | |
| Jul 6, 2019 at 17:01 | comment | added | cmaster - reinstate monica | This depends totally on style: When I comment out code, I generally add the // to the first column, and since virtually all code is indented, the result is virtually always that the comment starts with some tabs. Normal comments don't get a leading space from me, unless there are already other comments with a leading space in the vicinity. So, your method would fail abysmally on comments that I produced, and any method designed to recognize my comment patterns would fail abysmally on yours. | |
| Jul 6, 2019 at 11:35 | review | First posts | |||
| Jul 8, 2019 at 8:46 | |||||
| Jul 6, 2019 at 11:32 | history | answered | IanF1 | CC BY-SA 4.0 |