November 2005 - Boost-users

[Review] The review of the Boost.Logging library starts November 7th
by Hartmut Kaiser 10 Nov '05

10 Nov '05

Hi all, today starts the review of the Boost.Logging library written by John Torjo. It will end on November 16th. --------------------------------------------------- About the library: As applications are becoming more and more complex, logging is more and more of a must, in nowadays software. The Boost Logging Library is a library that: * makes it very easy to declare/define logs * allows you very simple access to logs * allows you to easily use/manipulate log levels (like, dbg/err/info/etc.) * allows for log hierarchies, and for manipulating log hierarchies * is thread-safe To get you started, here's some basic usage: BOOST_LOGL(app,dbg) << "debugging: " << i << '-' << j << std::endl; BOOST_LOG(app) << "I just wanted to tell you something...."; BOOST_LOGL(app,err) << "this is an error!"; The latest version of the lib can be found here: http://torjo.com/code/logging.zip --------------------------------------------------- Please always state in your review, whether you think the library should be accepted as a Boost library! Additionally please consider giving feedback on the following general topics: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Regards Hartmut Review Manager

1 0

Serialized as what?
by Merrill Cornish 10 Nov '05

10 Nov '05

What external file format does the Boost Serialization Library use? The introduction to the library states the requirement that serialization written by one machine must be readable by a different machine. And, elsewhere, it mentions that and XML intermediate file is on possibility; but I can't seem to find what the format being used is. Merrill

4 3

bidirectional file_descriptor
by Johannes Balle 10 Nov '05

10 Nov '05

Hello, I am currently trying to use the iostreams lib with standard BSD socket() file descriptors. If I understand correctly, I need a "bidirectional" stream buffer, so I tried overriding the mode like this: stream_buffer<file_descriptor, std::char_traits<file_descriptor::char_type>, std::allocator<file_descriptor::char_type>, boost::iostreams::bidirectional> But I cannot instantiate this because a static assertion fails. I assume this happens because the file_descriptor class is defined to be seekable (which a TCP socket is not), so what is the best way to do this? Thanks for your help ... Johannes Ballé Philips Applied Technologies Building SFJ 4.50 Glaslaan 2 5616 LW Eindhoven Tel: +31 40 2734194 E-mail: johannes.balle(a)philips.com

1 0

[program_options] how to use case_insensitive
by Lawry, Brian 10 Nov '05

10 Nov '05

I am using Boost 1.33.0 and MS Visual Studio .NET 2003 (13.10.3077) and having trouble developing a simple Win32 console application that accepts case-insensitive command-line options. -- output ---------------------------------- ..\>app -n 2 BOOST_PROGRAM_OPTIONS_VERSION=2 count set to 2 ..\>app -N 2 BOOST_PROGRAM_OPTIONS_VERSION=2 Exception caught: unknown option -N -------------------------------------------- -- code ------------------------------------ #include <boost/program_options.hpp> int _tmain(int argc, _TCHAR* argv[]) { using std::cout; using std::endl; namespace po = boost::program_options; namespace cls = boost::program_options::command_line_style; int count = 0; cout << "BOOST_PROGRAM_OPTIONS_VERSION=" << BOOST_PROGRAM_OPTIONS_VERSION << endl; try { po::options_description desc("Usage"); desc.add_options() ("help,h", "produce help message") ("count,n", po::value<int>(&count), "repeat count") ; po::variables_map vm; int cl_style = 0; cl_style |= cls::allow_short; cl_style |= cls::allow_dash_for_short; cl_style |= cls::short_allow_next; cl_style |= cls::case_insensitive; po::store(po::command_line_parser(argc, argv).options(desc).style(cl_style).run(), vm); po::notify(vm); if (vm.count("count")) cout << "count set to " << count << endl; else cout << "count not set" << endl; } catch( exception &e ) { cout << "Exception caught:\t" << e.what() << endl; } catch(...) { cout << "Unhandled exception caught!" << endl; } } -------------------------------------------- The line "cl_style |= cls::case_insensitive;" seems to have no effect. The other options in that section do seem to work as I can create other errors by omitting others. I tried for a minimal set of styles. Any ideas what I'm doing wrong? Thanks. Brian Lawry Mfg Software Engineer Compressor Controls Corp blawry<insert@here>cccglobal.com

3 2

Compilation problems on VC7 of code uses boost 1.31.0
by Miko Nahum 10 Nov '05

10 Nov '05

