5 ms·
Having been a longtime coder in a language that doesn't support Todo tasks (tooling doesn't find them) I've seen double commenting a line as a trick to make the
by Forge36 4y ago
Having been a longtime coder in a language that doesn't support Todo tasks (tooling doesn't find them) I've seen double commenting a line as a trick to make them easily findable (it's the fastest thing to type).
It's a personal hack for being able to quickly find them. Ctrl+F //// is a reasonable "Todo" And one which on a single person project I can get away with. Because they are also valid comments persisting past release occasionally happens as (in my case) the second reviewer doesn't know this convention.
Working on a project for the past several months I've left many todos in my code to be reviewed. In most cases by myself when I better understand the problem. I am after all the first person to review my own code.
- andirk 4y agoTheir comments are quite sloppy in other ways, too. They use the `//` on many lines, instead of the common `/* ... */` like: // Why base-58 instead of standard base-64 encoding? // - Don't want 0OIl characters that look the same in some fonts and // could be used to create visually identical looking account numbers. // - A string with non-alphanumeric characters is not as easily accepted as an account number. // - E-mail usually won't line-break if there's no punctuation to break at. // - Doubleclicking selects the whole number as one word if it's all alphanumeric. //
- crecker 4y agoThank you for this comment. For todo comments, Satoshi or whoever was used "//// todo: " so it might be for that too.
- Forge36 4y agoPersonally: I use both! I've also noticed myself forgetting "Todo:". Sometimes it's the ":" and the tooling doesn't pick it up. If I've really screwed up its "tod:".