May 2005 - Boost - lists.preview.boost.org

Logging library - your own scenario!
by John Torjo 23 May '05

23 May '05

Hi all, In order to make the Logging lib as usable as it can be, I'd like to know what is *your* scenario, when using a Logging lib. Thus, I'll do my best to make it as easy as possible to use my lib, and also tweak it to be easily usable in most common scenarios. Even if you scenario fits an already described one, please just reply to that email with something like "mine too!", so that I'll know which scenarios are most common. Thanks! Best, John -- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -v1.6.3 (Resource Splitter) -- http://www.torjo.com/cb/ - Click, Build, Run!

15 37

[serialization][test] Helping end-user testing serialisation
by Loïc Joly 23 May '05

23 May '05

Hello everybody, I think I have some idea that might improve the ease for the end user to test if he properly set-up his class for serialization. Sorry if this idea has already been discussed (or even is already implemented), but I tried to search a little, without finding anything about this. The main idea is that if an user has a serializable class, he will probably want to test wether he forgot to put some usefull member data in his |serialize function. Thus, he will have to write some test with always the same pattern. My suggestion is to put test_tools.hpp inside the serialization library, along with some template :| || |template<class T> void check_serialization(T const &t) // t should not be initialized to default values| |{| | const char * testfile = boost::archive::tmpnam(NULL);| | BOOST_REQUIRE(NULL != testfile);| | {| || std::ofstream ofs(testFile); | boost::archive::text_oarchive oa(ofs);| | oa|| << t;| | }| | { ||| T t1; || std::ifstream ifs(testFile, std::ios::binary); | boost::archive::text_iarchive ia(ifs); | ia >> t1 ||| }| | BOOST_CHECK_EQUAL(t, t1);| | std::remove(testfile);| |||}| |||| Do you think it would make a worthy addition ? -- Loïc | |

3 2

[Boost-bugs] [ boost-Bugs-1206663 ] call to split_winmain raises exception for 8-bit locale
by SourceForge.net 22 May '05

22 May '05

Bugs item #1206663, was opened at 2005-05-22 13:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1206663&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: call to split_winmain raises exception for 8-bit locale Initial Comment: This bug is detected for boost::program_options::split_winmain function and debug version CRT of the VC 7.0 under WinXP. The problem is: split_winmain (winmain.cpp, line 62) uses isspace() from VC CRT. The isspace() got int value which < 0 and not EOF and raises exception. That int value is russian symbol in rus_russia.1251 locale and casted to int. Before to call to winmain i had setted locales for CRT and STL: if (NULL == setlocale(LC_ALL, "rus_russia.1251")) { ... } std::locale::global(std::locale("rus_russia.1251")); ... I suppose, there is simple fix: change isspace(*i) call to isspace((unsigned char)*i) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1206663&group_… ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[build] relative vs absolute
by Yuval Ronen 22 May '05

22 May '05

Hi all. I have a question which is somewhat Boost-related and somewhat general. I've looked at the build system (i.e, Jam files) and noticed that most of time, the directories (include directories, link directories) are specified in absolute format - $(BOOST_ROOT)/whatever. However, not all of them are absolute. Some are relative - ../../../whatever. Other parts of the Boost tree, such as the html files, contain relative paths. My question is: shouldn't there be a uniform way - absolute or relative? And if so, what would it be? My opinion is that relative is superior, because is makes it possible to checkout several instances of the tree (several branches, or even several instances of head) to separate parts of the disk and work on all of them as needed, without mangling with environment variables. What I mean is that requiring to change environment variables is burdensome and errorprone (I can easily execute bjam from directory X, while BOOST_ROOT points to directory Y, which will create a disaster). What is your opinion regarding this in repect to Boost, and in respect to other projects in general? Many thanks for your time, Yuval

3 9

regex documentation redirected
by Stephen Lamb 22 May '05

22 May '05

Not sure if this is intentional but http://www.boost.org/libs/regex/index.html is redirecting to http://www.boost.org/libs/regex/doc/index.html. It would be nice for users to eliminate the redirection and go directly to the correct page. Thanks, Steve

2 1

Re: [boost] [serialization] autolinking
by JOAQUIN LOPEZ MU?Z 22 May '05

22 May '05

