// TODO: fix
-
Don't you just love it when you leave yourself a note like this in the code, but without an explanation of what's wrong / needs to be fixed? Especially if it's not something obvious :doh:
#pragma message
Paul Sanders http://www.alpinesoft.co.uk
-
I never liked 'TODO' comments in the code. I rather keep a plain text file in the project directory listing all the things that should be remembered and considered. Then I can be sure that I don't overlook a fix because I didn't open that source file. I can more easily sort out a group of related fixes and do them in one cleanup. And I can put in a reminder about planned/desired functionality that doesn't yet have any definite place in the source code of already implemented functionality. In my text files, the entries are not necessarily limited to strict coding actions. They may e.g. state the defined order of method parameters for this project, or identify the standards to be followed. Sometimes it grows to require a splitting into sections. Some of that information later goes into the system documentation.
Visual Studio has a Task List view which brings them all together which I think is better than having a separate file which may or may not get updated when then 'TODO' is done.
-
I do that all the time. :doh:
cheers Chris Maunder
