- Boost-users - lists.boost.org

boost_1.36 beta on AIX 5.3 with gcc 4.2.4: Compile errors in math
by Andrej van der Zee 01 Aug '08

01 Aug '08

Hi, Building on IBM AIX 5.3 with gcc 4.2.4 gives me the compile-time error below in math repeating itself endlessly. No such problems for boost_1.35. ...failed gcc.compile.c++ bin.v2/libs/math/build/gcc-4.2.4/release/threading-multi/cbrt.o... gcc.compile.c++ bin.v2/libs/math/build/gcc-4.2.4/release/threading-multi/copysign.o In file included from libs/math/build/../src/tr1/copysign.cpp:7: ./boost/math/tr1.hpp:438: error: 'boost::math::tr1::expm1' declared as an 'inline' variable ./boost/math/tr1.hpp:438: error: 'long double boost::math::tr1::expm1' redeclared as different kind of symbol ./boost/math/tr1.hpp:436: error: previous declaration of 'double boost::math::tr1::expm1(double)' ./boost/math/tr1.hpp:438: error: expected primary-expression before 'double' ./boost/math/tr1.hpp:438: error: expected `)' before 'double' ./boost/math/tr1.hpp:459: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:460: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:460: error: '::type' has not been declared ./boost/math/tr1.hpp:467: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:468: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:468: error: '::type' has not been declared ./boost/math/tr1.hpp:475: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:476: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:476: error: '::type' has not been declared ./boost/math/tr1.hpp:553: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:554: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:554: error: '::type' has not been declared ./boost/math/tr1.hpp:561: error: expected primary-expression before 'class' ./boost/math/tr1.hpp:562: error: 'T2' was not declared in this scope ./boost/math/tr1.hpp:562: error: '::type' has not been declared ./boost/math/tr1.hpp:611: error: expected initializer before '<' token ./boost/math/tr1.hpp:612: error: expected initializer before '<' token It seems that the compiler sees the two following functions as the same symbols, although the name slight differs: inline double expm1(double x) { return boost::math::tr1::boost_expm1(x); } inline long double expm1l(long double x) { return boost::math::tr1::boost_expm1l(x); } Renaming the second function to __expm1l makes the error disappear. The same goes for the following functions: inline double log1p(double x) { return boost::math::tr1::boost_log1p(x); } inline long double log1pl(long double x) { return boost::math::tr1::boost_log1pl(x); } And the following: inline double nextafter(double x, double y) { return boost::math::tr1::boost_nextafter(x, y); } inline long double nextafterl(long double x, long double y) { return boost::math::tr1::boost_nextafterl(x, y); } Well, there is a clear pattern. After prefixing the second function with __ makes the errors go away. Could somebody enlighten me why this is? Greets, Andrej __________________________________________________________ Not happy with your email address?. Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

2 1

[PATCH]: filesystem: Shadow Variables Cause Warnings/Errors When Headers Are Not in System Path
by Grant Erickson 01 Aug '08

01 Aug '08

In working through cross-compilation issues with boost, particularly the filesystem library, I discovered the following error reproduced with the following test case with both boost 1.34.1 and 1.35.0: FAILS: echo "#include <boost/filesystem.hpp>\nint main (void) { return (0); }" | g++ -o test -I/${BuildRoot}/results/boost/include -Werror -Wall -Wshadow -x c++ - PASSES: echo "#include <boost/filesystem.hpp>\nint main (void) { return (0); }" | g++ -o test -I/usr/include -Werror -Wall -Wshadow -x c++ - The failing case complains about 'what', 'path1' and 'path2' argument shadowing in boost/filesystem/path.hpp with respect to like-named member functions. Since GCC does not enforce warning options on headers in /usr/include, this only shows up when building against a boost installation outside /usr/include, as in the above failure example. The patch to address this is: Signed-off-by: Grant Erickson <gerickson(a)nuovations.com> --- --- boost_1_35_0/boost/filesystem/path.hpp 2008-07-30 16:54:53.000000000 -0700 +++ boost_1_35_0/boost/filesystem/path.hpp.N 2008-07-30 16:59:42.000000000 -0700 @@ -577,23 +577,23 @@ // BOOST_FILESYSTEM_DECL version works for VC++ but not GCC. Go figure! inline const char * what( const char * sys_err_what, - const path & path1, const path & path2, std::string & target ) + const path & path1_arg, const path & path2_arg, std::string & target ) { try { if ( target.empty() ) { target = sys_err_what; - if ( !path1.empty() ) + if ( !path1_arg.empty() ) { target += ": \""; - target += path1.file_string(); + target += path1_arg.file_string(); target += "\""; } - if ( !path2.empty() ) + if ( !path2_arg.empty() ) { target += ", \""; - target += path2.file_string(); + target += path2_arg.file_string(); target += "\""; } } @@ -607,7 +607,7 @@ template<class Path> const char * what( const char * sys_err_what, - const Path & /*path1*/, const Path & /*path2*/, std::string & /*target*/ ) + const Path & /*path1_arg*/, const Path & /*path2_arg*/, std::string & /*target*/ ) { return sys_err_what; } @@ -624,14 +624,14 @@ typedef Path path_type; - basic_filesystem_error( const std::string & what, + basic_filesystem_error( const std::string & what_arg, system::error_code ec ); - basic_filesystem_error( const std::string & what, - const path_type & path1, system::error_code ec ); + basic_filesystem_error( const std::string & what_arg, + const path_type & path1_arg, system::error_code ec ); - basic_filesystem_error( const std::string & what, const path_type & path1, - const path_type & path2, system::error_code ec ); + basic_filesystem_error( const std::string & what_arg, const path_type & path1_arg, + const path_type & path2_arg, system::error_code ec ); ~basic_filesystem_error() throw() {} @@ -1385,8 +1385,8 @@ template<class Path> basic_filesystem_error<Path>::basic_filesystem_error( - const std::string & what, system::error_code ec ) - : system::system_error(ec, what) + const std::string & what_arg, system::error_code ec ) + : system::system_error(ec, what_arg) { try { @@ -1397,29 +1397,29 @@ template<class Path> basic_filesystem_error<Path>::basic_filesystem_error( - const std::string & what, const path_type & path1, + const std::string & what_arg, const path_type & path1_arg, system::error_code ec ) - : system::system_error(ec, what) + : system::system_error(ec, what_arg) { try { m_imp_ptr.reset( new m_imp ); - m_imp_ptr->m_path1 = path1; + m_imp_ptr->m_path1 = path1_arg; } catch (...) { m_imp_ptr.reset(); } } template<class Path> basic_filesystem_error<Path>::basic_filesystem_error( - const std::string & what, const path_type & path1, - const path_type & path2, system::error_code ec ) - : system::system_error(ec, what) + const std::string & what_arg, const path_type & path1_arg, + const path_type & path2_arg, system::error_code ec ) + : system::system_error(ec, what_arg) { try { m_imp_ptr.reset( new m_imp ); - m_imp_ptr->m_path1 = path1; - m_imp_ptr->m_path2 = path2; + m_imp_ptr->m_path1 = path1_arg; + m_imp_ptr->m_path2 = path2_arg; } catch (...) { m_imp_ptr.reset(); } } ---

2 1

Re: [Boost-users] Boost spirit: overlapping inner struct result
by Kesseli Pascal 31 Jul '08

31 Jul '08

Hi Joel Thanks for your reply. That simple example you stated compiles fine, though. Is it possible that the templates might have ane impact here? "Joel de Guzman" <joel(a)boost-consulting.com> schrieb im Newsbeitrag news:<g6pu9q$r4b$1(a)ger.gmane.org>... > Pascal Kesseli wrote: > > Hi everyone > > > > When trying to compile the serialization library for my Montavista embedded > > computer, I am getting a strange error message concerning boost > > spirit/core/primitives/numerics.hpp stating that struct result in > > sign_parser has already been defined before. > > > > Back then, I couldn't deny that fact, as result is already defined in > > sign_parser's superclass parser, so I renamed the struct in the subclass to > > tresult and the library compiled fine. > > > > Currently, I am asking myself what influence such a change might have on > > the > > running program. I am having unexplainable SIGABRT signals appearing and > > killing my program, thus I suspect my change was not that mere after all. > > > > Is there a better workaround I could use to solve this problem? > > > > Thanks in advance for your replies and best regards > > I don't quite understand what's happening here. It shouldn't be > an error if a base class and a subclass share the same result > struct. Try this short example: > > struct x > { > struct result { typedef int type; }; > }; > > struct y : x > { > struct result { typedef double type; }; > }; > > Regards, > -- > Joel de Guzman > http://www.boostpro.com > http://spirit.sf.net

1 0

is BOOST_STATIC_WARNING part of boost public interface?
by frederic.bron＠alcan.com 31 Jul '08

31 Jul '08

I cannot find any documentation about BOOST_STATIC_WARNING, is it intended to be used by users or only internal to the library? F. Bron Avis : Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes en tout ou en partie. Notice: This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part.

3 3

[boost.thread] destruction of condition variables
by Vladimir Pozdyaev 31 Jul '08

31 Jul '08

Hello. Is it feasible to make CVs' destructors thread-safe? Consider the code below. It causes a failed assertion in basic_condition_variable::dispose_entry(...) when cv's destructor kicks in while notify_all() is still cleaning up. The problem is easily resolved by adding another mutex, but it would just look nicer if we could rely on cv's own features for that. Another alternative would be to make wait() return only after notify_xxx() has really finished its job. (Yes, I guess this code is not exactly a Good Practice :) , but it's not exactly logically inconsistent either. Or is it?) [ Boost 1.35.0, MSVC2008, Win32 Debug configuration Actually, it's not easy to make this particular code fail; adding a short sleep() in the beginning of dispose_entry(...) helps. This problem managed to appear quite systematically in a more complex program though. ] ---- Vladimir :::CODE::: #include <boost/thread.hpp> #include <boost/bind.hpp> class C { private: boost::mutex m; boost::condition_variable cv; public: ~C() { boost::mutex::scoped_lock l( m ); cv.wait( l ); } void fn() { boost::this_thread::sleep( boost::posix_time::milliseconds( 500 ) ); cv.notify_all(); } }; int main() { C c; boost::thread t( boost::bind( &C::fn, &c ) ); return 0; }

5 8

Boost with gcc 3.4.3?
by Karthick Gururaj 31 Jul '08

31 Jul '08

Hello, I am porting code which compiles with gcc 3.2.3 and uses boost, to compile for gcc 3.4.3. I get the following compilation errors. Also there are a lot of erros regarding scope, which can be fixed. Can anybody suggest what I should be looking at to resolve this. Regards Karthick /inc/boost/integer_fwd.hpp:70: error: `long_long_type' is not a member of `boost' /inc/boost/integer_fwd.hpp:70: error: `long_long_type' is not a member of `boost' /inc/boost/integer_fwd.hpp:70: error: template argument 1 is invalid /inc/boost/integer_fwd.hpp:73: error: `ulong_long_type' is not a member of `boost' /inc/boost/integer_fwd.hpp:73: error: `ulong_long_type' is not a member of `boost' /inc/boost/integer_fwd.hpp:73: error: template argument 1 is invalid /inc/boost/integer.hpp:20, inc/word_includes.hpp:34, /inc/word.hpp:34, /inc/boost/integer_traits.hpp:162: error: `long_long_type' is not a member of `boost' /boost/integer_traits.hpp:162: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:163: error: template argument 1 is invalid /boost/integer_traits.hpp:163: error: explicit specialization of non-template `<type error>' /inc/boost/integer_traits.hpp:163: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:163: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:163: error: template argument 1 is invalid /inc/boost/integer_traits.hpp:164: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:164: error: `long_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:165: error: template argument 1 is invalid /inc/boost/integer_traits.hpp:165: error: `<type error>' is not a valid type for a template constant parameter /inc/boost/integer_traits.hpp:165: error: `<type error>' is not a valid type for a template constant parameter /inc/boost/integer_traits.hpp:168: error: `ulong_long_type' is not a member of `boost' //inc/boost/integer_traits.hpp:168: error: `ulong_long_type' is not a member of `boost' /inc/boost/integer_traits.hpp:169: error: template argument 1 is invalid /inc/boost/integer_traits.hpp:169: error: explicit specialization of non-template `<type error>'

