Thanks Andy (and Dr. Scott). I'll have a look at those things.
I used a log book for years and switched to DevonThink about 3 years
ago. DevonThink was a real improvement (until I started working on
multiple machines and using subversion; I've got to see if there's a
way to share a DevonThink database across machines) because it's
searchable, organizable, etc. etc. However, I really prefer to put
checks in the code, even if they're blocked out by #if
DebugBuild...#endif. I use asserts regularly, although introspection
would sure make them better. It would also be nice to have pure
virtual functions and class methods but I expect we'll get them
eventually.
Thanks again for your replies.
Dave
At 2:51 PM +0800 1/11/07, Andy Dent wrote:
On 11/01/2007, at 7:13 AM, [EMAIL PROTECTED] wrote:
t I'm trying to prevent a class of bugs where I fail to update all
the code required to save, restore (or transmit & receive) an
object. I add a new field and, say, get interrupted and forget to
do the last update to a method.
I catch this by writing things down, see some discussion of my
Diary-based Development method at
http://www.oofile.com.au/adsother/sse.html
As I record all property and method changes under a single heading
for a given task, it is a lot easier to audit what I have done.
Note that this is also the kind of thing that support for Scott
Steinman's RealityCheck project might help - we could end up with
the equivalent of PC-Lint for REALbasic.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
