October 2005 - Boost-users - lists.boost.org

Re: [Boost-users] [bind] Member fn has defeated me
by BRIDGES Dick 05 Oct '05

05 Oct '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Peter Dimov > Sent: Tuesday, October 04, 2005 3:49 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [bind] Member fn has defeated me > > > BRIDGES Dick wrote: > > > class Bar { > > typedef void (*pf)(bool); > > If you make this > > typedef boost::function<void(bool)> pf; > [snip] > > then > > Bar bar_( boost::bind(&X::f, &x) ); > > should work. But you can't get an oridnary function pointer from > boost::bind; a function pointer doesn't have enough state to > represent &X::f > + &x. <error_message> Building file: ../main.cpp g++ -D_REENTRANT -I/boost_1_33_0 -O0 -g3 -Wall -c - fmessage-length=0 -omain.o ../main.cpp /boost_1_33_0/boost/bind.hpp: In instantiation of ?boost::_bi::result_traits<boost::_bi::unspecified, void (X::*)(bool)>?: /boost_1_33_0/boost/bind/bind_template.hpp:15: instantiated from ?boost::_bi::bind_t<boost::_bi::unspecified, void (X::*)(bool), boost::_bi::list1<boost::_bi::value<X*> > >? ../main.cpp:197: instantiated from here /boost_1_33_0/boost/bind.hpp:63: error: ?void (X::*)(bool)? is not a class, struct, or union type /boost_1_33_0/boost/bind/bind_template.hpp: In instantiation of ?boost::_bi::bind_t<boost::_bi::unspecified, void (X::*)(bool), boost::_bi::list1<boost::_bi::value<X*> > >?: ../main.cpp:197: instantiated from here /boost_1_33_0/boost/bind/bind_template.hpp:15: error: no type named ?type? in ?struct boost::_bi::result_traits<boost::_bi::unspecified, void (X::*)(bool)>? ... [previous line repeated 23 times - increasing __LINE__] ... /boost_1_33_0/boost/function/function_template.hpp: In static member function ?static void boost::detail::function::void_function_obj_invoker1<Functio nObj, R, T0>::invoke(boost::detail::function::any_pointer, T0) [with FunctionObj = boost::_bi::bind_t<boost::_bi::unspecified, void (X::*)(bool), boost::_bi::list1<boost::_bi::value<X*> > >, R = void, T0 = bool]?: /boost_1_33_0/boost/function/function_template.hpp:479: instantiated from ?void boost::function1<R, T0, Allocator>::assign_to(FunctionObj, boost::detail::function::function_obj_tag) [with FunctionObj = boost::_bi::bind_t<boost::_bi::unspecified, void (X::*)(bool), boost::_bi::list1<boost::_bi::value<X*> > >, R = void, T0 = bool, Allocator = std::allocator<void>]? /boost_1_33_0/boost/function/function_template.hpp:430: instantiated from ?void boost::function1<R, T0, Allocator>::assign_to(Functor) [with Functor = boost::_bi::bind_t<boost::_bi::unspecified, void (X::*)(bool), boost::_bi::list1<boost::_bi::value<X*> > >, R = void, T0 = bool, Allocator = std::allocator<void>]? /boost_1_33_0/boost/function/function_template.hpp:294: instantiated from ?boost::function1<R, T0, Allocator>::function1(Functor, typename boost::enable_if_c< boost::type_traits::ice_not< boost::is_integral<Functor>::value>::value, int>::type) [with Functor = boost::_bi::bind_t<boost::_bi::unspecified, void (X::*)(bool), boost::_bi::list1<boost::_bi::value<X*> > >, R = void, T0 = bool, Allocator = std::allocator<void>]? /boost_1_33_0/boost/function/function_template.hpp:638: instantiated from ?boost::function<R ()(T0), Allocator>::function(Functor, typename boost::enable_if_c< boost::type_traits::ice_not< boost::is_integral<Functor>::value>::value, int>::type) [with Functor = boost::_bi::bind_t<boost::_bi::unspecified, void (X::*)(bool), boost::_bi::list1<boost::_bi::value<X*> > >, R = void, T0 = bool, Allocator = std::allocator<void>]? ../main.cpp:197: instantiated from here /boost_1_33_0/boost/function/function_template.hpp:136: error: no match for call to ?(boost::_bi::bind_t<boost::_bi::unspecified, void (X::*)(bool), boost::_bi::list1<boost::_bi::value<X*> > >) (bool&)? make: *** [main.o] Error 1 </error_message> Peter, Your suggestion sure made sense. I clearly did something wrong but can't figure out what that would be. I must be interpreting the error message incorrectly. I interpret it to say that the compiler can't find the definition of X but X x; x.f(true); compiles without any problem. Where should I be looking? Regards, Dick