2 2

boost program options future plans
by Aljaz 31 Jul '08

31 Jul '08

Hello Having an option to save-back configuration files would be a great feature of program option library. I've been wondering if there are any future plans for this? Also I have came across website http://code.google.com/p/clipo/ where idea for Clipo : Command Line Interpreter library based on the boost Program Option library is mentioned. This would be very useful as well. What do you think? Thanks for responses! Aljaz

2 1

about shared_ptr and object_pool
by Ken zhang 31 Jul '08

31 Jul '08

Hi dear all. I have a class named "session" look like below code: class session : public boost::enable_shared_from_this< session >, private boost::noncopyable { public: session(boost::asio::io_service& io_service); ..... }; I want use boost::object_pool for allocate memory for session. class host { public: typedef boost::object_pool<session> session_pool; host() : new_session_( session_pool_.construct(), boost::bind(&session_pool::destroy, &session_pool_)) { } public: boost::shared_ptr< session > new_session_; session_pool session_pool_; }; but there has a compiler error was occured: 1> d:\development\boost_1_35_0\boost\bind.hpp(1613) : warning C4180: qualifier applied to function type has no meaning; ignored 1> d:\development\boost_1_35_0\boost\bind.hpp(1647) : see reference to class template instantiation 'boost::_bi::add_cref<Pm,I>' being compiled 1> with 1> [ 1> Pm=void (__thiscall boost::object_pool<session>::* )(session *), 1> I=1 1> ] 1> d:\development\coreframework\portal\src\portal_server.cpp(16) : see reference to class template instantiation 'boost::_bi::dm_result<Pm,A1>' being compiled 1> with 1> [ 1> Pm=void (__thiscall boost::object_pool<session>::* )(session *), 1> A1=portal_server::session_pool *__w64 1> ] 1>d:\development\boost_1_35_0\boost\mem_fn.hpp(318) : warning C4180: qualifier applied to function type has no meaning; ignored 1> d:\development\boost_1_35_0\boost\bind\bind_template.hpp(344) : see reference to class template instantiation 'boost::_mfi::dm<R,T>' being compiled 1> with 1> [ 1> R=void (session *), 1> T=boost::object_pool<session> 1> ] 1>Project : error PRJ0002 : Error result 1 returned from 'C:\Program Files\Microsoft Visual Studio 8\VC\bin\cl.exe'. I use Microsoft visual studio 8 (vs2005). Thanks all Best regards. Yours Kenneth.Sh

