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

structure alignment
by Christoph Macheiner 12 May '09

12 May '09

(Long-time reader, first-time poster) Hi all Recently I wanted to upgrade from 1.33 and got build errors in boost format. It is a quite large codebase which, for legacy reasons, has to be built with 1-byte structure alignment (this cannot easily be changed). The error comes from an boost::optional<boost::io::detail::locale_t> in boost/format/internal.hpp that wants to be 4-byte aligned (platform is Win32 vc9). Now I cannot just include this (or all) boost headers with 4- (or 8-)byte alignment because they include other std headers which have already been included before (with 1-byte alignment). Is there an easy solution to this that I am missing despite changing all includes? Is there information on such interdependencies somewhere? Or do I have to bite the bullet and include all standard headers with a suitable alignment. I am sorry if this has been discussed before, but I could not find anything. Thanks, Christoph.

1 0

[trac] version 1.39.0 in trac
by Michael Caisse 12 May '09

12 May '09

Version: Boost 1.39.0 needs to be added in trac for tickets. Thank you - Michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

3 2

Bounded String
by vicente.botet 12 May '09

12 May '09

Hi, I was looking for a bounded capacity string and I have take a look to the review (2006) of the rejected FixedString library (http://www.boostpro.com/vault/index.php?action=downloadfile&filename=fixed_…) Here follows a brief compilation of the main points * A motivating use case was missing * the motivating example (printf) was not enough significant, when we have the choice we can always find a better class. * The design was not adapted to the goals * the inheritance hierarchy was considered to complicated needing an allocation * buffer overrun should be configurable - truncate, exception, assert, * The formating should be considered orthogonal to the fixed_string class The context where I need to use something like this class is: * the binary layout can not be modified and must be bounded due to legacy issues, Third Party Products interfaces, protocol messages format or bounded capacity strings on persistent databases. * overrun must be checked because otherwise the program can crash. I will propose to name it bounded_c_string (when _c_ stands for "C-style" but recalls also capacity) These are the requirements I would associate to such a class * the value must always be a C-string (so with a trailing '\0') * The layout of a bounded_c_string<N> class must be the same as its counterpart C-string char[N] (sizeof(bounded_c_string<N>==N) * As a lot of code can use this type the refactoring from C code using char[N] to bounded_c_string<N> should be reduced to the type declaration (overloading of all the C string functions with bounded_c_string<N> are a must) * the efficiency must be equivalent to the hand written C-style * convertible to and from C-strings, std::string and other bounded_c_string<M> * C++ std::string like interface must also be provided Note that there is not issues with the length of the string coherency because not stored. This class do not intends to use dynamic memory when fixed capacity is not enough (see AutoBuffer library http://www.cs.aau.dk/~nesotto/boost/auto_buffer.zip for this use case) I don't know which is the FixedString library, the last upload on the Vault dates from 08.01.2006. Is there an interest for this simple class? Do you agree with the requirements? Is there an interest for a bounded_c_memory class which will take care of the length of the significant data instead of the trailing '\0'? Best regards, _____________________ Vicente Juan Botet Escribá

2 1

[GIL.IO] Looking for a review manager
by Christian Henning 12 May '09

12 May '09

Hi there, I'm looking for a review manager for the new GIL.IO extension. Anyone around here who would like to volunteer? Regards, Christian

1 0

Requesting interest in a bounded capacity C-string
by vicente.botet 12 May '09

12 May '09

Hi, I was looking for a bounded capacity string and I have take a look to the review (2006) of the rejected FixedString library (http://www.boostpro.com/vault/index.php?action=downloadfile&filename=fixed_…) Here follows a brief compilation of the main points * A motivating use case was missing * the motivating example (printf) was not enough significant, when we have the choice we can always find a better class. * The design was not adapted to the goals * the inheritance hierarchy was considered to complicated needing an allocation * buffer overrun should be configurable - truncate, exception, assert, * The formating should be considered orthogonal to the fixed_string class The context where I need to use something like this class is: * the binary layout can not be modified and must be bounded due to legacy issues, Third Party Products interfaces, protocol messages format or bounded capacity strings on persistent databases. * overrun must be checked because otherwise the program can crash. I will propose to name it bounded_c_string (when _c_ stands for "C-style" but recalls also capacity) These are the requirements I would associate to such a class * the value must always be a C-string (so with a trailing '\0') * The layout of a bounded_c_string<N> class must be the same as its counterpart C-string char[N] (sizeof(bounded_c_string<N>==N) * As a lot of code can use this type the refactoring from C code using char[N] to bounded_c_string<N> should be reduced to the type declaration (overloading of all the C string functions with bounded_c_string<N> are a must) * the efficiency must be equivalent to the hand written C-style * convertible to and from C-strings, std::string and other bounded_c_string<M> * C++ std::string like interface must also be provided Note that there is not issues with the length of the string coherency because not stored. This class do not intends to use dynamic memory when fixed capacity is not enough (see AutoBuffer library http://www.cs.aau.dk/~nesotto/boost/auto_buffer.zip for this use case) I don't know which is the FixedString library, the last upload on the Vault dates from 08.01.2006. Is there an interest for this simple class? Do you agree with the requirements? Is there an interest for a bounded_c_memory class which will take care of the length of the significant data instead of the trailing '\0'? Best regards, _____________________ Vicente Juan Botet Escribá

1 0

[filesystem] copy_file() not atomic proposed fix
by Beman Dawes 12 May '09

12 May '09

Ticket #2925 complains that "boost::filesystem cannot atomically copy file if target exists", and gives this example: void copy (std::string src, std::string target, int flags) { if ( (flags & Overwrite) && boost::fs::exists (tgt) ) { boost::fs::remove (tgt); } // second process can create file again here boost::fs::copy_file (src, tgt); } Changing boost::filesystem::copy_file() to overwrite isn't viable; (1) that just creates a mirror of the race condition when an overwrite is actually desired to be an error, and (2) changing the behavior would silently break existing code. The proposed solution is to add an option to copy_file(): enum class copy_option { fail_if_exists, overwrite_if_exists }; void copy_file( const Path & from_path, const Path & to_path, copy_option option=copy_option::fail_if_exists ); The implementation would be atomic on both POSIX and Windows. Comments? --Beman

1 0

Anybody tried AMD x86 Open64 Compiler Suite?
by Hartmut Kaiser 11 May '09

11 May '09

Here: http://developer.amd.com/CPU/OPEN64/Pages/default.aspx Regards Hartmut

4 3

[iostream] Device::read return inconsistency
by Richard Smith 11 May '09

11 May '09

The example in the documentation for the Source concept in Boost.Iostreams says: std::streamsize read(char* s, std::streamsize n) { // Read up to n characters from the input // sequence into the buffer s, returning // the number of characters read, or -1 // to indicate end-of-sequence. } (The same text appears in 'valid expressions / semantics' table, which is probably more definitive.) What does a return of less than n actually mean? Nowhere on the documentation pages for the Source concept or the read function template does it say what a return value in the range [0,n) means. And from the comment in the example, it would appear that read is permitted to return less than n if the some smaller number of characters are currently available /without/ implying that a subsequent call will hit eof. This seems to be confirmed by the use of non_blocking_adapter in places in the library where you want code to block until the n bytes are available, and to guarantee eof (or, I guess, an error) for a subsequent call. However, the comment in the BidirectionalDevice seems to disagree: std::streamsize read(char* s, std::streamsize n) { // Reads up to n characters from the input // sequence into the buffer s, returning the number // of characters read. Returning a value less than n // indicates end-of-sequence. } (Again, the same text appears in the 'valid expressions / semantics' table.) So which is it? I don't believe it is the library's intention for a [0,n) return to have different meanings in BidirectionalDevice and Source. I haven't located any code in the library itself that assumes a non-zero return of less than n signifies eof (though I haven't searched all that hard), but third-party code and/or any other boost libraries that use Boost.Iostreams may well do. However there do seem to be places where a return of zero is taken to mean eof. For example, indirect_streambuf::underflow seems to treat zero as eof. At the very least the documentation needs fixing to be consistent. And ideally it needs to document what a return of 0 means (presumably undefined behaviour unless n == 0) and whether a return in the range (0,n) implies that the next call to read will return eof (probably not). (Also, a minor typo: in the example on the Sink concept documentation, write should return std::streamsize, not void.) Richard Smith

2 3

[filesystem] [cygwin] Version 3 will not support BOOST_NO_STD_WSTRING
by Beman Dawes 11 May '09

11 May '09

The GCC 4.4.0 release binary for Windows available from http://www.equation.com/servlet/equation.cmd?call=fortran supports std::wstring, std::wcout, etc. Presumably official Cygwin support will follow. That removes the little remaining incentive I had, so Boost.Filesystem Version 3 will not support BOOST_NO_STD_WSTRING. There had been some previous discussion of this, but it is now definite. I still don't have an exact target date for V3, but plans should become more concrete over the next couple of months. --Beman

2 2

[dynamic_bitset] proposed fix for ticket #2842
by Juan Antonio Zaratiegui Vallecillo, a.k.a. Zara 11 May '09

11 May '09

Dear all, I have suffered the effects described on ticket #2842: "dynamic_bitset.hpp fails to compile with g++ (Ubuntu 4.3.3-5ubuntu2) 4.3.3" after upgrading from Ubuntu 8.10 to 9.04. After some testing, I have found a possible fix, but I would like to know how may I test thoroughly over as many compiler/versions as possible before I may suggest its inclusion in trunk. Fix data: -- tested under gcc versión 4.3.3 (Ubuntu 4.3.3-5ubuntu4) -- tested under gcc versión 4.1.2 20080704 (Red Hat 4.1.2-44) -- Patch data: <PATCH> Index: boost/dynamic_bitset/dynamic_bitset.hpp =================================================================== --- boost/dynamic_bitset/dynamic_bitset.hpp (revision 52752) +++ boost/dynamic_bitset/dynamic_bitset.hpp (working copy) @@ -999,11 +999,17 @@ using detail::dynamic_bitset_impl::access_by_blocks; using detail::dynamic_bitset_impl::value_to_type; +#if BOOST_WORKAROUND(__GNUC__, == 4) && (__GNUC_MINOR__ >= 3) + // NOTE: Explicitly qualificationf of "bits_per_block" + // breaks compilation on gcc 4.3.3 + const bool no_padding = bits_per_block == CHAR_BIT * sizeof(Block); +#else // NOTE: Explicitly qualifying "bits_per_block" to workaround // regressions of gcc 3.4.x const bool no_padding = dynamic_bitset<Block, Allocator>::bits_per_block == CHAR_BIT * sizeof(Block); +#endif const bool enough_table_width = table_width >= CHAR_BIT; </PATCH> TIA Zara

2 2

[scope_exit] Boost.ScopeExit capturing 'this'
by adam.butcher＠selex-comms.com 11 May '09

11 May '09

I wasn't sure whether I had the correct address for Boost.ScopeExit's author Alexander Nasonov, so I've submitted to this list just in case and to get feedback from other users. I have been playing with BOOST_SCOPE_EXIT -- it it very convenient. One thing I would have liked would be to capture 'this' inside member functions. I have created a patch which adds BOOST_SCOPE_EXIT_THIS to do just that. It provides an operator->() in the generated struct which can be used to access the enclosing class's members. The syntax is: BOOST_SCOPE_EXIT_THIS( (&a) (&b) ) { a; b; // local captures (*this)->member; // member access } BOOST_SCOPE_EXIT_END; and can be BOOST_SCOPE_EXIT_THIS() { (*this)->member; } BOOST_SCOPE_EXIT_END; providing the preprocessor allows for empty parameter lists (which gcc does and vc does albeit after disabling a warning to remove noise). The type pointed to by the result of operator->() is correctly cv qualified. It has been tested on gcc 4.3, gcc 4.2, msvc 7.1 and msvc 9.0. I don't have access to other compilers. Boost.Typeof worked fine on gcc for typeof(this) -- mostly because gcc has a native typeof I guess. On visual studio (vc71 and vc90) it was not so good -- a compiler bug ( http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedba… , http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedba… ) that has been marked as 'Won't fix' means that 'this' cannot be used in expressions within template argument lists -- even if those expressions are innocuous typeid()s or sizeof()s for type-inference. The common workaround (capturing a compile-time integer with an enumerator and using the enumerator in the template parameter list) doesn't work with the vc71-specific implementation of Boost.Typeof since it is based on typeid() -- this cannot be captured in a compile-time expression (or I know of no way to that doesn't involve the expression existing in a template argument list). All is not lost though -- the general-purpose sizeof() based approach for the other VC versions works fine for VC71 for determining the typeof 'this'. As such my patch includes a VC>=1300 specific workaround for typeof 'this' determination. This is unfortunate but I couldn't think of any other non-intrusive way of doing it. Please find the attached patch and let me know what you think -- I'm sure this feature would be useful to users -- it saves having to do: TypeOfMyClassWhichCouldBeTedious* self = this BOOST_SCOPE_EXIT( (&self) ) { self->member; } BOOST_SCOPE_EXIT_END; which removes the convenience of BOOST_SCOPE_EXIT in these contexts since something like: struct at_end { TypeOfMyClassWhichCouldBeTedious* self; ~at_end() { self->member; } } at_end = {this}; can be done without any dependencies to achieve the same result. Regards, Adam. ------------------------------------------------------------ This email and any attached files contains company confidential information which may be legally privileged. It is intended only for the person(s) or entity to which it is addressed and solely for the purposes set forth therein. If you are not the intended recipient or have received this email in error please notify the sender by return, delete it from your system and destroy any local copies. It is strictly forbidden to use the information in this email including any attachment or part thereof including copying, disclosing, distributing, amending or using for any other purpose. In addition the sender excludes all liabilities (whether tortious or common law) for damage or breach arising or related to this email including but not limited to viruses and libel. SELEX Communications Limited is a Private Limited Company registered in England and Wales under Company Number 964533 and whose Registered Office is Lambda House, Christopher Martin Rd, Basildon, SS14 3EL. England.

4 8

[1.40.0] Release branch open
by Beman Dawes 11 May '09

11 May '09

The release branch (https://svn.boost.org/svn/boost/branches/release) is open for merging all stable changes from trunk, including bug fixes and major upgrades to existing libraries. Breaking changes should be coordinated via the mailing list with the developers of the other libraries affected. New libraries may be added, but require permission of a release manager. In other words, except for new libraries, merging changes *does not* need permission from a release manager. I.e. just do it! The release schedule: * June 15, 2009: branches/release closed for new libraries and breaking changes to existing libraries. Still open for bug fixes and other routine changes to all libraries. * June 22, 2009: Release managers start QA checks. * July 6, 2009: branches/release closed for major code changes. Still open for serious problem fixes and docs changes. * July 13, 2009: branches/release closed for all library changes except when specific permission given by release manager(s). * July 20, 2009: Beta release target date. Further betas and/or release candidates as feedback dictates. * August 1, 2009: Release ship date. Links relating to this release: * Google Calendar with the release schedule: <http://www.boost.org/development/index.html>. * Release schedule explanation: <http://svn.boost.org/trac/boost/wiki/ReleaseSchedule>. * Release practices for developers: <http://svn.boost.org/trac/boost/wiki/ImprovingPractices>. --The release management team

1 0

[signals2] Compile errors when using signals2
by Carlos Rafael Giani 11 May '09

11 May '09

Hi, I had some compiling errors when I wanted to try out signals2. In predestructible.hpp line 33 there is an extra semicolon (the empty {} scope has a an extra ;). Also, in tracked_objects_visitor.hpp line 85, the "trackable" parameter is unused, which causes a warning. The warning is not critical, but the error is. It basically forces one to either manually fix the predestructible.hpp header, or to stop using the -pedantic flag. My flags: -Wextra -Wall -std=c++98 -pedantic

2 1

Boost Asio in Windows
by Kenny Stone 10 May '09

10 May '09

I'm trying to use asio in linux and windows, and I have to use a very specific way of starting my IO Service to get it to work in windows xp: void start() { tcp::endpoint endpoint = *iterator_; socket_.async_connect(endpoint, boost::bind(&MessageHandler::handle_connect, this, boost::asio::placeholders::error, ++iterator_ ) ); boost::thread t( boost::bind( &boost::asio::io_service::run, &(socket_.get_io_service() ))); t.detach(); //threadPool_.schedule(boost::bind( &boost::asio::io_service::run, &(socket_.get_io_service()) ) ); } The commented out line is what I wanted to use (threadpool), as thread detach is far from an ideal situation. To work in windows, I have to call io_service.run() in this function and thread detach; it doesn't seem to work any other way. Everything pretty much works in linux. Is there a pattern that I should be using here for cross platform usage of the library? Any ideas why the threadpool solution doesn't work in windows? ( http://threadpool.sourceforge.net/) Thanks, -- Kenny Stone Connamara Systems, LLC

2 1

Re: [boost] [test] Automatic registration of tests created with BOOST_PARAM_TEST_CASE
by Jan Stolarek 10 May '09

10 May '09

> Boost.Test do not support this setup out of the box It seems to me that there's no unit testing framework for C++ that would support that (please correct me if I'm wrong). > Which particular part? For example this : "Sub test case names are deduced from the macro argument test_case_name. If you prefer to assign different test case names, you need to use the underlying make_test_case interface instead." More details on that would be nice. It would also be great to add more complex examples. Examples for each section are clear, however problems arise when one tries to combine concepts from many sections. > This is not a good idea. I found it in documentation for Boost 1.34 : http://www.boost.org/doc/libs/1_34_1/libs/test/doc/tests/parameterized_test… > Your best shot probably is to try ot do this in global fixture. Would this be a good solution if I had many tests with lots of data sets? > You can implement your own generator. Could you point me to example on how to do that? >Also you probably should register your test units directly under >framework::master_test_suite() As mentioned in my fisrt mail I have tried that but with no result. It seems that I got something wrong with what I can add to master test suite. Jan

2 1

Re: [boost] [test] Automatic registration of tests created with BOOST_PARAM_TEST_CASE
by Jan Stolarek 10 May '09

10 May '09

Ok, I figured out a solution that seems to be quite elegant, not so verbose and easy to achieve : using namespace boost::unit_test; class DataSet { public : DataSet( /* params */ ) { /* setup single data set */ } ~DataSet( ) { /* teardown single data set */ } /* some fields */ } void testMethod( DataSet* data ) { /* do something with method that's being tested. Use data somehow */ BOOST_CHECK( /* assertion */ ); } BOOST_AUTO_TEST_CASE( TestNameFirstDataSet ) { DataSet dataSet( /* params for first data set */ ); testMethod( dataSet ); } BOOST_AUTO_TEST_CASE( TestNameSecondDataSet ) { DataSet dataSet( /* params for second data set */ ); testMethod( dataSet ); } It's so simple that I wonder why didn't I figure it out right away. It doesn't require extra lines of code (dataSet has to be created somewhere anyway), it even allows to get rid of DataProvider class. Also there is no problem of spliting the tests into many files (I think this could be problematic if I had used global fixture, since all the data sets would have to be defined in one file). Any bad sides of this approach? Jan

1 0

[iostreams] regression - Missing include guard in boost/iostreams/device/mapped_file.hpp
by Bjørn Roald 10 May '09

10 May '09

Hi, Seems like the trunk@46692 commit, 25 june 2008, removed the include guard in boost/iostreams/device/mapped_file.hpp This breaks gcc43 compilation of sources directly including this header. Eg. http://www.mapnik.org/ trunk code. -- Bjørn

2 4

[Review Request] Boost.Convert
by Vladimir Batov 08 May '09

08 May '09

The proposed Boost.Convert has seen some lively discussions and considerable changes. Since then its interface and major implementation details have been unchanged and are being used/tested in an actual development of a system of a moderate size. Therefore, I would like to request a formal review and the component placed into the review queue. The zipped source and documentation are in the Vault: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost-… Thanks, Vladimir.

1 0

[utility][foreach][1.39.0] warning C4512
by Michael Mathews 08 May '09

08 May '09

HI folks, Just upgraded to 1.39.0 and everything works well except I started getting these warnings. >C:\Boost\include\boost-1_39\boost/utility/addressof.hpp(30) : warning C4512: 'boost::detail::addr_impl_ref<T>' : assignment operator could not be generated 1> with 1> [ 1> T=std::vector<double> 1> ] 1> C:\Boost\include\boost-1_39\boost/utility/addressof.hpp(56) : see reference to class template instantiation 'boost::detail::addr_impl_ref<T>' being compiled 1> with 1> [ 1> T=std::vector<double> 1> ] 1> C:\Boost\include\boost-1_39\boost/foreach.hpp(627) : see reference to function template instantiation 'T *boost::addressof<T>(T &)' being compiled 1> with 1> [ 1> T=std::vector<double> 1> ] 1> .\main.cpp(102) : see reference to function template instantiation 'boost::foreach_detail_::auto_any<T> boost::foreach_detail_::contain<std::vector<_Ty>>(std::vector<_Ty> &,boost::mpl::false_ *)' being compiled 1> with 1> [ 1> T=std::vector<double> *, 1> _Ty=double 1> ] msvc9 sp1 warning level 4. I didn't get these warnings in 1.38 enjoy michael

2 1

Does Boost has an utility to replace all OLD Keys with NEW one for MultiMap/Map?
by Tushar Chowdhury 08 May '09

08 May '09

Hi Guys, As of now I failed to get such an algo. I've come up with an proposed solution. Please verify: namespace Boost{ template <typename CONTAINER> void replace_key(CONTAINER& container, const typename CONTAINER::key_type& oldKey, const typename CONTAINER::key_type& newKey) { typename CONTAINER::iterator begin(container.find(oldKey)); for(;;){ if(begin != container.end()){ container.insert(typename CONTAINER::value_type(newKey, begin->second)); container.erase(begin++); begin = container.find(oldKey); } else{ return; } } } } make sense?

6 11

[test] Automatic registration of tests created with BOOST_PARAM_TEST_CASE
by JS 08 May '09

08 May '09

Hi, I want to create a test that a) runs the same testing function with different sets of input data AND b) registers automatically Obviously I can use BOOST_PARAM_TEST_CASE macro for a), but how do I achieve b) at the same time? I've been fighting with the problem for many hours and I have no idea how to do it. Unfortunately the documentation is very cryptic. Here's what I came up with so far: boost-main.cpp : #define BOOST_TEST_DYN_LINK #define BOOST_TEST_MAIN #define BOOST_TEST_MODULE My Master Test Suite #include <boost/test/unit_test.hpp> testSomeFunctions.cpp : using namespace boost::unit_test; class DataSet { public : DataSet( /* params */ ) { /* setup single data set */ } ~DataSet( ) { /* teardown single data set */ } /* some fields */ } class DataProvider { public : DataProvider() { dataSet.push_back( new DataSet( /* params */ ) ); /* add more if necessary */ } ~DataProvider() { /* free memory*/ } std::vector<DataSet*> dataSet; } void testMethod( DataSet* data ) { /* do something with method that's being tested. Use data somehow */ BOOST_CHECK( /* assertion */ ); } BOOST_AUTO_TEST_CASE( TestName ) { DataProvider dataProvider; test_suite* test = BOOST_TEST_SUITE( "I don't think the name matters" ); test->add( BOOST_PARAM_TEST_CASE( &testMethod, dataProvider.dataSet.begin(), dataProvider.dataSet.end() ) ); framework::run( test ); } However this is not correct since test cases created with BOOST_PARAM_TEST_CASE are not registered in the master test suite. If one of the tests fails I get the following log : Running 1 test case... ../test/functions/testSomeFunctions.cpp(67): error in "testMethod": check data->a == data->b failed [2 != 3] *** No errors detected I tried replacing "framework::run( test );" with "framework::master_test_suite().add( test );" but that doesn't work at all (log says that no errors were detected, while there should be one test that fails). I also tried something like this : BOOST_AUTO_TEST_CASE( ActivationFunctionTest ) { DataProvider dataProvider; framework::master_test_suite().add( BOOST_PARAM_TEST_CASE( &testMethod, dataProvider.dataSet.begin(), dataProvider.dataSet.end() ) ); } but the result is the same (No errors detected). What should I do? Jan