2 1

ld warnings when building boost on Fedora Core 4 with gcc 3.4.4
by Ken Roser 05 Oct '05

05 Oct '05

I've recently switched my Linux system to Fedora Core 4 which has gcc 4.0.1 as the default compiler. Since the code I'm developing must be built with gcc 3.4.4, I have installed a copy of gcc 3.4.4 at /usr/local/gcc/gcc34. When I build boost with this compiler I get hundred of similar errors from /usr/bin/ld. I'll attach those warnings to the end of this email. I invoked the build with the command: ./bjam -d2 --with-serialization -sGCC_ROOT_DIRECTORY=/usr/local/gcc/gcc34 -sBUILD="release" I do see boost get built using my specified compiler but get all the warnings. Building boost without specifying the gcc 3.4.4 compiler does not produce any errors. I suspect the problem has something to do with the version of ld that gets invoked but even if it does, how would I fix it. ld is version: GNU ld version 2.15.94.0.2.2 20041220 Can anyone help? Build output follows in the proximity of the warnings: LD_LIBRARY_PATH=bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true:$LD_LIBRARY_PATH export LD_LIBRARY_PATH "/usr/local/gcc/gcc34/bin/g++" -s -fPIC -shared -o "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/libboost_serialization-gcc-1_33.so.1.33.0" -L"/usr/local/gcc/gcc34/lib" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_archive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_archive_impl.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_iarchive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_iserializer.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oserializer.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_pointer_iserializer.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_pointer_oserializer.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_serializer_map.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_text_iprimitive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_text_oprimitive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_xml_archive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/binary_iarchive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/binary_oarchive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/extended_type_info.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/extended_type_info_no_rtti.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/extended_type_info_typeid.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/polymorphic_iarchive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/polymorphic_oarchive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/stl_port.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/text_iarchive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/text_oarchive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/void_cast.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/xml_grammar.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/xml_iarchive.o" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/xml_oarchive.o" -Wl,-rpath-link,. -Wl,-soname,libboost_serialization-gcc-1_33.so.1.33.0 ln -fs "libboost_serialization-gcc-1_33.so.1.33.0" "bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/libboost_serialization-gcc-1_33.so" /usr/bin/ld: `.L3' referenced in section `.rodata' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o /usr/bin/ld: `.L13' referenced in section `.rodata' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o /usr/bin/ld: `.L4' referenced in section `.rodata' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o /usr/bin/ld: `.L5' referenced in section `.rodata' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o /usr/bin/ld: `.L6' referenced in section `.rodata' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o /usr/bin/ld: `.L7' referenced in section `.rodata' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o /usr/bin/ld: `.L8' referenced in section `.rodata' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o /usr/bin/ld: `.L9' referenced in section `.rodata' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o: defined in discarded section `.gnu.linkonce.t._ZNK5boost7archive17archive_exception4whatEv' of bin/boost/libs/serialization/build/libboost_serialization.so/gcc/release/shared-linkable-true/basic_oarchive.o

2 2

[Boost][mpl] vector_c boolean operations
by Noel Belcourt 05 Oct '05

05 Oct '05

Hi, I'm new to the list so this may have been answered elsewhere (like a FAQ for MPL) but I couldn't find it. I've got 2 vector_c types like this typedef vector_c<int, 1,2,1,1,-2,0,1> p1; typedef vector_c<int, 0,3,0,-1,1,3,5> p2; and a resultant type defined as typedef vector_c<int, 1,1,0,1,1,0,1> r; that I want to compare at compile time using logic like this r = p1 || p1 && p2 This pseudo code is what I want to do but I know this doesn't work. Can anyone can suggest a better approach? template <class R, class P1, class P2> struct validate_checkin : boost::mpl::equal< boost::mpl::placeholders::_1, boost::mpl::or_< boost::mpl::placeholders::_2, boost::mpl::and_< boost::mpl::placeholders::_2, boost::mpl::placeholders::_3 >, >, > {}; Regards, -- Noel Belcourt

4 7

Re: [Boost-users] Type List Iteration?
by Sohail Somani 05 Oct '05

05 Oct '05

Is there some trouble with defining: class Base { virtual void some_function() = 0; }; ??? I can understand the void f() entry point for C callbacks but you can use C++ to do the work for you. Unless I'm missing something. > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Duane Murphy > Sent: Tuesday, October 04, 2005 2:38 PM > To: Boost Users > Subject: [Boost-users] Type List Iteration? > > > How do I iterate over a type list and call a function? MPL? > > I have a base class BASE that has several subclasses A, B, C > that have special capabilities, but no way to identify those > capabilities aside from the type. > > I would like to determine if an object of type BASE is also > of one of the special subclasses: > > ie > void f( BASE* base) > { > if ( dynamic_cast< A* >( base ) != NULL ) > { > some_function( dynamic_cast< A* >( base ) ); > } > else if ( dynamic_cast< B* >( base ) != NULL ) > { > some_function( dynamic_cast< B* >( base ) ); > } > else if ( dynamic_cast< C* >( base ) != NULL ) > { > some_function( dynamic_cast< C* >( base ) ); > } > } > > I think you can see why I'd like a type list iterator > solution to this. > > I have arranged for the some_function to be a template as > well to make things easier. > > What I am looking for is the equivalent of find_if() but for > types and done at run time. I looked over MPL, but MPL seems > to apply at compile time without a door to the run time world. :-) > > Thanks for your helpful tips! > > ...Duane > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

3 2

[bind] Member fn has defeated me
by BRIDGES Dick 05 Oct '05

05 Oct '05

void foo(bool){} struct X { void f(bool b) {} } class Bar { typedef void (*pf)(bool); public: Bar(pf fn){ fn(true); } }; int main( int argc, char **argv ) { Bar bar_(foo); // ok. X x; Bar bar_(boost::bind(&X::f, &x)()); // compile fails. /*LOTS* of other failed attempts with various errors. 8( return(0); } <error_msg edited=yes instance="one of many"> error: no matching function for call to 'X::x()' candidates are: void X::x(bool). </error_msg> I've been reduced to [shudder] "...trying things." I'm simply trying to construct one class by passing in a function pointer (that happes to be a class member). Could someone point me in the right direction? Regards, Dick Bridges

2 1

using boost test framework with PWLIB
by Bondarenko Denis 04 Oct '05

04 Oct '05

Hello! I got a question about unit testing. I have an application, which uses PWLIB (http://www.voxgratia.org/docs/pwlib/pwlib-v1_7_4/index.html) This library creates MAIN function by it's own macros. When I'm trying to write unit tests for my application I have to use PWLIB. Can I use boost test unit framework with PWLIB application? As I understand, Boost test unit framework will try to create its MAIN function by its macros and this will cause to problems. Is it possible to use both - Boost test framework and PWLIB library? Will be grateful for your help. Storm.

2 2

The internal compiler error (python), gcc 4.0.2 of windows
by Huifeng Shen 04 Oct '05

04 Oct '05

The compiler is compiled by myself. The official mingw website only release the gcc 3.44. I use this complier to compile the boost 1.33.0 and find there is some internal compiler error when compiling python. Since I am not a expert of gcc. I report this and hope it is helpful. I give the all internal compiler error as below C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/object/class.cpp:688: internal compiler error: output_operand: invalid expression as operand Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/list.cpp: In constructor 'boost::python::detail::list_base::list_base(const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/list.cpp:23: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/long.cpp: In constructor 'boost::python::detail::long_base::long_base(const boost::python::api::object&, const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/long.cpp:34: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/dict.cpp: In constructor 'boost::python::detail::dict_base::dict_base(const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/dict.cpp:40: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/tuple.cpp: In constructor 'boost::python::detail::tuple_base::tuple_base(const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/tuple.cpp:20: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/str.cpp: In constructor 'boost::python::detail::str_base::str_base(const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/str.cpp:40: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/object/class.cpp:688: internal compiler error: output_operand: invalid expression as operand Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/object/class.cpp:688: internal compiler error: output_operand: invalid expression as operand Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/list.cpp: In constructor 'boost::python::detail::list_base::list_base(const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/list.cpp:23: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/long.cpp: In constructor 'boost::python::detail::long_base::long_base(const boost::python::api::object&, const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/long.cpp:34: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/dict.cpp: In constructor 'boost::python::detail::dict_base::dict_base(const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/dict.cpp:40: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/tuple.cpp: In constructor 'boost::python::detail::tuple_base::tuple_base(const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/tuple.cpp:20: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/str.cpp: In constructor 'boost::python::detail::str_base::str_base(const boost::python::api::object&)': C:\opt\boost\libs\python\build\../src/str.cpp:40: internal compiler error: in valid_in_set, at tree-ssa-pre.c:1082 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. C:/opt/boost/boost/python/detail/wrapper_base.hpp:17: warning: type attributes are honored only at type definition C:/opt/boost/boost/python/object/instance.hpp:14: warning: type attributes are honored only at type definition C:\opt\boost\libs\python\build\../src/object/class.cpp:688: internal compiler error: output_operand: invalid expression as operand Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions.

2 1

inconvenient for boost::thread::sleep
by RocWood 04 Oct '05

04 Oct '05

boost::thread::sleep, IMHO, it's too inconvenient. I get these example code to sleep 1 second, { boost::xtime xt; boost::xtime_get(&xt, boost::TIME_UTC); xt.sec += 1; // change xt to next second boost::thread::sleep(xt); } and, only 1 line in another platform(origianl plaform or java) { sleep(1000); } hmmm... Too inconvenient, and, to make things worse, quite a heavy calling. Is there any suggestion for me? Thanks.

4 3

Status of logging library
by Austin Bingham 03 Oct '05

03 Oct '05

Does anyone know what the status of John Torjo's logging library is? I've noticed that it's "in the review queue". Does this indicate that it's largely just a matter of time before it's ratified? If so, how long might this matter of time be? Thanks. -- Austin Bingham "If I were creating the world I wouldn't mess about with butterflies and daffodils. I would have started with lasers, eight o'clock, Day One!" Evil

2 1

[wave] Error when parsing files from ACE (Adaptive Communication Environment)
by Yariv Tal 03 Oct '05

03 Oct '05

Hi. I use the ACE library (http://www.cs.wustl.edu/~schmidt/ACE.html) which is known for being highly portable. When using wave to pre-process my code, which includes files from the ACE lib, wave fails on the following code snippet: -------------snippet------------------- // The number of bytes in a short. # if !defined (ACE_SIZEOF_SHORT) # if (USHRT_MAX) == 255U # define ACE_SIZEOF_SHORT 1 # elif (USHRT_MAX) == 65535U # define ACE_SIZEOF_SHORT 2 # elif (USHRT_MAX) == 4294967295U # define ACE_SIZEOF_SHORT 4 # elif (USHRT_MAX) == 18446744073709551615U <===[fails here] # define ACE_SIZEOF_SHORT 8 # else # error: unsupported short size, must be updated for this platform! # endif /* USHRT_MAX */ # endif /* !defined (ACE_SIZEOF_SHORT) */ -------------end snippet------------------- Note: USHRT_MAX is defined as 0xffff The failure occurs at the designated line, due to an ill-formed number. I suppose that the number is just too big, but shouldn't the comparison never even be "reached"? (since the previous elif would have been true) I am not too familiar with the standard, so I don't know if emitting an error for this case is correct, but my intuition is that even if this is not standard conforming, there should at least be a flag allowing this, since I assume (if it is used in such a highly portable library) that it _IS_ supported by most preprocessors out there. Apart from that, great lib! I just started using it, but I already love it. Yariv Tal.

2 1