2016-04-26 20:16 GMT+02:00 Sven Van Caekenberghe <sven@stfx.eu>:

Try to look at it this way: by using objects (events, signals, announcements, whatever) and just generating them on the spot and sending them off somewhere, you have everything you need, without imposing any restrictions.

If logging system will not allow me to log arbitrary object it would be restriction. And by "log object" I mean not just adding it to some log collection. But I need ability to mark objects with tags, messages and timestamps.

��

If you want to use log/severity levels and/or categories and/or tags, you can do that. But I don't want to. Your objects will contain that info and you will be able to filter on it.

Most of objects not have timestamp, tag or user message. So I can't filter them in such naked state. And instead of generating special objects with such information I want logging library take care about it.��

Of course for some cases I will need special objects for logs. But I should not be forced to do it every time.��