----- Mensaje original ----- De: JOAQUIN LOPEZ MU?Z <joaquin(a)tid.es> Fecha: Domingo, Mayo 22, 2005 1:56 pm Asunto: [boost] [serialization] autolinking > I'd like to know which the circumstances are > under which Boost.Serialization autolinking feature > kicks in. > > Last time I discuseed with Robert about this > (see http://lists.boost.org/MailArchives/boost/msg78596.php) > seemed that autolinking won't affect programs > that are only including boost/serialization/* headers > but *not* including any of *_?archive.hpp. > But recent tests in the mslater regression runner > (for instance http://tinyurl.com/a3n6u) suggest > that this may not longer be true. Clarification, > please? Thank you, > For the record, multi_index metacomm tests have just begin failing in msvc-stlport and vc7, for the very same reason, see for instance http://tinyurl.com/7ewf4 http://tinyurl.com/cpyoa Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Building from current CVS
by Marcin Tustin 22 May '05

22 May '05

I'm trying to build from the current CVS (actually about a week old), and it has some weird problem with creating files and directories. When trying to build with a version of Jam from 1.32, it always falls over trying to create a file or directory, normally mentioning Mkdir1 first. When trying to build the version of Jam that comes with the CVs source, it is able to build jam0.exe, but when it comes time to make bin.ntx86 it fails; and if that directory exists, the jam executable is not created; instead an error about "spawn: No such file or directory" is emittted. I am using vc 7.1. Any ideas for a better way to build the boost libraries?

2 1

Logging Library -- Formal Review Request
by John Torjo 22 May '05

22 May '05

Hi all, I've just updated the Boost Log Library: http://torjo.com/code/logging-v132.zip I would also like to ask for a _Formal Review_. The Boost Log Library is a small library, who: * makes it very easy to declare/define new logs * allows you very simple access to logs * allows for log hierarchies, and for modifying log hierarchies * allows for easy and efficient enabling/disabling of logs/log hierarchies * allows for easy manipulation of log behaviors (the log's destination(s) and/or adjusting the original message) * is thread-safe Using the library in code is easy and straightforward: int i = 1, j = 2, k = 3; BOOST_LOG(app) << "testing " << i << '-' << j << '-' << k << std::endl; BOOST_LOG(dbg) << "this is a debug message, i=" << i << std::endl; BOOST_LOG(info) << "I just wanted to tell you something...."; Additions to v1.3.2 - can be compiled as a static/dynamic runtime (works as a DLL as well) - removed dependency on boost_thread Note: I did not test this on Unix, but it should work. If anybody can take a look at detail/ts_posix.hpp, I'd appreciate it. - solved other small issues, based on feedback - slightly improved documentation -- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -v1.6.3 (Resource Splitter) -- http://www.torjo.com/cb/ - Click, Build, Run!

13 54

RE: [boost] Logging library - your own scenario!
by Spencer.Collyer＠barclayscapital.com 22 May '05

22 May '05

Hello John The situation we have here for logging is as follows: a) All logging goes via a Logger singleton. b) The output destination of the Logger is configurable at runtime. We currently have LogOutputters for file, console, and network. These LogOutputters are roughly equivalent to your appenders. c) All log messages belong to a particular topic. Topics are arranged hierarchically, which is important when considering log levels. d) All log messages also have a particular log level. These range from 'CRITICAL' all the way down to 'DEBUG4' (yes, we have four different levels of debug messages). Log levels and log topics are orthogonal to each other. e) A particular log topic can have a minimum log level specified, and any messages on that topic with levels below that level will not be logged. If a log topic does not have a level explicitly set, it inherits its level from its parent in the hierarchy, working its way up the tree until it finds a topic that has a level set. Hence, topic '/sm/message/builder' will inherit from '/sm/message', and if that has no level set then they both inherit from '/sm'. The root topic always has a level specified, even if it is the default of 'INFO'. Note that in our scheme it is impossible to turn off CRITICAL messages. f) We have a defined 'syslog' log level. All messages of that level and above are sent to the syslog, even if they are turned off for their topic. g) Log messages are sent to the LogOutputters in a structured format, with date/time, pid/tid, topic, level, and message all seperate. The LogOutputters determine how these values are formatted. h) We have the ability to adjust log levels by topic while a program is running. i) As a corollary to (h), and in contrast to what a lot of people have said, we do *not* turn off logging in our production code. However, note that all our programs are strictly 'in-house' so this is probably an unusual requirement. j) We do not do any kind of log rotation within the logging system itself. However, we do have external programs that rotate logs for us on a daily basis, and our file LogOutputter has the ability to insert a timestamp into a logfile name or append rather than overwrite on startup. Spencer ------------------------------------------------------------------------ For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. ------------------------------------------------------------------------

3 2

Re: [boost] Logging library - your own scenario!
by John Torjo 22 May '05

22 May '05

Dan, thanks for your thorough feedback! >> > > Here's what OpenWBEM does. > > > ------------------------------------------------------------------------ > > ----------------------------------------------------------------------------- > Definitions: > log > n. The end-point that log messages are sent to. Examples include a log file, syslog and the console. > v. The act of generating and outputting a message. e.g. The error message was logged. > Yup > logger > A C++ instance of a class derived from Logger, which is used by the OW code to output log messages. > Not sure why needed, I have appenders and modifiers. > component > A string identifying the logical grouping of code within OW that generated a log message. It is useful to organize components hierarchially, using a "." to separate ancestor and descendent. The hierarchy is meaningless to OW from a configuration or API point of view, but it is helpful for log processing. > The component "*" is reserved for configuration to mean all possible components. > Examples include "owcimomd", "owcimomd.http_server", "owcimomd.http_server.local_auth", "vintela.computer_system_provider". > I assume this is equivalent to "log names", in my lib. > category > Associated with a message to indicate attributes of the log message. > Also commonly refered to as log levels. > The category "*" is reserved for configuration to mean all possible categories. > Examples include Debug, Info, Warn, Error, FatalError, Trace, AuthenticationFailure, etc. > The 4 categories "Debug", "Info", "Error", "FatalError" are treated as levels for configuration purposes. If a log is configured for Debug, all 4 categories will be output. > Otherwise there is no relationship between categories. > Yes, I need to implement this ;) > message > The text of a message. A message has the following attributes: component, category, source filename, source line number, date/time, process id, thread id. > By default, I use a simpler approach (that is, the text is a string), but you can specify a custom log manager, and configure it to keep most if not all of the above. > message format > A pattern which indicates the format of the log message and associated attributes. In my case, "modifier" functions. > > ----------------------------------------------------------------------------- > Feature requirements & Use case list: > > - Ability to log all messages at or below a threshold (one of the 4 predefined categories) into a log. > Yup, need to implmement this. > - Ability to configure a log for each component. e.g. A specific provider's messages all go to a log. The log only contains the provider's messages. > Already exists. > - Set different thresholds for different components of the cimom. e.g. If I'm interested in debugging one specific component, I can turn on debug logging for that specific component (say my provider I'm working on) and not have to wade through tons of other unwanted debug messsages. Need to implement it. > > - Ability to configure a log for a specific category. e.g. The error messages from all components go to a log. Not sure I understand here. Could you give me an example? > > - Ability to configure a log with a "component"/"message category" combination. e.g. auditing of authentication: it would be nice to be able configure logging of all authentication failures and/or successes, and nothing else, to a certain log. > So far, you can configure per "component". For each "component", you'll be able to set a "message category" for which messages are logged. Messages below and with this category are logged, while messages above this category are ignored. Setting the "message category" to DISABLED will ignore all messages that are sent to this log. > - User-defined logfile formats. Use the same formatting rules as log4j > (or log4perl, like specified at > http://search.cpan.org/~mschilli/Log-Log4perl-0.48/lib/Log/Log4perl/Layout/…) > Available data includes: [date and time] [pid/thread-id] [category] [component] [log message] > You can do this with modifiers. In the future, I plan to create a small library on top of logging lib, which will make it very easy to define logfile formats, and configure logging. (I say in the future, because I don't think I'll have the time to finish it in time for the review) > - Ability to output to a log that can be processed by log4j compatible log > processing tools (e.g. Chainsaw) > Hmmm... Need to dig into this... > - Ability to configure the console logging when the cimom is run in debug mode > (with -d) What's cimom? I've looked on the web, is it "Common Information Model Object Manager (CIM OM)."? (did not have time to do some heavy searching though) > > ----------------------------------------------------------------------------- > On to the design: > > Each log message will have an associated component, category, source filename, source line number, date/time, process id, thread id. > > { "Debug", "Info", "Error", "FatalError" } are the set of predefined message categories. This set may be treated as levels, so that a message with a higher level category is also considered matching a lower level category (i.e. a FatalError is also categorized as a Debug level). Additional categories may be used, but they are independent of any other category. They are also the most commonly used, so the API will have convenience functions for them. > > A log is configured with a name, components, categories, format, type and any specific logger information such as a filename. If a component == "*", then it will match all components. If a category == "*", then it will match all message categories. > Yup, will do. > For owcimomd, there is a predefined log named "main". The owcimomd.log_level and owcimomd.log_location config items will be deprecated but still supported, and they will affect this log if set. > > For owcimomd, there is a predefined log named "debug". This log will be > enabled when owcimomd is run with a -d. The default will be all categories > and levels. > > When a message is sent to a logger, it will be evaluated against each log's configuration and if it matches, the message will be formatted according to the format configuration and output to the log. > Need to dig deeper, to see what you mean. > ----------------------------------------------------------------------------- > Configuration > [...] As said, I'd like to create a small lib on top of logging lib, to allow such easy configuration. Best, John -- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -v1.6.3 (Resource Splitter) -- http://www.torjo.com/cb/ - Click, Build, Run!

1 0