- Boost - lists.boost.org

[move] Declarations of the copy constructor and copy-assign operator produced by BOOST_MOVABLE_BUT_NOT_COPYABLE
by Joseph Trebbien 15 Apr '11

15 Apr '11

Looking through the sources of Boost.Move in trunk, I am wondering about a couple of lines in <boost/move/move.hpp> that are part of the expansion of BOOST_MOVABLE_BUT_NOT_COPYABLE when BOOST_NO_RVALUE_REFERENCES is defined: #define BOOST_MOVABLE_BUT_NOT_COPYABLE(TYPE)\ private:\ TYPE(TYPE &);\ TYPE& operator=(TYPE &);\ public:\ operator ::boost::rv<TYPE>&() \ { return *static_cast< ::boost::rv<TYPE>* >(this); }\ operator const ::boost::rv<TYPE>&() const \ { return *static_cast<const ::boost::rv<TYPE>* >(this); }\ private:\ // Why do the declarations of the copy constructor and copy-assign operator overload not take a const-reference to TYPE? When BOOST_NO_RVALUE_REFERENCES is not defined, they do: #define BOOST_MOVABLE_BUT_NOT_COPYABLE(TYPE)\ public:\ typedef int boost_move_emulation_t;\ private:\ TYPE(const TYPE &);\ TYPE& operator=(const TYPE &);\ // Joseph Trebbien

2 1

[chrono] Compiler errors for mpl/abs.hpp
by lcaminiti 14 Apr '11

14 Apr '11

Hello all, I am trying to compile the example below on MSVC using Boost.Chrono (headers-only) from the sandbox but I am getting some compiler errors. What am I doing wrong? Thank you very much. --Lorenzo #define BOOST_CHRONO_INLINED #include <boost/chrono.hpp> #include <boost/spirit/include/phoenix.hpp> #include #include #include #include #include int main(int argc, char* argv[]) { assert(argc == 2); unsigned long n = sqrt(double(atol(argv[1]))); using boost::phoenix::ref; using boost::phoenix::arg_names::_1; double sum = 0.0; int factor = 1; std::vector v(n); std::fill(v.begin(), v.end(), 1.0); boost::chrono::duration sec; for (unsigned long i = 0; i < n; ++i) { boost::chrono::system_clock::time_point start = boost::chrono::system_clock::now(); std::for_each(v.begin(), v.end(), ( ref(sum) += factor * _1 )); sec += boost::chrono::system_clock::now() - start; } std::cout << sec.count() << std::endl; assert(sum == n * n); return 0; } E:\sandbox\boost-sandbox-local\libs\local\example>cl /EHs /Ox /I..\..\.. /I"c:\P rogram Files\boost\boost_1_46_1" /I..\..\..\..\boost-sandbox-chrono.x benchmark_ boost_phoenix.cpp Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for 80x86 Copyright (C) Microsoft Corporation. All rights reserved. benchmark_boost_phoenix.cpp ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : error C2143: syntax e rror : missing ',' before ')' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(75) : see reference to class template instantiation 'boost::mpl::abs_impl::apply' being compiled ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : error C2059: syntax e rror : ')' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(74) : error C2143: syntax e rror : missing ';' before '{' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(75) : error C2143: syntax e rror : missing ';' before '}' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : error C2143: syntax e rror : missing ';' before '}' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : fatal error C1004: un expected end-of-file found -- View this message in context: http://boost.2283326.n4.nabble.com/boost-chrono-Compiler-errors-for-mpl-abs… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

[locale] trouble building
by Noah Roberts 14 Apr '11

14 Apr '11

