Re: [MirageOS-devel] Logging

[Drup <drupyog+caml@xxxxxxxx>]

> Agreed. I had in mind a branching structure that would include a branch per 
> component, followed by the debug levels.  Other listeners could then do 
> aggregation into different views, including operations such as time-based 
> rotation and aggregation across components.  For an Irmin backend, such 
> listeners can just be watchers (either offline or online, which is nice!).
If I understand correctly, this would allow to encode Lwt_log's sections 
quite easily, is that right ? It is a feature that I found rather 
lacking in other logging libraries (in particular, dolog).
I like your "only one function" idea.
The alternative of passing around the unique function is to have a 
global reference containing the dispatcher function. It's the solution 
used by Lwt_log. It's mostly equivalent (and it works ok in practice) 
but I think it's indeed better to pass the function explicitly.
I'm not really convinced by the extension syntax trick (it was done for 
Lwt_log too and it uses a very syntactic criteria, which makes it a bit 
fishy). What would it do exactly ? Can't you rely on partial evaluation 
and Flambda's inlining to do the correct thing ?

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel