Re: Logging librarie (Re: Debugging COMM:START-UP-SERVER hang)
"Tim Bradshaw (as tfb at cley dot com)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <[email protected]> |
On 2 Mar 2026, at 12:07, David McClain <[email protected]> wrote: > > Seems like the signaling overhead would be heavier than function call/return, no? Logging is not just calling a function. It's saying 'hey, something interesting happened with some properties, does anyone out there care?' with the usual answer being 'no', or 'only if the thing you said has such-and-such a property' or 'on Tuedsays, before 12'. So you can build such a thing which will certainly involve, for instance, binding things that want to handle log messages to special variables and so on, or you can realise that CL already has such a mechanism and use that. slog was an exercise in doing the latter, as well as trying to avoid the vast bureaucracy that seems to infest logging systems. It might be slower than a dedicated system could be. But I generally don't log events in inner loops. Things may come out in non-monotonic time order, especially with multiple independent threads / machines logging. That's what happens with 'industrial' systems as well and is really unavoidable without very significant costs. --tim _______________________________________________ Lisp Hug - the mailing list for LispWorks users [email protected] http://www.lispworks.com/support/lisp-hug.html