November 2004 - Boost - lists.preview.boost.org

RE: [boost] Another logo proposal
by Robert Geiman 22 Nov '04

22 Nov '04

---- Original Message ---- From: joaquin(a)tid.es To: boost(a)lists.boost.org Subject: RE: [boost] Another logo proposal Date: Mon, 22 Nov 2004 16:49:12 +0100 >Here's my take. I'm providing b/w and color versions. The idea >is to provide an abstract logo to associate with Boost while >retaining >the visual link with the previous artwork (through using the same >Impact font for the name, a very appropriate font IMHO.) >Some more rationales behind the proposal: > >* It can be easily rasterized. >* It goes well with flat backgrounds. >* It works as a transition from the old logo. > >As for the logo itself, it tries to convey the following >connotations: > >* Its square shape, and the fact that is bottom aligned >with the text, gives a sense of solidness. >* It reminds the reader of a set of construction toolkit >pieces, which associates well with Boost being a repository of >general purpose libraries. >* The "++" part of C++ is retained, integrated into the >logo. Going a little pedantic, one can even recognize >the logo as a deconstruction of "C++", where the L-shaped >pieces are the two halves of an upper "C", split and shifted. > >Dya like it? Yes, I like the simplicity a lot. However, I'd also make a slight change to the background of the ++. Could you remove the lower right background of the ++, and instead mirror the upper left background vertically. That is, the background would appear in the upper and lower left area of the ++. To me this would look better as the background would look like the letter C, which would go nicely with the ++. - Robert Geiman

1 0

[serialization] std::set compile errors
by Jeff Flinn 22 Nov '04

22 Nov '04

Robert, boost 1.32, with VC7.1 I'm getting compiler errors in two unrelated translation units both dealing with std::set<std::string> data members. I've gone through and ensured that i've #include'd the <set.hpp> and <string.hpp> headers from boost/serialization. Any ideas on what might be causing this problem? This has worked fine previously with boost 1.31 and serialization20 version of the library. Why would the 3 argument overload not be found? Below are the (beginnings of the ) related compiler errors. Thanks, Jeff ======================== C:\boost\boost_1_32_0\boost\serialization\split_free.hpp(55) : error C2780: 'void boost::archive::load(Archive &,T &)' : expects 2 arguments - 3 provided C:\boost\boost_1_32_0\boost\archive\detail\iserializer.hpp(514) : see declaration of 'boost::archive::load' C:\boost\boost_1_32_0\boost\serialization\split_free.hpp(54) : while compiling class-template member function 'void boost::serialization::free_loader<Archive,T>::invoke(Archive &,T &,const unsigned int)' with [ Archive=boost::archive::text_iarchive, T=std::set<std::string> ] .... ======================== C:\boost\boost_1_32_0\boost\serialization\split_free.hpp(55) : error C2780: 'void boost::archive::load(Archive &,T &)' : expects 2 arguments - 3 provided C:\boost\boost_1_32_0\boost\archive\detail\iserializer.hpp(514) : see declaration of 'boost::archive::load' C:\boost\boost_1_32_0\boost\serialization\split_free.hpp(54) : while compiling class-template member function 'void boost::serialization::free_loader<Archive,T>::invoke(Archive &,T &,const unsigned int)' with [ Archive=boost::archive::binary_iarchive, T=std::set<std::string> ] ....

1 0

[serialization] and macro 'max' compiler warning on VC71
by Jeff Flinn 22 Nov '04

22 Nov '04

I've just tried to move to 1.32 and get the following warning: C:\boost\boost_1_32_0\boost\archive\basic_binary_oprimitive.hpp(101) : warning C4003: not enough actual parameters for macro 'max' which points to: assert( static_cast<std::size_t>(std::numeric_limits<std::streamsize>::max()) >= count ); Any suggestions on avoiding this with an MFC based project? Thanks, Jeff

3 4

[assign] documentation - bugs in examples
by Anton Gutsunaev 22 Nov '04

22 Nov '04

