In fact, nearly all of my programs (interactive and batch) have 
print files defined "just in case" ;-)

I agree with Terry's notion of avoiding SYSOUT - but I would use a called
program/procedure to do the logging.  I would also tend to use a database to
report to rather than a print file simply because I can use SQL etc. against
the debug file to locate entries with specific values.

In the past I have built utility routines of this nature that allowed me to
print and/or database log specific debug messages.

Jon Paris

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.