- Boost - lists.preview.boost.org

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

gcc4 not recognized
by Neal D. Becker 22 Nov '04

22 Nov '04

Attempting to use boost with gcc4 says version not recognized. I ran configure. BTW, configure should be chmod +x. Here is the result:

2 1

[Review] Named Parameters library (ongoing)
by Doug Gregor 22 Nov '04

22 Nov '04

Today is the last day of the review of the Named Parameters library by David Abrahams and Daniel Wallin. Let's hear some more comments! The original announcement follows: The Named Parameters library provides a framework for writing functions that can accept arguments by name or by position. The use of named parameters can improve the readability of calls to these functions, especially when the functions have many parameters with default values. The Named Parameters library allows one to write a new_window function that allows a call such as: window* w = new_window("alert2", movable = true); The library is available in the Boost sandbox here: boost/named_params.hpp libs/utility And in the files area (login required): http://groups.yahoo.com/group/boost/files/named_params.zip Reviewers may wish to compare this solution to the named parameters already used by the Boost Graph Library, documented here: http://www.boost.org/libs/graph/doc/bgl_named_params.html Please send your reviews either to the Boost list or to me personally. The former is preferred, because it allows the community to consider your review as well. When writing your review, you may wish to consider the following questions (from http://www.boost.org/more/formal_review_process.htm#Comments) - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? As always, please remember to clearly state whether you believe the library should be accepted into Boost. Thank you Doug Gregor Review Manager, Named Parameters library

1 0

[patch] [shared_ptr] out-of-date comment
by Jonathan Wakely 22 Nov '04

22 Nov '04

The attached patch removes an old comment from shared_count.hpp that refers to initial_use_count and initial_weak_count. Those parameters were removed from the constructor a while ago. jon -- "Whenever you find that you are on the side of the majority, it is time to reform." - Mark Twain

2 1

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

22 Nov '04

Under the Motivation section, the sentence: Please note: the intent is not to fix the known defaults of std::min and std::max, but to add one more algorithms that combines both; Should read: Please note: the intent is not to fix the known defaults of std::min and std::max, but to add one more algorithm that combines both;

2 1

shared_ptr and serialization
by Robert Ramey 22 Nov '04

22 Nov '04

Would it be possible to add something like friend template<class Archive> boost::serialization::serialize(Archive &ar, T &t); to boost::shared_ptr ? This would let me remove a problematic hack in boost/serialization/shared_ptr which is creating a headache when shared_ptr serialization is used with some other headers. The same may be necessary for some other headers - e.g. weak ptr. Another alternative would be to change the private members to protected or maybe even public. I realize that this creates a dependency between boost::serialization and boost:: shared_ptr that you have hoped to avoid. But until this is resolved at another level, its would be better than the current situation. Alternatively, you might want to consider expanding the shared_ptr interface with enough information to permit serialization to be implemented via the public interface. This has worked well for the stl collections. I don't know if this was an intentional design decision or just an accident. We really need a real solution now for boost::shared_ptr / boost::serialization . Robert Ramey

9 33