From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Zheng Junjie <zhengjunjie@iscas.ac.cn>
Cc: "Attila Lendvai" <attila@lendvai.name>,
"Ludovic Courtès" <ludo@gnu.org>,
guix-devel@gnu.org
Subject: Re: [shepherd] several patches that i deem ready
Date: Wed, 24 Jan 2024 14:23:44 -0500 [thread overview]
Message-ID: <87a5ouwn5r.fsf@gmail.com> (raw)
In-Reply-To: <87cytqwuhe.fsf@iscas.ac.cn> (Zheng Junjie's message of "Thu, 25 Jan 2024 00:41:39 +0800")
Hi,
Zheng Junjie <zhengjunjie@iscas.ac.cn> writes:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi Attila,
>>
>> Attila Lendvai <attila@lendvai.name> writes:
>>
>>>> About "cheaper code path when a log level is disabled at runtime",
>>>> perhaps it can be improved in guile-lib, but otherwise that's a nice
>>>> list. I just wish we had a good logging library in Guile and could stop
>>>> reinventing the wheel left and right.
>>>
>>>
>>> i've made my judgement that the logger in guile-lib was never applied
>>> seriously when i relized that it stores the enabled state in a
>>> hashtable (which must be looked up for every log statement).
>>>
>>> i made sure the log statements have a unique syntax, so the underlying
>>> machinery can be replaced easily later, and then i moved on.
>>
>> I guess if we were serious at giving Scheme/Guile a great logging
>> library we would try to design it with the help of everyone as a SRFI;
>> it could then be integrated to Guile and any other Scheme, benefiting
>> the ecosystem at large. Is this something you could be interested in
>> trying? I've found the Scheme community around SRFIs very knowledgeable
>> and helpful.
>>
>
> maybe can see srfi-215 Central Log Exchange
> [https://srfi.schemers.org/srfi-215/srfi-215.html]?
That's somewhat related, but is not an actually usable logging library,
just some standard means to dispatch them to various sinks, if I
recall my read of it.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-01-24 19:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 23:38 [shepherd] several patches that i deem ready Attila Lendvai
2024-01-21 9:38 ` Attila Lendvai
2024-01-21 17:49 ` Maxim Cournoyer
2024-01-22 18:38 ` Attila Lendvai
2024-01-23 13:21 ` Maxim Cournoyer
2024-01-24 10:56 ` Attila Lendvai
2024-01-24 13:56 ` Maxim Cournoyer
2024-01-24 16:41 ` Zheng Junjie
2024-01-24 19:23 ` Maxim Cournoyer [this message]
2024-01-24 17:11 ` Attila Lendvai
2024-01-26 9:50 ` [OT: s/Joshua/Josiah/ in sig ;-] " bokr
2024-01-26 21:50 ` [OT: s/Joshua/Josiah/ in sig ; -] " Attila Lendvai
2024-04-02 10:43 ` Attila Lendvai
2024-04-10 16:32 ` Ludovic Courtès
2024-04-18 12:15 ` Attila Lendvai
2024-05-23 17:48 ` Attila Lendvai
2024-05-24 16:57 ` Attila Lendvai
2024-05-26 19:02 ` Attila Lendvai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5ouwn5r.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=zhengjunjie@iscas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).