[email protected] writes: Hi Andreas,
> I'm not sure if I understand you correctly. > You can use (log) in different ways, e.g.: > (log "just a message") > (log 'debug "variable x is" x) > (log 'warn "folder size is reaching >1GB") > (log 'error "a fatal error occured") > > If (on *LogOn), all messages get printed. > If (setq *LogOn 'warn), only warn and error messages (the 2 at bottom) > will be printed. > If (setq *LogOn 'error), only the last message will be printed. ok, I see, so its the programmers responsability to put 'warn and 'error level statements in places that are only reached under some error condition and nowhere else. > So far this system only handles messages which you explicitly send > yourself with (log Type any ...). Error ouput from pil isn't getting > handled, as I don't know how I could do that. Pil error messages can be > redirected to a file with (err), but I don't see a way to get it > redirected to a function... > > Does this answer your question? Yes, thanks! >> Thorsten Jolitz <[email protected]> >> writes: >> >> after testing a bit more I have one question: >> >> It seems the levels 'warning and 'error unconditionally print their >> messages when *LogOn is set to them, but from my understanding these >> levels would eventually be turned-on in production code and thus >> should only print something when something goes wrong in the program >> execution. >> >> Would it be possible to only log messages from catched error with level >> 'warning and try to log some system information when there is a real >> uncatched error with log-level 'error? So that level 'warning would >> become the default level for production code and nothing is printed as >> long as the program runs smoothly? >> >> -- >> cheers, >> Thorsten >> >> -- >> UNSUBSCRIBE: >> mailto:[email protected]?subject=Unsubscribe >> > > > -- cheers, Thorsten -- UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