Some examples in <boost>/libs/assign/doc/index.html file print "Assertion failed" message or cannot be compiled. <boost>/libs/assign/doc/index.html#operator+= vector<int> values; values += 1,2,3,4,5,6,7,8,9; // insert values at the end of the container BOOST_ASSERT( values.size() == 9 ); BOOST_ASSERT( values[0] == 1 ); BOOST_ASSERT( values[9] == 9 );// <---must be "values[8]" <boost>/libs/assign/doc/index.html#operator() map<string,int> months; insert( months ) ( "january", 31 )( "february", 28 ) ( "march", 31 )( "april", 30 ) ( "may", 31 )( "june", 30 ) ( "july", 31 )( "august", 31 ) ( "september", 30 )( "october", 31 ) ( "november", 30 )( "december", 31 ); BOOST_ASSERT( m.size() == 12 ); //<---change "m" to "months" BOOST_ASSERT( m["january"] == 31 ); //<---same here after words "If operator()() is too cumbersome to use with eg. push_front()we can also say": deque<int> di; push_front( di ) = 1,2,3,4,5,6,7,8,9; BOOST_ASSERT( di.size() == 9 ); BOOST_ASSERT( di[8] == 9 );//<-- must be di[8]==1 or di[0]==9 because of push_front <boost>/libs/assign/doc/index.html#list_of: const stack<string> names = list_of( "Mr. Foo" )( "Mr. Bar")( "Mrs. FooBar" ).to_adapter(); const stack<string> names2 = (list_of( "Mr. Foo" ), "Mr. Bar", "Mrs. FooBar" ).to_adapter(); BOOST_ASSERT( names.size() == 3 ); BOOST_ASSERT( names[0] == "Mr. Foo" ); //<---can't use operator [] with stack BOOST_ASSERT( names[2] == "Mrs. FooBar" ); //<---same here example after words "A more general list can be constructed with repeat_fun()": template< class T > struct next { T seed; next( T seed ) : seed(seed) { } T operator()() const //<---remove const or declare "T seed" as mutable { return seed++; } };

2 1

[TYPO] Assignment Library
by Javier Estrada 22 Nov '04

22 Nov '04

Under the Reference section, the sentence: Originally const references was used, but it lead to many problems with string-literals. Should read: Originally const references were used, but it led to many problems with string-literals.

2 1

Typo in Assignment Library documentation
by Javier Estrada 22 Nov '04

22 Nov '04

In http://www.boost.org/libs/assign/doc/index.html there is a typo under the Introduction section. The sentence: These two operators makes it possible to construct lists of values which are then copied into a container: Should read: These two operators make it possible to construct lists of values which are then copied into a container:

3 2

[thread] Compiler warnings: 1.32 release
by Jody Hagins 22 Nov '04

22 Nov '04

