- Boost - lists.boost.org

Re: [boost] C++ Builder 2009 and Boost compliance
by Peter Dimov 16 Sep '08

16 Sep '08

siliconman: > In article <00c101c91801$b08eeb00$6507a80a@pdimov2>, > "Peter Dimov" <pdimov(a)pdimov.com> wrote: > >> Do you have an idea why your 5.6.4 and 5.8.2 tests fail (apparently at >> random) with errors like: >> >> Fatal: Unable to open file 'turboc.$ln' > > It seems that the compiler creates these temporary files and if two > instances of the compiler are working at the same time (I'm currently > testing on a quad core machine) in the same directory that those > versions of the compiler isn't able to handle this situation. I'm > actually retooling my build systems, so I was going to pass this task > back to a single core machine even thought that would mean longer turn > around time. > Alternatively, I could have two machines running tests and have > siliconman-legacy with 5.64 and 5.82 on the single core machine and > siliconman with 5.9.3 and 6.10 with the faster machine. A quick temporary fix - until one of your permanent measures are put in place - might be to just disable one of 5.64 and 5.82; that way we'll at least have one set of reliable results instead of two that are unfortunately of little use in their present state.

1 0

Re: [boost] Answers re BENUM library for automated enum streaming
by Tony D 16 Sep '08

16 Sep '08

From: David Abrahams <dave(a)boostpro.com> > [I/Tony wrote]: > > BENUM(X, A = 1, B, C = 22, D = B|N); > > This interface requires variadic (C99) preprocessor support, does it not? Quite so David. So, limited portability - unless your preprocessor library has some relevant workarounds? Cheers, Tony

3 3

Re: [boost] Answers re BENUM library for automated enum streaming
by Tony D 16 Sep '08

16 Sep '08

> From Manuel Fiorelli: > You could try to look at [boost preprocessor lib docs] to avoid variadic macros. > I am not sure if it is applicable at your library, though. As best I understand it, they're not applicable :-(. Perhaps David will confirm. Also appreciate if someone can fill me in on boost's (historical?) attitude to facilities with this dependency. FWIW, http://en.wikipedia.org/wiki/Variadic_macro lists compilers with __VA_ARGS__ support (GCC 3.0+, VC++2005+, C++Builder 2006+). > From: Marcus Lindblom <macke(a)yar.nu> > However, is it possible to define a separate mapping if one would like? > > For instance, I like my strings to be lower case, and without prefixes, > whereas my enums need a bit more scaffolding: > > enum Context { CXT_APP, CXT_PHYS, CXT_VIS } > enum Aspect { ASP_APP, ASP_PHYS} > CXT_APP = "app", CXT_PHYS = "phys", etc. > ASP_APP = "app", ASP_PHYS = "phys", etc. Hi Marcus, There are several points of customisation that do or might allow it. For example, derive an "Info_Container" (into which identifier/value pairs are inserted via registration callback) with your callback performing simple automated substitutions like removal of text up to and including an underscore and conversion to lower case. At worst - not recommended as it requires manual maintainence - you can resort to ignoring the automated registration and hardcode one-by-one insertions using arbitrary identifiers, or even create a completely customer Info_Container class hardcoding support for a specific enum. The main BENUM macro also allows specification of extra functions to include in the generated class (a set of such precanned "features" are provided in benum_features.h). I haven't tried it, but I suspect a static method could be introduced to perform a transformation, but it would need to be called before first use. > > - smart enums requires user-maintained "meta-data" - from the smart enum docs: > > bool init = (::EnumIO<Foo>::the() (Bar, "bar") (Baz, "baz")), true; > > EnumIO only does that, and it hides the usage of EnumIO<> from the > header file, thus it is very lean and efficient. > How much extra template code is instantiated in each source file > including BENUM-use? Not so much: - only a thin wrapper is instantiated for each type, performing type casting as it interacts with a single instance of the core storage/lookup code that works with int enumeration values - there's a preprocessor #ifdef to control whether one of the implementation files is sucked into the related header for convenience vs out-of-line for decoupling physical dependency / faster compiles Regards, Tony

1 0

Re: [boost] C++ Builder 2009 and Boost compliance
by Peter Dimov 16 Sep '08

16 Sep '08

siliconman: > In article <48CE15DC.6010301(a)tid.es>, joaquin(a)tid.es wrote: > >> It'd be nice if we could have a regression test runner for this >> product. > > I'll be adding it to my test runs soon. > -- > -David David, Do you have an idea why your 5.6.4 and 5.8.2 tests fail (apparently at random) with errors like: Fatal: Unable to open file 'turboc.$ln' Error: Could not delete C:\Boost\results\boost\bin.v2\libs\smart_ptr\test\sp_accept_owner_test.test\borland-5.6.4\debug\sp_accept_owner_test.tds (project already open in IDE?) ====== BEGIN OUTPUT ====== '"C:\Boost\results\boost\bin.v2\libs\smart_ptr\test\sp_atomic_test.test\borland-5.6.4\debug\sp_atomic_test.exe"' is not recognized as an internal or external command, operable program or batch file. EXIT STATUS: 9009 ====== END OUTPUT ====== I'd like to monitor these test results, but their unreliability makes it impossible.

1 0

Symbol not found for OS X
by Michel Valstar 16 Sep '08

16 Sep '08

Hello, I'm trying to build a project that was developed for Ubuntu on a Mac OS X 10.5. Building goes well for a long while, but then I get the following error: boost::python::converter::arg_to_python<unsigned char>::arg_to_python(unsigned char const&)in trackerbasewrapper.os "_PyObject_IsTrue", referenced from: boost::python::api::object_operators<boost::python::api::object>::operator _object* (boost::python::api::object::*)() const() constin trackerbasewrapper.os "_PyExc_KeyError", referenced from: _PyExc_KeyError$non_lazy_ptr in trackerbasewrapper.os "_PyObject_IsInstance", referenced from: boost::python::enum_<FeatureUsage>::convertible_from_python(_object*) in trackerbasewrapper.os "_PyExc_UserWarning", referenced from: _PyExc_UserWarning$non_lazy_ptr in trackerbasewrapper.os "_PyBool_FromLong", referenced from: boost::python::to_python_value<bool const&>::operator()(bool const&) constin trackerbasewrapper.os ld: symbol(s) not found collect2: ld returned 1 exit status scons: *** [trackerbase/libtrackerbasewrapper.dylib] Error 1 scons: building terminated because of errors. Is this a symbol that still needs to be added for the Max OS X codebase? Thanks, Michel -- Dr. Michel Valstar, Research Associate http://www.doc.ic.ac.uk/~mvalstar Department of Computing Imperial College London 180 Queens' Gate London SW7 2AZ, U.K. tel.: +44 20 7594 8234 fax: +44 20 7581 8024

1 0

[EnableIf?] Seeking an example....
by Robert Jones 16 Sep '08

16 Sep '08

Somewhere in the Boost headers, or maybe the Boost documentation I have seen a bit of code which uses SFINAE, and also possibly the enable_if header to select either a find class method or find global template depending on what's available. It might have been written by Eric. I can't find it now,maybe it's not there any more, but if anyone can point me to it I'd really appreciate it! Thanks in advance, - Rob.

1 0

Re: [boost] C++ Builder 2009 and Boost compliance
by Sean Farrow 16 Sep '08

16 Sep '08

Hi: There appears to be an issue with the spirit library and c++ builder. How are boost libraries built, as I want to determine what specifically is causing these issues. I use both boost.spirit and boost.serialization. Cheers Sean. -----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of siliconman Sent: 16 September 2008 01:24 To: boost(a)lists.boost.org Subject: Re: [boost] C++ Builder 2009 and Boost compliance In article <48CE15DC.6010301(a)tid.es>, joaquin(a)tid.es wrote: > It'd be nice if we could have a regression test runner for this > product. I'll be adding it to my test runs soon. -- -David _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost __________ Information from ESET NOD32 Antivirus, version of virus signature database 3444 (20080916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3445 (20080916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3445 (20080916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

1 0

[Config] Multiple versions of Boost
by Sohail Somani 16 Sep '08

16 Sep '08

Recently, I had the pleasure of integrating a statically linked library that used a version of Boost different from the one I was using. All relevant compiler flags matched. Only the Boost version was the problem. Fortunately, I was able to solve the problem by getting the provider of the statically linked library to rename the Boost namespace by passing in -Dboost=boost_133_1_provider to their compiler. This worked fine for them. Obviously part of this solution involved them rebuilding the part of boost that was important to them in the same manner, but we always build Boost ourselves don't we? Anyway, I thought it might be a good idea to do the same on the larger code base so I attempted to do the same. Failed miserably. The problem is that some of the Boost code contains some variant of: #if defined(SOME_CONDITION) # define HEADER <boost/some/header.hpp> #else # define HEADER <boost/some/other/header.hpp> #endif #include HEADER Reading 16.2/4, it seems that the behaviour in this case is not defined. Specifically, an implementation may or may not replace the boost text with boost_133_1_provider. This is true whether or not you have <boost/some/header.hpp> or "boost/some/header.hpp". So on one compiler, you may end up with: #include <boost_133_1_provider/some/header.hpp> And on another: #include <boost/some/header.hpp> My immediate problem solved, I made do. However, the problem still bugs me. There should be /some/ way to do this. So... What if Boost.Config did something like: #if !defined(BOOST) # define BOOST boost #endif And we replace all uses of the boost namespace with BOOST? Would such a patch against trunk be acceptable? What are the problems? I know it isn't aesthetically pleasing but it might have made this a bit easier. -- Sohail Somani http://uint32t.blogspot.com

8 25

Answers re BENUM library for automated enum streaming
by Tony D 16 Sep '08

16 Sep '08

Hi all, Markus: apologies for not including the full URL. The file is benum_v1.zip at http://www.boostpro.com/vault/ Full URL is hhttp://www.boostpro.com/vault/index.php?action=downloadfile&filename=benum… - note Google Chrome mistakes it for a query, but the vault CGI doesn't seem to cope with %3D/%26 encoding of = and &. Thorsten / Marcus: roughly comparing to smart enum proposal: - BENUM _automates_ conversions based on stringified source code, which (postulating an extra macro "BENUM" hard-coding your favourite selection of meta-data container and optional features) allows BENUM(X, A = 1, B, C = 22, D = B|N); to approximate enum X { A = 1, B, C = 22, D = B|N }; and needs no further code to be streamable etc (preprocessor macros allow run-time cross-referencing of stringified source code with array of actual values) - smart enums requires user-maintained "meta-data" - from the smart enum docs: bool init = (::EnumIO<Foo>::the() (Bar, "bar") (Baz, "baz")), true; - BENUM supports optional mark-up mixed in with the enumerations to capture use of bit masking, guiding conversion to/from pipe-separated identifiers - BENUM supports many optional "features" including bitwise operations, incrementing and arithmetic operations, while smart-enums supports arithmetic and increment - both provide iteration over enumerations - smart enums supports automated range checking, with handling via throw, wrap, modulo The benum.test.cpp file shows a very complex example usage highlighting the features. Sorry for not working in to it gently. Note that all that extra mark-up etc. is optional and not needed by simple enumerations without bit masking/ORing etc.. Regards, Tony

3 2

Old style casts and Boost style guidelines
by Jon Biggar 16 Sep '08

16 Sep '08

I wanted to get rid of all old-style casts in my application, so I turned on -Wold-style-cast in gcc and found a whole bunch of old-style casts in boost headers. It seems to me that the boost coding style guidelines ought to explicitly discourage old-style casts. Any one else have a point of view? I've attached a list of the old-style casts gcc found in the 1.36 headers. This list isn't exhaustive, since my app doesn't use all boost libraries. :) -- Jon Biggar jon(a)floorboard.com jon(a)biggar.org jonbiggar(a)gmail.com ../../../boost/asio/detail/posix_fd_set_adapter.hpp:41: warning: use of old-style cast ../../../boost/asio/detail/posix_fd_set_adapter.hpp:45: warning: use of old-style cast ../../../boost/asio/detail/posix_fd_set_adapter.hpp:53: warning: use of old-style cast ../../../boost/asio/detail/signal_init.hpp:41: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:117: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:163: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:423: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:469: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:470: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:471: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:558: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:560: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:581: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:583: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:772: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:78: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:81: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:858: warning: use of old-style cast ../../../boost/asio/detail/socket_select_interrupter.hpp:61: warning: use of old-style cast ../../../boost/asio/detail/socket_select_interrupter.hpp:68: warning: use of old-style cast ../../../boost/asio/detail/socket_select_interrupter.hpp:90: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:153: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:159: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:165: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:171: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:213: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:219: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:225: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:189: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:207: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:215: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:222: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:229: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:236: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:243: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:250: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:257: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:264: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:271: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:278: warning: use of old-style cast ../../../boost/asio/ip/basic_endpoint.hpp:71: warning: use of old-style cast ../../../boost/asio/ip/basic_endpoint.hpp:99: warning: use of old-style cast ../../../boost/asio/ip/detail/socket_option.hpp:275: warning: use of old-style cast ../../../boost/asio/ip/detail/socket_option.hpp:284: warning: use of old-style cast ../../../boost/asio/ip/detail/socket_option.hpp:353: warning: use of old-style cast ../../../boost/asio/is_read_buffered.hpp:54: warning: use of old-style cast ../../../boost/asio/is_write_buffered.hpp:54: warning: use of old-style cast ../../../boost/concept_check.hpp:915: warning: use of old-style cast ../../../boost/concept_check.hpp:928: warning: use of old-style cast ../../../boost/concept/detail/general.hpp:29: warning: use of old-style cast ../../../boost/concept/detail/general.hpp:37: warning: use of old-style cast ../../../boost/concept/detail/has_constraints.hpp:40: warning: use of old-style cast ../../../boost/concept/usage.hpp:21: warning: use of old-style cast ../../../boost/detail/lcast_precision.hpp:176: warning: use of old-style cast ../../../boost/detail/lcast_precision.hpp:177: warning: use of old-style cast ../../../boost/detail/sp_convertible.hpp:48: warning: use of old-style cast ../../../boost/exception/enable_error_info.hpp:85: warning: use of old-style cast ../../../boost/functional/detail/hash_float.hpp:180: warning: use of old-style cast ../../../boost/functional/detail/hash_float.hpp:182: warning: use of old-style cast ../../../boost/functional/hash/hash.hpp:112: warning: use of old-style cast ../../../boost/functional/hash/hash.hpp:114: warning: use of old-style cast ../../../boost/functional/hash/hash.hpp:132: warning: use of old-style cast ../../../boost/functional/hash/hash.hpp:134: warning: use of old-style cast ../../../boost/function/function_base.hpp:300: warning: use of old-style cast ../../../boost/function/function_base.hpp:347: warning: use of old-style cast ../../../boost/function/function_base.hpp:434: warning: use of old-style cast ../../../boost/function/function_base.hpp:619: warning: use of old-style cast ../../../boost/function/function_template.hpp:342: warning: use of old-style cast ../../../boost/function/function_template.hpp:435: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:145: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:151: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:152: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:153: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:155: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:166: warning: use of old-style cast ../../../boost/lexical_cast.hpp:578: warning: use of old-style cast ../../../boost/lexical_cast.hpp:694: warning: use of old-style cast ../../../boost/lexical_cast.hpp:764: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:117: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:27: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:45: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:63: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:81: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:99: warning: use of old-style cast ../../../boost/none.hpp:23: warning: use of old-style cast ../../../boost/regex/v4/cpp_regex_traits.hpp:284: warning: use of old-style cast ../../../boost/regex/v4/cpp_regex_traits.hpp:294: warning: use of old-style cast ../../../boost/regex/v4/cpp_regex_traits.hpp:653: warning: use of old-style cast ../../../boost/regex/v4/cpp_regex_traits.hpp:663: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:106: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:115: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:128: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:369: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:370: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:94: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_common.hpp:787: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_common.hpp:831: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_common.hpp:866: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher.hpp:50: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher.hpp:54: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:432: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:433: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:476: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:477: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:665: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:671: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:733: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:739: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:802: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:808: warning: use of old-style cast ../../../boost/regex/v4/regex_split.hpp:124: warning: use of old-style cast ../../../boost/regex/v4/regex_token_iterator.hpp:112: warning: use of old-style cast ../../../boost/regex/v4/regex_token_iterator.hpp:141: warning: use of old-style cast ../../../boost/regex/v4/sub_match.hpp:69: warning: use of old-style cast ../../../boost/regex/v4/sub_match.hpp:75: warning: use of old-style cast ../../../boost/thread/locks.hpp:1259: warning: use of old-style cast ../../../boost/thread/locks.hpp:1293: warning: use of old-style cast ../../../boost/thread/locks.hpp:1299: warning: use of old-style cast ../../../boost/thread/locks.hpp:1305: warning: use of old-style cast ../../../boost/thread/locks.hpp:43: warning: use of old-style cast ../../../boost/thread/locks.hpp:59: warning: use of old-style cast ../../../boost/thread/locks.hpp:75: warning: use of old-style cast ../../../boost/thread/pthread/timespec.hpp:28: warning: use of old-style cast ../../../boost/thread/thread_time.hpp:34: warning: use of old-style cast ../../../boost/thread/xtime.hpp:83: warning: use of old-style cast

8 13