October 2009 - Boost - lists.boost.org

Preliminary submission: generic linear algebra algorithms library Boost LA
by Emil Dotchevski 23 Nov '09

23 Nov '09

I remember some past discussions on this mailing list about the need for similar library in Boost, so I hope it is OK to skip the interest query and request a preliminary review for Boost LA. Boost LA provides a set of generic linear algebra algorithms, primarily for working with vectors and matrices of static size. The library also defines vector and matrix data types, however it allows users to introduce their own types by specializing the vector_traits and matrix_traits templates. Documentation and source code available at http://www.revergestudios.com/boost-la, released under the Boost Software License. Thanks, Emil Dotchevski

9 25

[BGL] [variant] problem (and perhaps solution?) with strong_components.hpp and variant
by Nil Geisweiller 17 Nov '09

17 Nov '09

Hi, it seems the problem is indeed a conflict between the get function of variant.hpp and the get function of two_bit_color_map. After renaming get by getTEST in 1) two_bit_color_map.hpp line 61 2) breadth_first_search.hpp line 78 3) property_map.hpp line 164 the compiling error has disappeared. Of course it is certainly not the right way to fix that bug, maybe wrapping two_bit_color_map get (and alike) function name under some namespace... but I'm not confident enough to take such decision. Maybe there is a better way. Please if someone is more knowledgeable could help me fix that bug. Thanks for your help Nil On Tue, Oct 27, 2009 at 7:31 AM, Nil Geisweiller <ngeiswei(a)googlemail.com> wrote: > Hi, > > I resend that email with the right title header. > > ---------- Forwarded message ---------- > From: Nil Geisweiller <ngeiswei(a)googlemail.com> > Date: Sun, Oct 25, 2009 at 6:11 PM > Subject: [Graph] problem with strong_components.hpp and variant > To: boost(a)lists.boost.org > > > Hi, > > it seems there is a conflict between strong_components.hpp and > variant, maybe the method boost::get is wrongly overloaded. > > The problem occurs with 1.40 but not with 1.37, and it is still occurs > with the last svn. > > I attach a minimal code to reproduce the bug + compile error > > ###### > test.cpp > ###### > > //uncomment the line below to get the bug > #include <boost/graph/strong_components.hpp> > #include <boost/variant.hpp> > > typedef boost::variant < int, float > intorfloat; > > int main() { > int i(2); > intorfloat iof(i); > return boost::get<int>(iof); //problem is here > } > > ########### > compile error > ########### > > a-lin@a-lin-desktop:~/OpenCog/test/bin$ make > [100%] Building CXX object CMakeFiles/test.dir/test.cpp.o > In file included from /usr/include/boost/graph/graph_concepts.hpp:17, > from /usr/include/boost/graph/depth_first_search.hpp:18, > from /usr/include/boost/graph/strong_components.hpp:17, > from /home/a-lin/OpenCog/test/test.cpp:2: > /usr/include/boost/property_map/property_map.hpp: In instantiation of > ‘boost::property_traits<int>’: > /usr/include/boost/graph/two_bit_color_map.hpp:46: instantiated from > ‘boost::two_bit_color_map<int>’ > /home/a-lin/OpenCog/test/test.cpp:10: instantiated from here > /usr/include/boost/property_map/property_map.hpp:31: error: ‘int’ is > not a class, struct, or union type > /usr/include/boost/property_map/property_map.hpp:32: error: ‘int’ is > not a class, struct, or union type > /usr/include/boost/property_map/property_map.hpp:33: error: ‘int’ is > not a class, struct, or union type > /usr/include/boost/property_map/property_map.hpp:34: error: ‘int’ is > not a class, struct, or union type > make[2]: *** [CMakeFiles/test.dir/test.cpp.o] Error 1 > make[1]: *** [CMakeFiles/test.dir/all] Error 2 > make: *** [all] Error 2 > > Is it a bug? Thanks a lot! > Nil >

4 5

[move][container] Review Request (new versions of Boost.Move and Boost.Container in sandbox and vault)
by Ion Gaztañaga 17 Nov '09

17 Nov '09

Hi to all, I've just uploaded to boost sandbox... http://svn.boost.org/svn/boost/sandbox/move/) and Boost.Vault... http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost.… ...new versions of libraries Boost.Move and Boost.Container. Online documentation can be found here: Boost.Move http://svn.boost.org/svn/boost/sandbox/move/libs/move/doc/html/index.html Boost.Container http://svn.boost.org/svn/boost/sandbox/move/libs/container/doc/html/index.h… I would like to request a review for both libraries. Boost.Move is quite small (just one header). Boost.Container depends on Boost.Move and Boost.Intrusive so you must download also the post-1.40 version of Intrusive placed in the same package (Boost.Container uses new features from Intrusive not included in Boost 1.40). Just take fresh Boost 1.39 folder and overwrite it with package contents. ************************ What's new in Boost.Move: ************************ ->The library has been modified to support moving rvalues of copyable AND movable types, a limitation of the previous version. This changes where proposed by Klaus Triendl in this thread: http://lists.boost.org/Archives/boost/2009/06/153266.php The library has now new macros to declare copyable and movable types and movable only types. Old macros are still there for backwards compatibility (specially unordered library which was also ported to this move sandbox) but I expect to remove them if current approach is considered better. ->Updated documentation and tests. ************************ What's new in Boost.Container: ************************ -> Added tests and documentation -> Updated the library to the new Boost.Move macros * * * I've tested both libraries in Windows XP using the following compilers: Visual 7.1, Visual 8.0, Visual 9.0, Intel 10.0, Mingw-gcc 4.3 and Mingw-gcc 4.3 in C++0x mode. The library should work on any C++03 conforming compiler Best, Ion