2 1

[spirit2] conflict with asio header
by Michael Caisse 07 May '09

07 May '09

I'm not certain if this is an asio issue or spirit2 issue (or user error). I checked Spirit out from the trunk and placed it into a 1.37 boost tree. I'm running gcc 4.3.2. Creating file foo.cpp with the following: --------------- #include <boost/asio.hpp> #include <boost/spirit/include/qi.hpp> --------------- Produces a string of errors including this snippet: from ../src/foo.cpp:3: ../../../library/vendor/boost/boost/proto/make_expr.hpp: At global scope: ../../../library/vendor/boost/boost/proto/make_expr.hpp:935: error: expected nested-name-specifier before numeric constant ../../../library/vendor/boost/boost/proto/make_expr.hpp:935: error: expected â>â before numeric constant ../../../library/vendor/boost/boost/proto/make_expr.hpp:940: error: type/value mismatch at argument 3 in template parameter list for âtemplate<class Tag, class DomainOrA0, class A0, class A1, class A2, class A3, class A4, class Void> struct boost::proto::result_of::make_exprâ ../../../library/vendor/boost/boost/proto/make_expr.hpp:940: error: expected a type, got â0â ../../../library/vendor/boost/boost/proto/make_expr.hpp:940: error: expected initializer before âconstâ Swapping the include order resolves the error. Should I enter a ticket? Michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