Hi I need your example in compilation errors on code uses boost under Windows VC7 and HP-UX 11.11 aCC 3.55 in 64 bit mode. We have the boost 1.31.0 successfully installed and used in our products, in SunOS using Forte 6.5.3 CC, HP 11.11 using aCC 3.33, Windows (W2k, XP) using VC6. While porting our code to 64 bit, we have upgraded the development env` to Forte 8.5.5 CC on Sun, aCC 3.55 on HP and VC7 on Windows. Compilation of boost itself had no problem. However, compilation of our products that using it has been failed on HP and Windows. 1. Problems on Windows: We have the following piece of code that uses boost (copy/paste): #include "boost/regex.h" #include "boost/regex.hpp" using namespace boost; using namespace std; typedef boost::reg_expression<char> re_type; typedef re_type::allocator_type allocator_type; long example_func(long pos, const std::string& regE, long& reslen, long max) { long res; boost::match_results <PData::iterator, allocator_type> m; allocator_type (a); re_type e (a); e.set_expression (regE, regbase::normal); if (regex_search (begin (), end (), m, e, match_not_dot_newline | match_not_dot_null)) <-- line 4790 { res = pos + m.position(); reslen = m.length(); return res; } . . . Compiling the above produce the following error: parser.cpp z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\perl_ma tcher_common.hpp(208) : error C2228: left of '.second' must have class/struct/union type type is 'const std::allocator<_Ty>::value_type' with [ _Ty=char ] z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\basic_r egex.hpp(243) : while compiling class-template member function 'bool boost::re_detail::perl_matcher<BidiIterator,Allocator,traits,Allocator2> ::find_imp(void)' with [ BidiIterator=PData::iterator, Allocator=allocator_type, traits=boost::regex_traits<char>, Allocator2=std::allocator<char> ] c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xlocmon(190) : while compiling class-template member function 'boost::re_detail::perl_matcher<BidiIterator,Allocator,traits,Allocator2 >::perl_matcher(BidiIterator,BidiIterator,boost::match_results<BidiItera tor,Allocator> &,const boost::reg_expression<charT> &,boost::regex_constants::match_flag_type)' with [ BidiIterator=PData::iterator, Allocator=allocator_type, traits=boost::regex_traits<char>, Allocator2=std::allocator<char>, charT=char ] z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\regex_s earch.hpp(38) : see reference to class template instantiation 'boost::re_detail::perl_matcher<BidiIterator,Allocator,traits,Allocator2 >' being compiled with [ BidiIterator=PData::iterator, Allocator=allocator_type, traits=boost::regex_traits<char>, Allocator2=std::allocator<char> ] z:\med2\dev\ParserLib\parser.cpp(4790) : see reference to function template instantiation 'bool boost::regex_search<PData::iterator,allocator_type,char,boost::regex_tra its<charT>,std::allocator<_Ty>>(BidiIterator,BidiIterator,boost::match_r esults<BidiIterator,Allocator> &,const boost::reg_expression<charT> &,boost::regex_constants::match_flag_type)' being compiled with [ charT=char, _Ty=char, BidiIterator=PData::iterator, Allocator=allocator_type ] "z:\med2\dev\ParserLib\parser.cpp(4790)" is marked above with red. "z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\regex_ search.hpp(38)" is listed below: template <class BidiIterator, class Allocator, class charT, class traits, class Allocator2> bool regex_search(BidiIterator first, BidiIterator last, match_results<BidiIterator, Allocator>& m, const reg_expression<charT, traits, Allocator2>& e, match_flag_type flags = match_default) { if(e.flags() & regex_constants::failbit) return false; re_detail::perl_matcher<BidiIterator, Allocator, traits, Allocator2> matcher(first, last, m, e, flags); <-- line 38 return matcher.find(); } "z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\perl_m atcher_common.hpp(208)" is part of the following function: template <class BidiIterator, class Allocator, class traits, class Allocator2> bool perl_matcher<BidiIterator, Allocator, traits, Allocator2>::find_imp() and the line (208) is listed below: // start again: search_base = position = m_result[0].second; <-- line 208 // If last match was null and match_not_null was not set then increment // our start position, otherwise we go into an infinite loop: Searching Google for this problem did not help very much, so I was wondering if you have encounter it and put more light on it and the solution? 2. Problems on HP: 2.1. Error 24: "/VOBS/netrac2_3rd_party/boost/delivery/include/boost/regex/v4/regbase.h pp", line 53 # '<identifier>' expected instead of 'collate'. perlex = collate << 1, // perl extensions ^^^^^^^ Error 164: "/VOBS/netrac2_3rd_party/boost/delivery/include/boost/regex/v4/regbase.h pp", line 53 # Integral type expected for operator '<<'; types found were '<no type>' and 'int'. perlex = collate << 1, // perl extensions ^^^^ We do not understand why the error occurs, can you help with that? from some reason, HP's aCC doesn't like the "collate". Again, same as with problem #1, google it did not produce any useful information. We have workaround this problem as follow: changed: collate = icase << 1, // use locale specific collation perlex = collate << 1, // perl extensions to: collate = icase << 1, // use locale specific collation _collate = icase << 1, perlex = _collate << 1, // perl extensions What do you think about this solution? 2.2. Fixing above problem have exposed a problem similar to the Windows problem. Btw, both problems #1 and #2.2 were solved when set #define BOOST_NO_STD_ALLOCATOR Regards, Miko Nahum

1 0

MSVC Afx Libs incompatibility ?
by joel 10 Nov '05

10 Nov '05

I have just "demo_xml" serialisation test with "StdAfx.h" precompilated header. VC7.1 reply : nafxcwd.lib(afxmem.obj) : error LNK2005: "void * __cdecl operator new(unsigned int)" (??2@YAPAXI@Z) déjà défini(e) dans libcpmtd.lib(newop.obj) It seems that boost libs is defining new operator as nafxcwd.lib from microsoft. Does anyone succeed to use boost libs with "stdafx" libs ? Joel.

4 3

Re: [Boost-users] boost::python and Python 2.4
by Nat Goodspeed 09 Nov '05

09 Nov '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Noel Yap > Sent: Monday, November 07, 2005 6:34 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] boost::python and Python 2.4 > > What did you have to do to get it to work with Python 2.4? Is all > that's necessary to modify all references to python2.2 to python2.4? [Nat] ? Not sure what references you mean. I just changed the environment variable we use for the Python base directory from c:\Python23 to c:\Python24, thus pointing to all new header files and libraries, and ta daa!

3 2

boost::python and Python 2.4
by Noel Yap 09 Nov '05

09 Nov '05

Is there any work being done to get boost::python to work with Python 2.4? Does anyone see any reasons it won't work (assuming the build is able to work)? Thanks, Noel

3 2

boost1.33.0 on IA64 thread problem
by Andreas Unterkircher 09 Nov '05

09 Nov '05

I'm working on porting a large project to IA64. Therefore I'd like to use the boost thread package on IA64 using gcc 3.2.3 (standard compiler on the SL 3 Linux distribution). There are some problems which I describe below and at the end of the mail I pose my questions. Thanks for any comments ! To test I use the following code: #include <stdlib.h> #include <boost/thread/mutex.hpp> int main() { boost::mutex mut; return 0; } I downloaded boost 1.33.0 & build & install it. When I try to compile it with g++ -g -O2 -pthread -I/opt/boostTest/include/boost-1_33 -L/opt/boostTest/lib -lboost_filesystem-gcc-mt -lboost_thread-gcc-mt -lpthread -lboost_regex-gcc-mt prog.c I get In file included from /opt/boostTest/include/boost-1_33/boost/thread/detail/config.hpp:18, from /opt/boostTest/include/boost-1_33/boost/thread/mutex.hpp:15, from prog.c:2: /opt/boostTest/include/boost-1_33/boost/config/requires_threads.hpp:47:5: #error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)" [many more "not declared" messages] Now I use "-DBOOST_HAS_THREADS", but this also does not help : g++ -g -O2 -pthread -DBOOST_HAS_THREADS -I/op/boostTest/include/boost-1_33 -L/opt/boostTest/lib -lboost_filesystem-gcc-mt -lboost_thread-gcc-mt -lpthread -lboost_regex-gcc-mt prog.c /usr/bin/ld: cannot find -lboost_thread-gcc-mt collect2: ld returned 1 exit status In the boost mailing list archive I found an IA64 patch posted by Ben Hutchings. Applying this patch and recompiling boost I get: g++ -g -O2 -pthread -I/opt/boostTest/include/boost-1_33 -L/opt/boostTest/lib -lboost_filesystem-gcc-mt -lboost_thread-gcc-mt -lpthread -lboost_regex-gcc-mt prog.c In file included from /opt/boostTest/include/boost-1_33/boost/thread/detail/config.hpp:18, from /opt/boostTest/include/boost-1_33/boost/thread/mutex.hpp:15, from prog.c:2: /opt/boostTest/include/boost-1_33/boost/config/requires_threads.hpp:47:5: #error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)" But when I use "-DBOOST_HAS_THREADS" everything works fine: g++ -g -O2 -pthread -DBOOST_HAS_THREADS -I/op/boostTest/include/boost-1_33 -L/opt/boostTest/lib -lboost_filesystem-gcc-mt -lboost_thread-gcc-mt -lpthread -lboost_regex-gcc-mt prog.c Here are my questions: Boost 1.33.0 contains the file boost/detail/sp_counted_base_gcc_ia64.hpp, nevertheless thread support seems not to work with gcc3.2.3. Thread support works by applying the patch and using "-DBOOST_HAS_THREADS". What is the status of boost 1.33.0 concerning IA64 ? I guess the patch has not been incorporated into the boost distribution ? On IA32 I can compile and use boost 1.33.0 threads using gcc3.2.3 without using "-DBOOST_HAS_THREADS". Why is this the case ? Ideally I would like to use the same compiler flags to compile a project using boost on IA32 and IA64. For some reasons I'd prefer to use boost 1.32.0 on IA64 but I could not get the thread package to work. Does boost 1.32.0 threads work on IA64/gcc3.2.3 ? Or is it only with boost 1.33.0 + patch that I can use them on IA64 ? Best regards, Andreas

2 3

Boost 1.33.1 Beta released
by Douglas Gregor 09 Nov '05

09 Nov '05

Boost 1.33.1 Beta ----------------- Boost 1.33.1 Beta is now available at http://www.boost.org. This is a bug fix release to 1.33.0, containing updates to existing libraries and additional computer support. Updated Libraries * Any Library: Cast to reference types introduced in 1.33.0 is now documented on any_cast documentation page. * Config Library: Don't undef BOOST_LIB_TOOLSET after use. * Boost.Python: o The build now assumes Python 2.4 by default, rather than 2.2 o Support Python that's built without Unicode support o Support for wrapping classes with overloaded address-of (&) operators * Smart Pointer Library: Fixed problems under Metrowerks CodeWarrior on PowerPC (Mac OS X) with inlining on, GNU GCC on PowerPC 64. * Regex Library: Fixed the supplied makefiles, and other small compiler specific changes. Refer to the regex history page for more information on these and other small changes. * Iostreams Library: Improved the interface for accessing a chain's components, added is_open members to the file and file descriptor devices, fixed memory-mapped files on Windows, and made minor changes to the documentation. * Functional/Hash Library: Fixed the points example. * Multi-index Containers Library: Fixed a problem with multithreaded code, and other minor changes. Refer to the library release notes for further details. * Graph Library: Fixed a problem with the relaxed heap on x86 Linux. Fixed problems with cuthill_mckee_ordering and king_ordering producing no results. * Signals Library: Fixed problems with the use of Signals across shared library boundaries. * Thread library: read_write_mutex has been removed due to problems with deadlocks. Supported Compilers Boost is tested on a wide range of compilers and platforms. Since Boost libraries rely on modern C++ features not available in all compilers, not all Boost libraries will work with every compiler. The following compilers and platforms have been extensively tested with Boost, although many other compilers and platforms will work as well. For more information, see the regression test results. New for this release: Support for building with the newest STLport-5.0 was added. The support includes building with MinGW Runtime 3.8 plus STLport-5.0 improved to support wide character operations. Apple GCC 4.0, HP Tru64 C++, and Microsoft Visual C++ 8.0 are supported platforms. We have added an experimental autoconf-like configure script for Unix-like systems: run configure --help for more information. * Apple GCC 3.3, 4.0 on Mac OS X. * Borland C++ 5.6.4 on Windows. * GNU C++ 2.95.3 (with and without STLport), 3.2.x., 3.3.x, 3.4.x, 4.0.x on Windows, Linux and Solaris. * HP C++ for Tru64 UNIX 7.1. * Intel C++ 8.1, 9.0 on Windows, Linux. * Metrowerks CodeWarrior 8.3, 9.4, 9.5 on Mac OS X and Windows. * Microsoft Visual C++ 6.0 (sp5, with and without STLport), 7.0, 7.1, 8.0. Note: Boost does not support the non-standard "Safe" C++ Library shipping with Visual C++ 8.0, which may result in many spurious warnings from Boost headers and other standards- conforming C++ code. To suppress these warnings, define the macro _SCL_SECURE_NO_DEPRECATE. Acknowledgements Douglas Gregor managed this release. A great number of people contributed their time and expertise to make this release possible. Special thanks go to Aleksey Gurtovoy and Misha Bergal, who managed to keep the regression testing system working throughout the release process; David Abrahams, Beman Dawes, Aleksey Gurtovoy, Bronek Kozicki, Rene Rivera and Jonathan Turkanis for greatly improving the quality of this release; Rene Rivera for the new Boost web page design; and Zoltan "cad" Juhasz for the new Boost logo.

1 0