2 2

boost::function, using undefined class?
by Erzengel Des Lichtes 31 Jul '08

31 Jul '08

Hello, I'm having an issue with boost::function in Visual Studio.NET 2005. In the following program: #include <boost/function.hpp> void SomeFunc(int* Blah) { //DoSomething } int __cdecl main(int argc, char* argv[], char* envp[]) { boost::function<void(*)(int*)> MyFunc; } I get the following error message: (Project Directory)\boostfunctest.cpp(11) : error C2079: 'MyFunc' uses undefined class 'boost::function' with [ Signature=void (__stdcall *)(int *) ] If I leave off the "(*)" it will compile, but this is just a simplified version of my real problem. The main reason this is a concern is I have a templated function that looks like this: template<typename Signature> boost::function<Signature> GetFunction(Signature ToCall); Which I intend to use to record and "play back" certain function calls. However, when it sees the signiture from the function pointer, it ALWAYS sees it as 'void(*)(int*)' (for example), rather than 'void(int*)' and fails to compile. For example, the following program: #include <boost/function.hpp> void SomeFunc(int* Blah) { //DoSomething } template<typename Signature> boost::function<Signature> GetFunction(Signature ToCall) { //TODO: Check if function is in list, add it to list, etc. return boost::function<Signature>(ToCall); } int __cdecl main(int argc, char* argv[], char* envp[]) { GetFunction(SomeFunc); } I get: (Project Directory)\boostfunctest.cpp(17) : error C2027: use of undefined type 'boost::function' with [ Signature=void (__stdcall *)(int *), Allocator=std::allocator ] So, anyone have any idea what's wrong and how to fix it? Thanks for any help. Note: I am compiling with /Gz, but compiling with /Gd and /Gr merely changes the "__stdcall" to "__cdecl" and "__fastcall" in the error messages, respectively, so it does not seem to matter which calling convention is used. -- Erzengel des Lichtes 光の大天使 (Hikari no Daitenshi) Archangel of Light

