5 ms·

This is excellent. I always fail to keep track on my TODOS in files. Very useful.

• skrebbel 12y ago
  Use a decent editor.
  • middus 12y ago
    Alternatively, you could continue using your editor of choice for editing and use grep to identify TODOs in your code.
    • andywaite 12y ago
      Yes, if you're disciplined, and remember to do this regularly. But humans aren't perfect.
      • oinksoft 12y ago
        In smaller codebases you can use a git hook to display your TODOS: http://oinksoft.com/blog/view/5/ http://oinksoft.com/blog/view/5/
• watwut 12y ago
  My TODO comments show up in nice view in GUI I use (Eclipse). I'm sure other GUIs have similar views somewhere. I'm also sure that plugin to turn old ones into syntax errors could be done in a day or two. That sound like much safer approach then runtime exception.
  • aaronem 12y ago
    A day or two, really? That seems like an awfully long time requirement for what should be a simple change.
    • recursive 12y ago
      If you're experienced making Eclipse plugins, it would probably be under an hour. If you're not, it could take you a day to learn how.
    • watwut 12y ago
      I'm sure it is a simple change. The hard part is to find out where exactly should you do that simple change and how exactly should you do it. If you do not have experience with related APIs, you will need a day for googling and reading. Eclipse framework is huge and not all its parts are immediately understandable.