Sorry: SECOND attempt to describe what I'm talking about:
The major question (from *my shop*) is:
Why the hell should a PRODUCTION Version of a Compiled Class
STILL use TRACE, when it is already debugged ??
Wouldn't it be better to seek for other mechanisms, for the run-time version
to seek for OTHER methods, like ASSERTIONS ?
I'm loving ASSERTIONS!
My (personal) notation of an ASSERTION is (for example)
x=3
y = x ::= 3
Syntax:
On the left hand side (before the ::) is a NetRexx Statement
On the right hand side (after the ::) is a RELATIONAL OPERATOR
and a RESULT.
WHEN the result of the statement (on the left hand side of the original
statement, y in the example above) does NOT MATCH the assertion,
an ASSERTION message (ordinary followed by an ABORT, UNLESS in TEST
Mode) is issued ....
What do you think about this approach (when interested.. ) ?
The whole approach has been derived from JUnit, and does use JUnit, of
course, for the Details ....
I'm putting them into my programs, and they do tell me, when
some algorithms of mine are wrong (which happens from time to time) :-(
I'm only using TRACE in the early DEVELOPMENT CYCLE of a
program.....
... *OR* , when I found a *BUG* , *to DEBUG the BUG* (of my program)
(Sorry, MFC, to say that)
Thomas Schneider.
Tom. (ths@db-123.com)
Locked