2 2

Passing Mutexes
by Simon Pickles 31 Jul '08

31 Jul '08

Hi, I am trying to implement a simple producer/consumer system with two or more threads. The main thread has a consumer class which creates producers. These producers perform synchronous blocking operations then post their outcome into a std::vector of results which was passed from the main consumer. class consumer { public: consumer() { m_results = boost::shared_ptr<std::vector<result> >( new std::vector<result> ); new producer( m_results, m_mutex ); // do a single task and put result in m_results } void Process() { result r; { boost::mutex::scoped_lock lock(m_mutex); r = m_results.pop.front(); } // Do stuff with r } private: boost::mutex m_mutex; boost::shared_ptr<std::vector<result> > m_results; }; class producer { producer( boost::shared_ptr<std::vector<result> > results, boost::mutex& mtx ) { boost::thread( boost::bind( &DoInThread, this, results, mtx ) ); // actually uses a threadpool but not relevant here. } void DoInThread( boost::shared_ptr<std::vector<result> > results, boost::mutex& mtx ) { result r; // do long async op and store in r boost::mutex::scoped_lock lock(mtx); results->push_back(r); } }; /////////////// I am trying to share a single mutex with both producer and consumer. However I get a noncopyable error, even if I pass a reference. Can anyone point out what the correct approach is? Thanks Simon

3 4