19 95

[Locale] Boost.Locale - preliminary code
by Artyom 16 Nov '09

16 Nov '09

Hello, I'm working on Boost.Locale project. Source code and some basic examples can be found here: https://cppcms.svn.sourceforge.net/svnroot/cppcms/boost_locale/trunk/ It still lacks of documentation and some features. It is mostly tested under Linux gcc-4.3 and it seems to work under MSVC-9 (however I had less tested it). General description: ==================== Boost.Locale is a library that brings high quality localization facilities in C++ way. It uses `std::locale`, and `std::locale` facets in order to pro- vide localization in transparent and C++ aware way to user. C++ has quite good base for localization via existing C++ locale facets: `std::num_put`, `std::ctype`, `std::collate` etc.. But they are very limited and sometimes buggy by design. The support of localization varies between different operating systems and incompatible between them. On the other hand, there is great, well debugged, high quality, widely used ICU library that gives all of the goodies but, it has very old API that mimics Java behavior, it is completely ignores STL and provides useful API only for UTF-16 encoded text, ignoring other popular Unicode encodings like UTF-8 and UTF-16, or limited national character sets like Latin1. Boost.Locale provides the natural glue between C++ locales framework, iostreams and powerful ICU library in following areas: - Correct case conversion, case folding and normalization (DONE) - Collation including support of 4 Unicode collation levels. (DONE) - Date and time formatting and parsing including support of timezones and calendars other then Gregorian. (DONE) - Number formatting, spelling and parsing (DONE) - Monetary formatting and parsing (DONE) - Powerful message formatting including support plural forms, using GNU catalogs. (DONE) - Character, word, sentence and line-break boundary analysis. (TODO) - Support of 8-bit character sets like Latin1 and UTF-8 encoded text. (DONE) - Support of `char`, `wchar_t` and C++0x `char16_t`, `char32_t` strings and streams. (DONE) ------------------------------------------------------------ FYI, It is still work in progress but 90% of the job is done. Please take a look on it --- especially experts in Windows programming. I would glad if someone explains me the process of submission and what should be done for it. I know that it is not yet Boost ready but it goes fast in this direction. Best, Artyom.

4 5

[mirror] C++0x version of the reflection library available
by Matus Chochlik 14 Nov '09

14 Nov '09

Dear list, I would like to announce that a new (alpha) version of the Mirror reflection library, re-written nearly completely from scratch in C++0x, is available at sourceforge.net for those interested, the code can be checked out from the SF repository: https://mirror-lib.svn.sourceforge.net/svnroot/mirror-lib/trunk/impl documentation pre-built with doxygen and DOT is available here: http://kifri.fri.uniza.sk/~chochlik/mirror-lib/html/ Based on a year and a half of user experience with the previous version (the one in Boost sandbox) there have been made several important changes. Just to mention a few: - The meta-objects should be more consistent with the base-level language - There is a run-time layer with an run-time interface very similar to the compile-time interface - Meta-object categories for tag dispatching have been added - "Local" names having parts of the nested name specifier stripped away if the Mirror's "using namespace" directive is used on the current (or parent) scope - C++0x features are extensively used to make things more straightforward - etc. This version does not yet implement all features from the previous version, like inherited class members, visitor-based traversals, meta-constructors and factory generators. These will be added in the near future. The library has been tested only with gcc (version 4.5.0 20091010) so I would be glad to hear about experiences with other compilers supporting C++0x. I would also appreciate any feedback, suggestions or other contributions. best regards, Matus

2 3

Boost.Variant is not EqualityComparable
by brook＠biology.nmsu.edu 12 Nov '09

12 Nov '09

