the new math: old battle of the lovees was: PDP1 3589

You have my permission; splitting the process up into these three categories is very useful.

This is a really good distinction to make. This thinking was almost automatic in my neck of the woods. And nobody argued if someone questioned an buttumption at any time.

This is similar thinking styles to what I've been arguing with in the so-called political discussions. Have you figured out how to unwedge that kind of thinking style w.r.t. coding, which about as determinant as one can get?

YES! That is mostly what debugging is all about. I suppose you can call them sanity checks but people misinterpret the term to be a discrete check rather than a process.

If you could realize how odd this sentence is to me...:-). I can't think of any other way to develop code. It is one the reasons I asked RDH to implement an undocumented feature of DDT. You can write a series of DDT instuctions, store it, and have them executed whenever a specified breakpoint is reached. It made my life of debugging BACKUP so much easier.

He's had a 25-year-long mental kiss because of that work.

BTW, thanks for giving the discussion this kick in the butt. Making the three distinctions is very important.

BAH