I grabbed the ICU bin for VS2010. I extracted the content into d:\icu so that d:\icu\include has the various includes. I set up the PATH variable to include d:\icu\bin... I copied boost and lib from the review into boost_1_46_1 where the root of boost source is. The docs seem to imply that I can get a build without ICU if I'm using Windows but this doesn't seem to be the case. I tried --without-icu and I got an error about using --with and --without for the same lib. Here's my attempt to build (with ICU installed): D:\boost_1_46_1\boost_1_46_1>bjam --build-dir=.\build toolset=msvc-10 --with-loc ale --prefix=d:\boost_msvc_1461 --layout=system -sICU_PATH=d:\icu stage Performing configuration checks - iconv (libc) : no - iconv (separate) : no - icu : no D:/boost_1_46_1/boost_1_46_1/tools/build/v2/build\virtual-target.jam:1079: in vi rtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <pstage\lib>libboost_locale.lib error: previous virtual target { common%common.copy-libboost_locale.lib.STATIC_L IB { msvc%msvc.archive-libboost_locale.lib.STATIC_LIB { msvc%msvc.compile.c++-en coding\codepage.obj.OBJ { encoding/codepage.cpp.CPP } } { msvc%msvc.compile.c++- shared\date_time.obj.OBJ { shared/date_time.cpp.CPP } } { msvc%msvc.compile.c++- shared\format.obj.OBJ { shared/format.cpp.CPP } } { msvc%msvc.compile.c++-shared \formatting.obj.OBJ { shared/formatting.cpp.CPP } } { msvc%msvc.compile.c++-shar ed\generator.obj.OBJ { shared/generator.cpp.CPP } } { msvc%msvc.compile.c++-shar ed\ids.obj.OBJ { shared/ids.cpp.CPP } } { msvc%msvc.compile.c++-shared\localizat ion_backend.obj.OBJ { shared/localization_backend.cpp.CPP } } { msvc%msvc.compil e.c++-shared\message.obj.OBJ { shared/message.cpp.CPP } } { msvc%msvc.compile.c+ +-shared\mo_lambda.obj.OBJ { shared/mo_lambda.cpp.CPP } } { msvc%msvc.compile.c+ +-util\codecvt_converter.obj.OBJ { util/codecvt_converter.cpp.CPP } } { msvc%msv c.compile.c++-util\default_locale.obj.OBJ { util/default_locale.cpp.CPP } } { ms vc%msvc.compile.c++-util\info.obj.OBJ { util/info.cpp.CPP } } { msvc%msvc.compil e.c++-util\locale_data.obj.OBJ { util/locale_data.cpp.CPP } } { msvc%msvc.compil e.c++-std\codecvt.obj.OBJ { std/codecvt.cpp.CPP } } { msvc%msvc.compile.c++-std\ collate.obj.OBJ { std/collate.cpp.CPP } } { msvc%msvc.compile.c++-std\converter. obj.OBJ { std/converter.cpp.CPP } } { msvc%msvc.compile.c++-std\numeric.obj.OBJ { std/numeric.cpp.CPP } } { msvc%msvc.compile.c++-std\std_backend.obj.OBJ { std/ std_backend.cpp.CPP } } { msvc%msvc.compile.c++-util\gregorian.obj.OBJ { util/gr egorian.cpp.CPP } } { msvc%msvc.compile.c++-win32\collate.obj.OBJ { win32/collat e.cpp.CPP } } { msvc%msvc.compile.c++-win32\converter.obj.OBJ { win32/converter. cpp.CPP } } { msvc%msvc.compile.c++-win32\lcid.obj.OBJ { win32/lcid.cpp.CPP } } { msvc%msvc.compile.c++-win32\numeric.obj.OBJ { win32/numeric.cpp.CPP } } { msvc %msvc.compile.c++-win32\win_backend.obj.OBJ { win32/win_backend.cpp.CPP } } } } error: created from ./stage-proper error: another virtual target { common%common.copy-libboost_locale.lib.STATIC_LI B { msvc%msvc.archive-libboost_locale.lib.STATIC_LIB { msvc%msvc.compile.c++-enc oding\codepage.obj.OBJ { encoding/codepage.cpp.CPP } } { msvc%msvc.compile.c++-s hared\date_time.obj.OBJ { shared/date_time.cpp.CPP } } { msvc%msvc.compile.c++-s hared\format.obj.OBJ { shared/format.cpp.CPP } } { msvc%msvc.compile.c++-shared\ formatting.obj.OBJ { shared/formatting.cpp.CPP } } { msvc%msvc.compile.c++-share d\generator.obj.OBJ { shared/generator.cpp.CPP } } { msvc%msvc.compile.c++-share d\ids.obj.OBJ { shared/ids.cpp.CPP } } { msvc%msvc.compile.c++-shared\localizati on_backend.obj.OBJ { shared/localization_backend.cpp.CPP } } { msvc%msvc.compile .c++-shared\message.obj.OBJ { shared/message.cpp.CPP } } { msvc%msvc.compile.c++ -shared\mo_lambda.obj.OBJ { shared/mo_lambda.cpp.CPP } } { msvc%msvc.compile.c++ -util\codecvt_converter.obj.OBJ { util/codecvt_converter.cpp.CPP } } { msvc%msvc .compile.c++-util\default_locale.obj.OBJ { util/default_locale.cpp.CPP } } { msv c%msvc.compile.c++-util\info.obj.OBJ { util/info.cpp.CPP } } { msvc%msvc.compile .c++-util\locale_data.obj.OBJ { util/locale_data.cpp.CPP } } { msvc%msvc.compile .c++-std\codecvt.obj.OBJ { std/codecvt.cpp.CPP } } { msvc%msvc.compile.c++-std\c ollate.obj.OBJ { std/collate.cpp.CPP } } { msvc%msvc.compile.c++-std\converter.o bj.OBJ { std/converter.cpp.CPP } } { msvc%msvc.compile.c++-std\numeric.obj.OBJ { std/numeric.cpp.CPP } } { msvc%msvc.compile.c++-std\std_backend.obj.OBJ { std/s td_backend.cpp.CPP } } { msvc%msvc.compile.c++-util\gregorian.obj.OBJ { util/gre gorian.cpp.CPP } } { msvc%msvc.compile.c++-win32\collate.obj.OBJ { win32/collate .cpp.CPP } } { msvc%msvc.compile.c++-win32\converter.obj.OBJ { win32/converter.c pp.CPP } } { msvc%msvc.compile.c++-win32\lcid.obj.OBJ { win32/lcid.cpp.CPP } } { msvc%msvc.compile.c++-win32\numeric.obj.OBJ { win32/numeric.cpp.CPP } } { msvc% msvc.compile.c++-win32\win_backend.obj.OBJ { win32/win_backend.cpp.CPP } } } } error: created from ./stage-proper error: added properties: <debug-symbols>on <inlining>off <optimization>off <runt ime-debugging>on <variant>debug error: removed properties: <debug-symbols>off <define>NDEBUG <inlining>full <opt imization>speed <runtime-debugging>off <variant>release D:/boost_1_46_1/boost_1_46_1/tools/build/v2/build\virtual-target.jam:490: in act ualize-no-scanner from module object(file-target)@962 D:/boost_1_46_1/boost_1_46_1/tools/build/v2/build\virtual-target.jam:135: in obj ect(file-target)(a)962.actualize from module object(file-target)@962 D:/boost_1_46_1/boost_1_46_1/tools/build/v2\build-system.jam:748: in load from m odule build-system D:\boost_1_46_1\boost_1_46_1\tools\build\v2/kernel\modules.jam:283: in import fr om module modules D:\boost_1_46_1\boost_1_46_1\tools\build\v2\kernel\bootstrap.jam:142: in boost-b uild from module D:\boost_1_46_1\boost_1_46_1\boost-build.jam:17: in module scope from module D:\boost_1_46_1\boost_1_46_1> Any ideas?