I just ran into the case that Boost Variant does not satisfy the EqualityComparable concept. While it provides operator==() and operator<() (and therefore is LessThanComparable), it does not provide operator!=(), which is required for the EqualityComparable concept. Is this by design or oversight? It seems reasonable to expect that a Boost Variant model this concept, but perhaps I am missing something. In case it is by oversight, the following patch seems to provide the missing operator. Cheers, Brook --- boost/variant/variant.hpp.orig 2009-05-13 21:21:59.000000000 -0600 +++ boost/variant/variant.hpp 2009-05-25 19:21:40.000000000 -0600 @@ -1681,6 +1681,8 @@ return rhs.apply_visitor(visitor); } + bool operator!=(const variant& rhs) const { return !(*this == rhs); } + bool operator<(const variant& rhs) const { //

6 7

[BGL] Trying to get a correclty working Parallel BFS code
by Sandeep Gupta 11 Nov '09

11 Nov '09

Hi All, I have spent significant effort on parallel bfs. Currently its almost working. I would really appreciate some help to get it running correctly. I have attached the code (self contained and requires no input file). I think I have followed all the guidelines regarding distributed property maps mentioned in the docs ( http://www.osl.iu.edu/research/pbgl/documentation/graph/breadth_first_searc… ). I am out of ideas of where things can could have gone wrong. The correct output of input graph 0 --> 1 2 1 --> 2 3 2 --> 3 3 --> 4 6 4 --> 5 5 --> 6 --> should be Node ID : Level 0 : 0 1 : 1 2 : 1 3 : 2 4 : 3 5 : 4 6 : 3 But when ran with 2 processes the output comes out to be Node ID : Level 0 : 0 1 : 1 2 : 1 3 : 2 4 : 3 5 : 4294967295 6 : 3 Not sure why this is happening. Any suggestions or pointers would indeed be quite appreciated. Thanks for your time. -Sandeep

3 23

proposal interval container; ITL moved to the boost sandbox
by Joachim Faulhaber 11 Nov '09

11 Nov '09

Dear boosters, after completion of a lot of boostification work I moved my Interval Template Library to the boost sandbox in the boost project centric form: https://svn.boost.org/trac/boost/browser/sandbox/itl itl boost itl [itl_xt] [validate] libs itl [itl_xt] [validate] I have split up the original library into three parts: (1) itl, (2) itl_xt and (3) validate. Core part 1 'ITL' contains all interval container class templates. Only this part will be prepared for a formal submission. Part 2 'itl_xt' contains extended parts of the original library that do not belong to the core interval container data structures and might be proposed for later extensions. Part 3 'validate' contains the sources for the law based test automaton 'LaBatea' that has been used for an automated check of the ITLs correctness. Parts 2 and 3 do not yet conform boost standards and naming conventions and are not yet intended as contributions to boost. On the core ITL-part I have done the following: + Removed all virtual functions via introduction of mixins + Integrated deeper into boost libraries replacing own code by e.g. boost::type_traits and boost::mpl + Minimized the class template interfaces by transforming member functions into non member function templates. + Made interval containers more interoperable by overloading operators and global function templates. + Wrote a test suite using boost unit test tools. Tested for boost-instance types boost::date_time and boost::rational + Provided jamfiles to build and run examples and tests. + All examples and tests have been compiled, linked and run successfully with msvc_9.0 and gcc_3.4.4(cygwin). Next I am going to write boost style html-documentation. >From the boost web page I don't see a clear recommendation for a preferable way of doing that. Handcoded? Generated with BoostBook? Is there a reference library that has an exemplary standard documentation? Cheers Joachim

3 4

Time for another bug sprint (after 1.41 ships)?
by Marshall Clow 09 Nov '09

09 Nov '09

Earlier this year, we had a "bug sprint", where many people focused on fixing bugs in Boost. We managed to get the # of open tickets down from 800 to about 720. As of today, there are 820 open tickets in Trac. Is it time to focus on swotting bugs again? 1.41 is scheduled for release on 1-November; that's six weeks from yesterday. How about a bug sprint starting on 14-November, finishing on 22- November? That's two weekends - and finishes up before the American Thanksgiving holiday. -- Marshall P.S. This doesn't mean that people have to wait until November to fix bugs ;-) ;-)

12 25

[function] "paranoia" vs efficiency
by Domagoj Saric 09 Nov '09

09 Nov '09

As far as I can see boost::function<>::operator() performs: if (this->empty()) boost::throw_exception(bad_function_call()); before invoking the stored function (object)... My question is why or why only this "checked"/"safe" approach/method of invocation exists? Because this: - causes (extra) code branching - causes the compiler to insert exception throwing and handling code in surrounding/calling code (which need not otherwise be if the function stored in the boost function instance is itself nothrow) - inserts a call to the bad_function_call constructor - disables the compiler from inlining the function (MSVC atleast) - disables NVRO (MSVC atleast, http://msdn.microsoft.com/en-us/library/ms364057(VS.80).aspx#nrvo_cpp05_top… ) while at the same time I would most often consider calling a "null-function-pointer" a programmer error (that would therefor need to be "handled" with an assert not an exception), not a runtime 'unpredictable' exception... ...IMO the default should be not to include this check (i.e. use an assert) and provide a safeInvoke() type of method for those users and cases that actually require/want this type of check/behaviour... ...or atleast "it would be welcomed" if a non-checking unsafeInvoke() type of method would be provided for those that are 'sure' that the boost::function<> object is valid (for example in the line before i've just performed the same check to decide whether to call the function object or not)... -- "That men do not learn very much from the lessons of history is the most important of all the lessons of history." Aldous Huxley

8 18