Compiler warnings, g++ 3.2... /home/jody/boost_1_32_0/libs/thread/src/recursive_mutex.cpp: In member function `boost::recursive_mutex::recursive_mutex()': /home/jody/boost_1_32_0/libs/thread/src/recursive_mutex.cpp:299: warning: unused variable `int res' /home/jody/boost_1_32_0/libs/thread/src/recursive_mutex.cpp: In member function `boost::recursive_try_mutex::recursive_try_mutex()': /home/jody/boost_1_32_0/libs/thread/src/recursive_mutex.cpp:455: warning: unused variable `int res' gcc-C++-action /home/jody/boost_1_32_0/bin/bin/boost/libs/thread/build/libboost_thread .so/gcc/release/shared-linkable-true/threading-multi/read_write_mutex.o /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `void boost::detail::thread::read_write_mutex_impl<Mutex>::do_read_lock() [with Mutex = boost::mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:943: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:101: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:943: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:114: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:943: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:127: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `void boost::detail::thread::read_write_mutex_impl<Mutex>::do_write_lock() [with Mutex = boost::mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:948: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:170: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:948: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:187: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:948: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:205: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `void boost::detail::thread::read_write_mutex_impl<Mutex>::do_promote_to_writ e_lock() [with Mutex = boost::mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:968: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:678: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `void boost::detail::thread::read_write_mutex_impl<Mutex>::do_read_lock() [with Mutex = boost::try_mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:983: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:101: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:983: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:114: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:983: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:127: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `void boost::detail::thread::read_write_mutex_impl<Mutex>::do_write_lock() [with Mutex = boost::try_mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:988: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:170: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:988: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:187: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:988: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:205: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `void boost::detail::thread::read_write_mutex_impl<Mutex>::do_promote_to_writ e_lock() [with Mutex = boost::try_mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1024: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:678: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `void boost::detail::thread::read_write_mutex_impl<Mutex>::do_read_lock() [with Mutex = boost::timed_mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1044: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:101: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1044: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:114: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1044: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:127: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `void boost::detail::thread::read_write_mutex_impl<Mutex>::do_write_lock() [with Mutex = boost::timed_mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1049: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:170: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1049: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:187: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1049: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:205: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `bool boost::detail::thread::read_write_mutex_impl<Mutex>::do_timed_read_lock (const boost::xtime&) [with Mutex = boost::timed_mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1075: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:353: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1075: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:371: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1075: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:389: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `bool boost::detail::thread::read_write_mutex_impl<Mutex>::do_timed_write_loc k(const boost::xtime&) [with Mutex = boost::timed_mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1080: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:469: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1080: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:491: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1080: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:514: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `void boost::detail::thread::read_write_mutex_impl<Mutex>::do_promote_to_writ e_lock() [with Mutex = boost::timed_mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1100: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:678: warning: unused variable `int loop_count' /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp: In member function `bool boost::detail::thread::read_write_mutex_impl<Mutex>::do_timed_promote_t o_write_lock(const boost::xtime&) [with Mutex = boost::timed_mutex]': /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:1110: instantiated from here /home/jody/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:770: warning: unused variable `int loop_count' gcc-C++-action /home/jody/boost_1_32_0/bin/bin/boost/libs/thread/build/libboost_thread .so/gcc/release/shared-linkable-true/threading-multi/thread.o

1 0

possible date-time documentation bug
by Pavol Droba 22 Nov '04

22 Nov '04

Hi, It seems that there is a bug in the date time documentation Documentation says this: " To use the alternate resolution (64 bit microsecond) the variable BOOST_DATE_TIME_POSIX_TIME_STD_CONFIG must be defined in the library users project files (ie Makefile, Jamfile, etc). This macro is not used by the Gregorian system and therefore has no effect when building the library." But in reality, the negation is actualy true. 64bit precision is used when this macro is NOT defined. In addition there is a slight problem with posix_time::microseconds() (and possibly with other similar function as well). Somewhere along the way, parameter is converted to long. This might cause some problems, since the resolution is larger (64bit). For instance time_duration::total_microseconds() returns 64bit integer. If the return value is used to initialize a duration of that lenght, overflow occurs. I'm using current cvs version of boost. Regards, Pavol

2 1

[Boost-bugs] [ boost-Support Requests-1071040 ] Static linking boost::thread, vc-7_1-stlport
by SourceForge.net 22 Nov '04

22 Nov '04

Support Requests item #1071040, was opened at 2004-11-22 07:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1071040&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Static linking boost::thread, vc-7_1-stlport Initial Comment: bjam -sTOOLS="vc-7_1-stlport" -sBUILD="<stlport-iostream>on" -sSTLPORT_PATH="D:\path" --with-thread stage When builded libboost_thread-vc71-mt-sgdp-1_32.lib contain ref: ??0thread@boost@@QAE@ABV?$function0@XV?$allocator@Vfunction_base@boost@@@_STL@@@1@@Z Is there any way to rebuild thread so libboost_thread-vc71-mt-sgdp-1_32.lib will contain ref: __imp_??0thread@boost@@QAE@ABV?$function0@XV?$allocator@Vfunction_base@boost@@@_STL@@@1@@Z (__imp_ added) ? Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1071040&group_… ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost.Build V2 logo wanted
by Vladimir Prus 22 Nov '04

22 Nov '04

Boost.Build V2 is in need of a good logo. The one used now on http://boost.org/boost-build2 is the C++ Boost logo, which is not accurate and confusing. I'd very appreciate any contribution! There's no requirements what should be on the logo, only two preferences: - vector format (or a very large bitmap file) - one version of logo should include "Boost.Build" text. Ideally, there would be two versions, with and without the text, but with the same graphical elements. Right at the moment we're also discussing new C++ logo. While it would be cool to have some common graphics elements, it's OK for Boost.Build logo to be completely different. Thanks in advance, Volodya

1 0