Add logging

[GoogleCodeExporter]

Since the major code changes since the 1.71 release have left EOF occasionally 
unstable, I think it would be worthwhile to implement a function such as 
eof_debug(const char *).  It could conditionally write to the open log file if 
logging was enabled in the options. The logging can be kept out of the main 
program loop and extremely time intensive functions such as the audio callback 
routine, but initially, a log entry each time a manipulation function (such as 
adding/deleting a note) started and ended may be good to track down which 
functions have glitchy code.

Original issue reported on code.google.com by raynebc on 20 Mar 2011 at 2:14

[GoogleCodeExporter]

On second thought, eof_log(const char *) would be a better name.

Original comment by raynebc on 21 Mar 2011 at 3:41

[GoogleCodeExporter]

Begun in r731.

Original comment by raynebc on 16 Apr 2011 at 8:05

• Changed state: Started

[GoogleCodeExporter]

r755 adds logging level functionality.  Some functions will now only log if 
level 2 (verbose) is in effect, reducing superfluous logging that occurs during 
import/load/project close.

Original comment by raynebc on 15 May 2011 at 10:14

[GoogleCodeExporter]

By now, EOF has been designed to generate a random three digit number during 
launch.  This instance ID is used in log entries, eliminating the issue of 
multiple simultaneous instances of EOF mixing their logging so that they cannot 
be told apart.  This is probably the best workaround, since there's no simple 
way to lock a file using the standard C I/O functions.

Original comment by raynebc on 16 Sep 2011 at 8:38

• Changed state: Done