Closed ggerganov closed 3 years ago
Awesome :)
I see the global is not protected by a lock, so the function is not threadsafe (not a problem in my usecase), but it would be worthwhile to document it ;)
I'm assuming setting it to NULL disables logging all together?
Good point - will add comment that setLogFile()
is not thread-safe and should not be called in parallel with other methods.
I'm assuming setting it to NULL disables logging all together?
Correct
ref #51
Using
GGWave::setLogFile()
it is now possible to change the log file used internally by ggwave, or disable it all together.The
C
interface function is respectivelyggwave_setLogFile()
I guess we can design a better interface in the future, but for now this seems to be simple enough and does the job.