3 2

Submitting a patch to the bug/ticket list
by Juan Antonio Zaratiegui Vallecillo, a.k.a. Zara 07 May '09

07 May '09

Well, I have submitted a patch for dynamic_bitset.hpp, and I have seen that the ticket is now 'closed' and 'fixed'. I don know if it is an automatic response from the system, or if I have done something wrong (like, for instance, clicking where I should not click), and in such case I should reopen the ticket. Please, tell me which is the case and what should I do, because I am not happy leaving it this way. BTW, the bug owner is listed as gennaro_prota. Should I try to contact him directly? TIA Zara

2 3

gcc-4.4.0 and boost::optional is giving (spurious?) strict-aliasing warnings
by Brad Spencer 07 May '09

07 May '09

Before I get to the details, let me start by saying that I suspect that these warnings are probably spurious. But, before I go and start asking the compiler folks if they are bugs, I'd like to check here first. If you take unmodified boost-1.38.0 and try to use boost::optional with gcc-4.4.0 -Wall -O3, you seem to get warnings about strict-aliasing rules being broken. If boost::optional (and boost::function) are really broken, then we're probably in trouble :) test.cc: #include <boost/optional.hpp> boost::optional<int> x; int func() { return *x; } On x86_64-unknown-linux-gnu: $ /opt/gcc-4.4.0/bin/g++ -Wall -O3 -I. -c -o test.o test.cc test.cc: In function ‘int func()’: test.cc:5: warning: dereferencing pointer ‘<anonymous>’ does break strict-aliasing rules ./boost/optional/optional.hpp:594: note: initialized from here I have seen some similar issues with boost::bind and boost::function, but I haven't isolated them down to something this simple yet. I figured I'd start by asking about this. So, is it safe to presume that boost::optional is not really breaking the strict aliasing rules? (It's not immediately obvious.) If so, then I can ask the gcc folks about this. Thanks! -- ---------------------------------------------------------- Brad Spencer - spencer(a)starscale.com - www.starscale.com

