It's nice when you can stop working on a project at a logical place.
For example, if you're adding a new feature, it's nice to get the
feature finished before you stop. That way when you come back to it,
you don't have to try and remember where you left off. Unfortunately,
this often doesn't happen. I'm sure you have had situations where you
had to stop working on a project right in the middle of fixing a bug or
adding a new feature. You probably got back to it the next day or
perhaps not until weeks or months later. When this happens it can be
time consuming to remember where you left off and what exactly you were
doing.
Here's a neat way to do both. When you have to stop, put in a break
point (or if you have v5 or later, use the BREAK command) and add a
comment that notes what you need to do to finish. The next time you
open the project, all you have to do is run it and the compiler will
stop at the break point or BREAK command and there will be your notes
on what remains to be done.
This tip was suggested by Mike Bailey.
--
Geoff Perlman
President and CEO
REAL Software, Inc.
|