Posted by Bob A on July 19, 2011 at 06:31:28:
I envision utilising the new TRACE statement with control of tracing being done at compile time as follows
SET TRACE=TRUE
.ifdef TRACE
Trace On
Trace Labels On
Trace Source On
.endif
with Trace Print "Overlapping Date Detected" and other "Trace Print" statements not being conditioned on the .ifdef TRACE
Most of the time, TRACE is all I need.
is consideration perhaps being given to a "WATCH" statement (I've had something like this in some DEBUG processors I've used), where a variable list is WATCHed and only printed in the TRACE where it changes? Sometimes, there are only a few flags that need to be tested, and in conjunction with being able to TRACE where we are in the code, the debug process is greatly speeded up.
This new statement will greatly simplify the process I've developed over the past 2 years of IB programming where I've salted "RTN$ = 'routine name'" statements throughout the code, and then the ERRORTO statement prints out the RTN$ value, so I know the last place I was... this has been very tedious and annoying, both in coding and in narrowing down where the code failed... TRACE will be much easier, faster and useful.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.