4 3

[thread] on_tls_prepare in win32\tss_pe.cpp incompatible with static linkage to a /clr object
by Matthew Chambers 06 May '09

06 May '09

I'm very interested in being able to have a native C++ executable which makes use of boost's TSS and also be able to wrap .NET modules with C++/CLI (i.e. /clr). And I much prefer it to be statically linked. The C++/CLI wrappers work fine when they are dynamically linked, but they cause a runtime initialization error (0xc000007b) whenever they are connected in only static links. It doesn't matter whether the host executable is compiled with /clr or not - somehow the MSVC linker knows to add some CLR initialization voodoo to the PE header whenever a static link to a /clr-enabled object is made. And that PE header voodoo seems to be incompatible with some of boost::thread's own brand of PE header voodoo which appears to be intended to provide TLS support for Windows. But as far as I can tell, I was able to get TLS working with MSVC9 even after commenting out the on_tls_prepare lines in tss_pe.cpp - commenting out the other lines wasn't necessary: > #if (_MSC_VER >= 1400) > //#pragma section(".CRT$XIU",long,read) > #pragma section(".CRT$XCU",long,read) > #pragma section(".CRT$XTU",long,read) > #pragma section(".CRT$XLC",long,read) > static __declspec(allocate(".CRT$XLC")) _TLSCB > __xl_ca=on_tls_callback; > // static __declspec(allocate(".CRT$XIU"))_PVFV p_tls_prepare = > on_tls_prepare; > static __declspec(allocate(".CRT$XCU"))_PVFV p_process_init = > on_process_init; > static __declspec(allocate(".CRT$XTU"))_PVFV p_process_term = > on_process_term; > #else I put together a test case that I'm pretty sure shows that TLS still works without that function. At the very least, can there be some preprocessor define to manually disable it for CLR compatibility? Or perhaps there is a way to adjust this voodoo to be compatible with the CLR initialization? I'm hosting the test case at: http://fenchurch.mc.vanderbilt.edu/files/TLS_CLR_Test.7z It includes a main function which runs a test of the TSS semantics, and a CLR class which tests console output via C++/CLI. I included binaries and the boost_thread.lib files for both the broken and "fixed" versions of tss_pe.cpp. Thanks, Matt Chambers

2 2