3 3

[Boost.Pool] TR1?
by Phil Bouchard 14 Apr '11

14 Apr '11

Greetings, I see the Boost.Pool is not making its way up to the C++ standards yet an it is very unfortunate given its great use. Boost.Pool provides an is_from() member function that does a simple range check and returns whether a pointer is part of the pool or not. This is a very useful function which I think should be part of the standards because it could be used for the global pool as well; i.e. the one used by operator ::new and ::delete. The benefits outweigh the costs. Thanks, -Phil

8 49

[Parallel BGL] Property access problem
by Cosimo Calabrese 14 Apr '11

14 Apr '11

Hi to all, I'm working on a WinXP, VS2010, boost 1.46.1, openMPI 1.4.3. I've used in the past the BGL lib, and now I would explore the PBGL extension. I've writed a simple program (you can find it in attach), but I've some problem. When I run it with: mpirun -np 1 .\test.exe it works. But if I use 2 or 4 processors the program crash sistematically in the following way, on different machines too: num_vertices: 10 num_edges: 19 A-->B : 1 A-->C : 10 A-->D : 11 B-->D : 13 C-->D : 12 B-->E : 1 C-->A : 14 E-->D : 1 D-->B : 15 D-->A : 1 E-->B : 16 -------------------------------------------------------------------------- Sorry! You were supposed to get help about: odls-default:could-not-kill But I couldn't open the help file: D:\dev\CommesseAperte\Sviluppo\TELLUSXX_CalcServer\lib\openmpi\installed\share\openmpi\help-odls-default.txt: No such file or directory. Sorry! -------------------------------------------------------------------------- Every process allocates 1 GB. The problem disappear only when I eliminate all the property access (get() and put()). Maybe I access to the MPI framework for the first time during the property access, and so could be an MPI problem? Am I using the property in a wrong way? Thanks in advance, Cosimo Calabrese.

1 1

New, powerful way to use enable_if in C++0x
by Matt Calabrese 13 Apr '11

13 Apr '11

