熟练使用Boost.Log日志库？ [英] Experience using Boost.Log logging library?

问题描述

我正在考虑开始使用 Boost.Log日志库。使用Boost.Log人？请在这方面分享您的经验。

I am considering starting to use the Boost.Log logging library. Is anyone using Boost.Log? Please share your experiences in this regard.

我正在考虑其他的库是Apache的log4cxx（似乎繁琐的安装，但我的队友们想要的东西简单的上手）和Pantheios（同样的问题，因为它有额外的前端和后端的工作）。

The other libraries I am considering are Apache log4cxx (it seems tedious to install but my team mates want something simple to get started) and Pantheios (the same problem since it works with extra front and back end).

推荐答案

我已经成功地集成Boost.Log在我的游戏引擎，我只能说说它的好东西。当然，这是一个有点早使用，因为第2版将成为实际的版本，这将成为正式Boost.Log。

I've successfully integrated Boost.Log in my game engine and I can only talk good things about it. Sure, it's a little early to use, since version 2 will be the actual version that will become the official Boost.Log.

当心版本1.0可以不被维持。接收更新，必须使用最前沿（主干）版本，这可能会变得不稳定。考虑到这一点，如果你要在任何严肃的项目中使用这个版本。如果你不害怕使用尖端的版本或将来的破损，然后去了。它真的很好用，因为它是在其目前的状态。

Beware that the version "1.0" available is not being maintained. To receive updates you must use the bleeding edge (trunk) version which might become unstable. Take this into account if you are going to use this version in any serious projects. If you are not afraid to use bleeding edge versions or future breakage, then go for it. It's really nice to use as it is in its current state.

我一直以为在log4j的/ log4cxx层次记录系统是优越，但Boost.Log已经让我思考，否则。过滤和属性的方式更加灵活。

I've long thought the hierarchical logging system in log4j/log4cxx was superior, but Boost.Log has got me thinking otherwise. Filtering and attributes is way more flexible.

由前端/后端分离汇的设计使得它很容易增加额外的后端。没有必要担心它是由前端处理同步问题或过滤。
该库还附带了大量的后端则已，旋转文件，控制台，系统日志，Windows事件寄存器等。

The design of sinks separated by frontend/backend makes it really easy to add additional backends. No need to worry about synchronization issues or filtering which is handled by the frontend. The library also comes with lots of backends already, rotational files, console, syslog, Windows event register, etc.

我写我自己的水槽后端;一个人去在游戏控制台和一个一种通知系统，为更严重的事件。比我想象得容易，受够了，并在短短几分钟内运行。

I have written my own sink backends; one goes to the in-game console and one to a kind of notification system for more serious events. Was easier than I expected, had it up and running in just a few minutes.

最后但并非最不重要的，维护者/开发商真的有帮助。你会得到很多帮助项目论坛。他定两个错误（为这事一个主要的），只是这个周末，我报： - ）

Last but not least, the maintainer/developer is really helpful as well. You'll get plenty of help in the project forums. He's fixed two bugs (whereof one major) just this weekend that I reported :-)

这篇关于熟练使用Boost.Log日志库？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！