I'm not sure if there is much interest in this or if someone else discovered this as well, but I realized today that enable_if can be used in a new way in C++0x. Traditionally when working with enable_if with function templates you invoke it either in the return type or in an additional function parameter of the function. Each of these has advantages and disadvantages. The parameter form has the downside of augmenting the parameter list. The most notable problems with this approach are that it can't be used with overloaded operators that require a fixed number of arguments, and it can't be used after a variadic argument list. The return type use of enable_if is often preferred since it does not involve augmenting the parameter list, meaning that it can be used with most overloaded operators, but you still can't use it for conversion operations and you can't use it all with constructors as they have no explicit return type. However, in C++0x, there is a new way to use enable_if by altering neither the function parameter list nor the specification of the return type. It can be used with operators, constructors, variadic function templates, and even overloaded conversion operations (the latter of which was previously considered impossible). The way to do it is with C++0x default function template parameters. Rather than try to explain any further in English, the following code should demonstrate the approach fairly clearly (tested in GCC 4.5.2): http://codepaste.net/23yo8o There is only one drawback that I can think of off of the top of my head -- you can't refer to the function parameters by name for the enable_if condition, whereas in C++0x if you use the return type form of enable_if along with the new trailing return type form of function declarations you can. I have never personally wanted to do this and I highly doubt that it's common so this is likely entirely a non-issue, plus you can always use std::declval anyway so you aren't actually losing any high-level functionality. Are there any thoughts on this or drawbacks other than what I mentioned? Should such use be added to the docs as supported behavior in 0x compilers? -- -Matt Calabrese

16 34

[config] Local classes as template parameters
by Lorenzo Caminiti 13 Apr '11

13 Apr '11

On Sat, Feb 12, 2011 at 5:50 AM, John Bytheway <jbytheway+boost(a)gmail.com> wrote: > On 11/02/11 22:29, Lorenzo Caminiti wrote: >> On Fri, Feb 11, 2011 at 4:31 PM, Lorenzo Caminiti <lorcaminiti(a)gmail.com> wrote: >>> From: John Bytheway <jbytheway+boost(a)gmail.com> >>> 2. Might anyone care so much about performance that they absolutely must >>> have the code inlined? The answer is probably "yes" (or at least there >>> will be people who *think* they care, which is also a problem). For >>> these people you could, if you choose, provide an alternate >>> implementation which doesn't indirect through local::function<>, and >>> thus will only work in C++0x (or C++03 with non-standard extensions). >> >> Without inheriting from local::function_base<> and then using >> local::function_ref<> the local struct cannot be passed as a template >> parameter in C++. Is this different for C++0x (C++03)? > > Yes, in C++0x local structs can be passed as template parameters. > Obviously, in C++0x there are lambdas too, so you might think your > library is useless, but I'd expect most compilers to support passing > local structs as template parameters before they support lambdas, so > there is some advantage in having this intermediate implementation. > Also, your macros would allow writing code that worked in C++0x and > C++03, with the virtual function business in only those compilers/modes > where it is necessary. Hello all, Is there a Boost.Config macro that indicates if the compiler allows local classes to be passed as template parameters? Thank you. -- Lorenzo

3 2

[GSoC] Boost.Tree and Boost.BloomFilter
by Alejandro Cabrera 13 Apr '11

13 Apr '11

Hello all, I've filed two proposals for this Google Summer of Code. Boost.Tree: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/cppcabre… <http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/cppcabre…> Boost.BloomFilter: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/cppcabre… I'd be glad to work on either project. Feedback is welcome. Thanks, -Alej

3 5

Installation fails if env VMS is set
by Dreamcat4 12 Apr '11

12 Apr '11

Hi, Over on the Boost-Users mailinglist we have found that this environment variable (and perhaps unknown but maybe others) will cause bootstrap.sh / Jam failure during the Boost libraries compile and install. Heres the full thread: http://lists.boost.org/boost-users/2011/04/67716.php You (or Jam developement team) may wish to consider taking some kind of action to avoid this as VMS is a very common acronym for "Virtual Machines". Its usage elsewhere is widespread and certainly not Boost-specific. Other choices of course - maybe look towards documenting such usag(es) if they cannot be easily avoided. Or consider ways to detect / warn / clean out the users shell environment variables if they are conflicting. Sorry I cant help any further however as a new user I simply have no experience with the Boost library yet. Many thanks. dreamcat4 dreamcat4(a)gmail.com

2 4

[GSOC]SIMD Library
by Faiçal Tchirou 12 Apr '11

12 Apr '11

Hi everyone, I recently ask documentation about the SIMD Library project here and I receive some guides and references links from Joel Falcou. Now I have some questions about the library itself. Is the goal of the project to build a library similar to libSIMDx86 but more focusing on the AltiVec instruction set ? Joel also advises me to take a look at Proto. I read that Proto is used to build DSEL. Will Proto be used to map high level classes and methods of the library to native SIMD instructions ? What about the library itself ? Which modules have to be developped ? Thanks.

8 37