- Boost-users - lists.preview.boost.org

UTF: test/included/unit_test.hpp vs test/unit_test.hpp
by Manav Bhatia 15 May '17

15 May '17

Hi, I am using the UTF in my code. Below is the key component of my code that I have been using on Mac for a few years with boost installed from macports. #define BOOST_TEST_DYN_LINK #define BOOST_TEST_MODULE MAST_TESTS #include <boost/test/unit_test.hpp> // C++ includes #include <memory> struct GlobalTestFixture { GlobalTestFixture() { /* my code here */ } ~GlobalTestFixture() { } }; BOOST_GLOBAL_FIXTURE( GlobalTestFixture ); A few days ago I started using this code on Ubuntu and kept getting segmentation faults with random values being returned for boost::unit_test::framework::master_test_suite().argc I managed to get rid of this problem by changing the included header to #include <boost/test/included/unit_test.hpp> I have seen the description here: http://www.boost.org/doc/libs/1_48_0/libs/test/doc/html/utf/compilation/dir… <http://www.boost.org/doc/libs/1_48_0/libs/test/doc/html/utf/compilation/dir…>. However, I am not quite able to follow why this problem occurred on Ubuntu (with system boost library) when I was still linking against the precompiled library (version 1.58). Is there a test I can include in my code to automatically switch from one include to the other? I will appreciate some guidance. Regards, Manav

3 2

Test: Skip test from fixture
by Florian Lindner 15 May '17

15 May '17

Hello, given I have a test with a fixture. How can I skip that test from within the fixture? Thanks, Florian

2 1

(no subject)
by Daniel Estermann 14 May '17

14 May '17

Hello everybody, I am trying to build HPX (https://github.com/STEllAR-GROUP/hpx) which uses Boost under Cygwin and I bumped into an incompatibility issue between the class boost::asio::detail::winsock_init_base and the WinSocket-API exposed by Cygwin. The error summary: the types of variable members in winsock_init_base::data are long (defined in boost/asio/detail/winsock_init.hpp). These variable are passed to functions _InterlockedIncrement, _InterlockedExchange etc (called from boost/asio/detail/impl/winsock_init.ipp). But there are no functions defined in Cygwin (in headers in /usr/include/w32api) expecting a long parameter. Here you can see the full gcc output: https://pastebin.com/raw/8MDa8QXJ I also produced the the preprocessor output which I zipped and uploaded to https://www.dropbox.com/s/anmjsjnvq7lnesr/hpx_init.cpp.i.zip?dl=0 Am I overlooking anything or is this really an incompatibility issue?

1 0

Context and coroutine for ARM
by Daniel Estermann 14 May '17

14 May '17

I am trying to cross compile boost 1.63 for Raspberry Pi, i.e. for an ARM core. But the build fails for boost-coroutine and boost-context. Here is my build log http://sprunge.us/NVDd As far as I can see from development files in https://github.com/ boostorg/context/tree/develop/src/asm ARM is supported at least by boost-context. Is there anything I can do about or any progress for this issue? If not, is there an older version I should try? Regards

5 18

Using the (new) C++ standard library in boost::dll
by Benjamin Buch 12 May '17

12 May '17

The boost::dll depends on 4 different boost-libraries which all have counterparts in the C++17 standard library. Worse, two of them (system & filesystem) are not header-only libraries, so you need to link against these libraries. Is it possible and planned to use the standard library counterparts as plug in replacement for these boost dependencies in a future release? In my opinion this would improve the usability massively, especially when you already use this counterparts in the rest of your program. Best regards, Benjamin

3 2

boost::process::search_path() and compound cmd
by niXman 12 May '17

12 May '17

Hi, I need to execute the 'stdbuf -oL -eL python scrypt.py' cmd but if I write the: auto p = boost::process::search_path("stdbuf -oL -eL python2"); boost::process::child c(p, "script.py"); c.wait(); I get the exception with 'execve failed: Permission denied' message. My question is, what should I change in my example for executing the 'stdbuf -oL -eL python2 scrypt.py' cmd? Thanks. -- Regards, niXman ___________________________________________________ Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: https://sf.net/p/mingw-w64/

2 1

[Fiber] Can a fiber promise be set in a different OS thread on which has no fibers running
by lin li 11 May '17

11 May '17

I have tested the following example code with Boost 1.61. And it worked (ignore the potential race conditions when accessing the variable 'p'). But I am not sure the fiber promise can be used in this way or I am just being lucky. #include <cstdlib> #include "boost/fiber/fiber.hpp" #include "boost/fiber/future.hpp" #include "boost/thread.hpp" #include <set> #include <iostream> #include <boost/date_time/posix_time/posix_time_duration.hpp> #include <boost/thread/pthread/mutex.hpp> #include <boost/thread/lock_guard.hpp> #include "boost/thread/pthread/thread_data.hpp" #include "boost/chrono/duration.hpp" using namespace std; boost::fibers::promise<int>* p; void wait() { p = new boost::fibers::promise<int>; auto future = p->get_future(); auto status = future.wait(); std::cout << "Value: " << future.get() << std::endl; delete p; } void f() { boost::fibers::fiber fiberJob(&wait); fiberJob.join(); } void setf() { // Is it safe to do this? boost::this_thread::sleep(boost::posix_time::seconds(5)); p->set_value(20); } void f1() { boost::fibers::fiber fiberJob(&setf); fiberJob.join(); } int main(int argc, char** argv) { boost::thread t(&f); setf(); cout << "Here" << endl; t.join(); cout << "Here 2" << endl; return 0; }

2 1

Cutting headers
by Igor Mironchik 10 May '17

10 May '17

Hello, How can I cut specific library from Boost, if, for example, I don't want to place all Boost but only one library from Boost? Is it possible? --- This email has been checked for viruses by AVG. http://www.avg.com

11 17

boost::asio::deadline_timer cancel and expires_from_now
by jupiter 10 May '17

10 May '17

Hi, Is it necessary to call the timer.cancel() before timer.expires_from_now? I think it is not just unnecessary, it will be a bug to call the timer.cancel() before timer.expires_from_now, I think that will run the cancel if the previous timer is not expired, is it correct? Thank you

2 2

database access library in boost?
by Paolo Bolzoni 09 May '17

09 May '17

Dear list, I was wondering, why there is no database access library in boost? (am I wrong?) It seems an imporant feature to not-have in a such library collection, so there must be a reason. Is there some "official" raccomandation? Soci, cppdb? Your faithfully, Paolo

3 2

Fwd: configure Jamfile boost 1_63_0 tutorial to build from command line with bjam
by Giulio De Luca 09 May '17

09 May '17

I´m totally new to boost, I just downloaded boost_1_63_0 and I´m trying to build the tutorial example located in \boost_1_63_0\libs\python\example\tutorial by following the tutorial documentation <http://www.boost.org/doc/libs/1_62_0/libs/python/doc/html/tutorial/index.ht…> http://www.boost.org/doc/libs/1_62_0/libs/python/doc/html/tutorial/ index.html The example is quite simple: it only contains 4 files: 1. hello.cpp 2. hello.py 3. Jamfile 4. ../Jamroot For simplicity I´m pasting below the content of each file : // hello.cpp #include <boost/python/module.hpp> #include <boost/python/def.hpp> char const* greet() { return "hello, world"; } BOOST_PYTHON_MODULE(hello_ext) { using namespace boost::python; def("greet", greet); } // hello.py import hello_ext print(hello_ext.greet()) And finally the boost configuration file: // Jamfile import python ; project tutorial : requirements <location>. ; python-extension hello_ext : hello.cpp ; run-test hello : hello_ext hello.py ; alias test : hello ; explicit test ; // ../Jamroot import python ; if ! [ python.configured ]{ ECHO "warning: no Python configured in user-config.jam" ; ECHO "warning: will use default configuration" ; using python ;} # Adjust the following if Boost.Python isn't installed in a default location lib boost_python ; project : requirements# <include>/path/to/boost/python <library>boost_python; rule run-test ( test-name : sources + ){ import testing ; testing.make-test run-pyd : $(sources) : : $(test-name) ;} build-project quickstart ; build-project tutorial ;if [ python.numpy ]{ build-project numpy ;} When I execute bjam.exe from my cmd prompt (after properly adding in the environment variables the path where bjam.exe is located) I get the following errors: ...found 12 targets......updating 5 targets... compile-c-c++ hello.obj hello.cpp hello.cpp(7) : fatal error C1083: Cannot open include file: 'boost/python/module.hpp': No such file or directory call "C:\Users\...\AppData\Local\Temp\b2_msvc_11.0_vcvarsall_x86.cmd" >nul cl /Zm800 -nologo @"hello.obj.rsp" ...failed compile-c-c++ hello.obj......skipped <p.>hello_ext.pyd for lack of <p.>hello.obj......skipped <p.>hello_ext.pdb for lack of <p.>hello.obj......skipped <p.>hello for lack of <p.>hello_ext.pyd......failed updating 1 target......skipped 4 targets... When I try and build the project from VS2012 I can build it properly because i know hot to add additional include libraries to the project, but I cannot find the proper way to config the Jamfile to make it build from command line. I tried to config the Jamroot file by changing the path to the boost/python libraries local path but with no luck. I wonder where and how should I add the absoulute path of the boost/python libraries. Any help would be much appreciated Thanks in advance!

1 0

"Invalid handle" error trying to use boost::process
by tom＠quarendon.net 09 May '17

09 May '17

I'm trying to run a simple program with boost::process, with boost 1.64 I'm using Windows, and visual studio 2015. I'm just trying to run the supplied "async_cio.cpp" example: My program is: boost::asio::io_service ios; boost::asio::streambuf buffer; bp::child c( "cmd /c dir", bp::std_out > buffer, ios ); ios.run(); (I've changed if from launching "test.exe" to launching "cmd /c dir"). If I run this I get: Exception thrown at 0x49409D2A in ConsoleApplication3.exe: 0xC0000008: An invalid handle was specified. Running in the debugger, it is in the destructor of the async_pipe object, in "win_iocp_handle_service::close_for_destruction". I've tried various of the examples with varying degrees of success. But any time I seem to use an async_pipe, I seem to get an "invalid handle" exception when it is calling CloseHandle on the completion port handle. Any ideas what I'm doing wrong? Thanks.

3 3

[Boost.Variant] Is there an r-value version of boost::get for variant?
by dariomt＠gmail.com 08 May '17

08 May '17

As seen in the std docs [1], std::get for variant provides r-value overloads. Does Boost.Variant have them? I'm interested in having this overload in particular: template<typename U, typename T1, typename T2, ..., typename TN> U && get(variant<T1, T2, ..., TN> && operand); Thanks in advance! [1] http://en.cppreference.com/w/cpp/utility/variant/get

2 2

[Units] Units in unit tests
by Stephan Menzel 08 May '17

08 May '17

Hello all, please excuse the weird subject line. I have just introduced boost units as length quantity for vectors into my project here. What previously was: typedef boost::qvm::vec<double, 3> vec3; is now: typedef boost::units::quantity<length, double> qlength; typedef boost::qvm::vec<qlength, 3> vec3; Which seems to work OK so far, I'm not done testing. While converting all my unit tests I came to wonder is how this is best adopted. I have lots of lines like: vec3 v = get_some_value(); and then I test the individual component values like this: BOOST_CHECK_CLOSE(X(v), 42.0, 0.001); // check for length of 42 meters Now this would have to be rewritten to: BOOST_CHECK_CLOSE(X(v).value(), 42.0, 0.001); But doing this, I imply the length is in meters, right? Doesn't that defeat the purpose a little? I feel this would be better: BOOST_CHECK_CLOSE(X(v), 42.0 * meters, 0.001); but the Macro won't accept this as this is not a floating point type anymore. Does anybody have some hint as to how this is best addressed while still have maximum readability? All my best... Stephan

3 5

Re: [Boost-users] Help with Boost Serialization library!
by label 03 May '17

03 May '17

Hi Tina, When you build the boost libraries, is there a way to generate .lib files for them? Below, I have documented the steps I took to build the library. Please take a glance at it and let me know if I missed something that will allow me to obtain the .lib file. I cannot see your pictures (A non-text attachment was scrubbed...), so I can only guess what goes wrong. My way building boost is (on Windows with VC++ 2015) cd c:\boost_1_64_0 .\bootstrap .\b2 --without-mpi --without-python --build-type=complete --reconfigure msvc stage This generates library files, for example libboost_serialization-vc140-mt-1_64.lib in the stage subdirectory of my boost root directory, here c:\boost_1_64_0\stage __________________________________ Freundliche Grüße * Best regards * Met vriendelijke groeten * Meilleures salutations Holger Gerth _________________________________________________________________________________ EB-Soft Gesellschaft fuer elektronische Beschriftungs-Software mbH Neckargartacher Str. 114, 74080 Heilbronn, Germany Tel: +49 (0)7131 / 9466-0 Email: info(a)ebsoft.de Fax: +49 (0)7131 / 1099-0 Homepage: www.ebsoft.de Amtsgericht-Registergericht-Stuttgart HRB 102882 Geschaeftsfuehrer: Michael Ehring, Helmut Sigler _________________________________________________________________________________

1 0

externing template instantiations of Boost.Multiprecision numbers
by Dani Brake 02 May '17

02 May '17

Hi Boost, I happily use Boost.Multiprecision inside a largely templated codebase, which involves the entirely-templated Eigen as well. My compile times are high. To gain insight into why compile time is so ridiculous, I used Templight <https://github.com/mikael-s-persson/templight> with Clang to query how many times my templates are instantiated, and how long they take. The answer was overwhelmingly that Boost.Multiprecision's number class is to blame, with 8264 instantiations of bmp::number<bmp::backends::mpft_float_backend<0,allocate_dynamic>, bmp::expression_template_option::et_on> 5052 of the same with the gmp_int backend, and 2689 for mpz_rational. I think the cure might be an extern template declaration on these three types, but where is the correct place to do this? In a header *I* have written which provides a few extensions / additions I needed? Or do I need to patch my install of BMP and put it there? As a follow-up, I have a cycle of instantiations I believe, but do not yet know, are expression templates. Can I extern a few common instantiations, and let the compiler do the rest? Any help or techniques are greatly appreciated. Especially as I (slowly) move toward applying expression templates to complex multiprecision arithmetic, too. Thanks a ton, Dani Brake University of Notre Dame Applied and Computational Mathematics and Statistics

1 0

Help with Boost Serialization library!
by Alam, Tina 02 May '17

02 May '17

Hi Boost Users, I need the Boost Serialization Library in order to use a MATLAB make file. The make file is looking for a static library file named either boost_serialization.lib or libboost_serialization.lib. However, when I built the serialization library, I got a lot of object files and rsp files rather than a .lib file. Do you know how to create the .lib file? I am not sure if it matters, but I am using a Windows computer. When you build the boost libraries, is there a way to generate .lib files for them? Below, I have documented the steps I took to build the library. Please take a glance at it and let me know if I missed something that will allow me to obtain the .lib file. 1. Download and unzip the boost folder http://www.boost.org/users/history/version_1_63_0.html 1. Look inside folder and make sure you find bootstrap.bat 1. Open the Visual Studio Developer Command Prompt and navigate to the boost folder [cid:image001.jpg@01D2BF3C.88D418B0] 1. Type bootstrap into the command line and hit enter [cid:image002.jpg@01D2BF3C.88D418B0] 1. After it finishes bootstrapping, type in .\b2 --with-serialization and hit enter. The serialization library will be built. I still have not figured out how to generate the .lib file. [cid:image003.jpg@01D2BF3C.88D418B0] Tina Alam IT Flex - Software Engineer

2 1

[BGL] null edge descriptor
by Ireneusz Szcześniak 01 May '17

01 May '17

Hi, I'm using Boost Graph Library (BGL), and I need a null edge. For years I was using G::edge_descriptor(), i.e., a default-constructed edge descriptor, and the code was working. However, I wonder if it is correct. Are all default-constructed edges equal? If I get a default-constructed edge descriptor e1 at some point in code, and another default-constructed edge descriptor e2 at some other point in code, will there descriptors always equal, i.e., will e1 == e2 always hold? Is it guaranteed that a default-constructed edge does not refer to an existing edge in a graph? Best, Irek

1 0

[review] Review of PolyCollection will start in a few days
by Ion Gaztañaga 30 Apr '17

30 Apr '17

Dear Boost community, The formal review of Joaquín M López Muñoz's PolyCollection library will start on Wednesday, May 3rd and ends on May 12th. This library implements fast containers of polymorphic objects. Typically, polymorphic objects cannot be stored directly in regular containers and need be accessed through an indirection pointer, which introduces performance problems related to CPU caching and branch prediction. Boost.PolyCollection implements a novel data structure that is able to contiguously store polymorphic objects without such indirection, thus providing a value-semantics user interface and better performance. Three polymorphic collections are provided: * boost::base_collection * boost::function_collection * boost::any_collection dealing respectively with classic base/derived or OOP polymorphism, function wrapping in the spirit of std::function and so-called duck typing as implemented by Boost.TypeErasure. If you are interested, you can start preparing your review with the following information: Repositories: Incubator: http://blincubator.com/bi_library/polycollection/?gform_post_id=1643 Github: https://github.com/joaquintides/poly_collection and the documentation here: http://rawgit.com/joaquintides/poly_collection/website/doc/html/index.html See you on Wednesday! Ion

1 0

Fwd: [boost] [clang] clang-cl expansion of macros
by degski 29 Apr '17

29 Apr '17

On 16 April 2016 at 17:58, Edward Diener <eldiener(a)tropicsoft.com> wrote: > What I strongly suspect will finally happen is that clang will not fix > these emulation problems because they are too tricky and numerous to do. > Instead they will probably declare that their emulation is good enough for > the majority of preprocessor constructs and that Boost PP, which pushes the > preprocessor to its limits, is not meant to work with their flawed VC++ > emulation. I hope I am wrong about that supposition, but having spent much > time in Boost PP and Boost VMD trying to workaround VC++ non-standard > preprocessor behavior I can envision that having to code "down" to that > behavior in numerous complicated instances will be too much time consuming > work for the clang developers who have chosen to work with VC++ > preprocessor emulation. > I've successfully built boost-1.64 with VC1410 (from the developer command prompt). Trying to use boost with a project using Clang 4.0.0 (both the LLVM and C2 backends) gives me the following PP error messages: 1>------ Rebuild All started: Project: test, Configuration: Debug x64 ------ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/ iterator/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/ aux_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(59,7): error : too many arguments provided to function-like macro invocation 1> 2 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/ iterator/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/ aux_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(58,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC2( 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(166,44): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC2' 1> #define BOOST_MPL_AUX_NA_SPEC2(i, j, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/ iterator/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/ aux_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(58,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(166,44): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC2' 1> #define BOOST_MPL_AUX_NA_SPEC2(i, j, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/def_params_tail.hpp(97,5): note: expanded from macro 'BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL' 1> BOOST_MPL_PP_DEF_PARAMS_TAIL_IMPL(i, param, BOOST_PP_IDENTITY(=value)) \ 1> ^ 1> note: (skipping 2 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(8,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/ iterator/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/ aux_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(58,1): error : template argument for template type parameter must be a type 1> BOOST_MPL_AUX_NA_SPEC2( 1> ^~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(166,44): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC2' 1> #define BOOST_MPL_AUX_NA_SPEC2(i, j, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(68,17): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> : name< BOOST_MPL_PP_PARAMS(i, T) > \ 1> ^~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> note: (skipping 5 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^~~~~~ 1> <scratch space>(33,1): note: expanded from here 1> T2 1> ^~ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(32,37): note: expanded from macro 'BOOST_PP_CAT_II' 1> # define BOOST_PP_CAT_II(p, res) res 1> ^~~ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(45,39): note: template parameter is declared here 1> , typename BOOST_MPL_AUX_NA_PARAM(T2) 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1> In file included from z:\vc\x64\include\boost/mpl/eval_if.hpp:17: 1>z:\vc\x64\include\boost/mpl/if.hpp(131,23): error : too many arguments provided to function-like macro invocation 1> BOOST_MPL_AUX_NA_SPEC(3, if_) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1> In file included from z:\vc\x64\include\boost/mpl/eval_if.hpp:17: 1>z:\vc\x64\include\boost/mpl/if.hpp(131,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC(3, if_) 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1> In file included from z:\vc\x64\include\boost/mpl/eval_if.hpp:17: 1>z:\vc\x64\include\boost/mpl/if.hpp(131,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> note: (skipping 3 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(4,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1> In file included from z:\vc\x64\include\boost/mpl/eval_if.hpp:17: 1>z:\vc\x64\include\boost/mpl/if.hpp(131,1): error : template argument for template type parameter must be a type 1> BOOST_MPL_AUX_NA_SPEC(3, if_) 1> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(68,17): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> : name< BOOST_MPL_PP_PARAMS(i, T) > \ 1> ^~~~~~~~~~~~~~~~~~~~~~~~~ 1> note: (skipping 6 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^~~~~~ 1> <scratch space>(29,1): note: expanded from here 1> T3 1> ^~ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(32,37): note: expanded from macro 'BOOST_PP_CAT_II' 1> # define BOOST_PP_CAT_II(p, res) res 1> ^~~ 1> z:\vc\x64\include\boost/mpl/if.hpp(53,39): note: template parameter is declared here 1> , typename BOOST_MPL_AUX_NA_PARAM(T3) 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1>z:\vc\x64\include\boost/mpl/eval_if.hpp(67,23): error : too many arguments provided to function-like macro invocation 1> BOOST_MPL_AUX_NA_SPEC(3, eval_if) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1>z:\vc\x64\include\boost/mpl/eval_if.hpp(67,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC(3, eval_if) 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1>z:\vc\x64\include\boost/mpl/eval_if.hpp(67,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> note: (skipping 3 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(29,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:15: 1>z:\vc\x64\include\boost/mpl/eval_if.hpp(67,1): error : template argument for template type parameter must be a type 1> BOOST_MPL_AUX_NA_SPEC(3, eval_if) 1> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(161,40): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC' 1> #define BOOST_MPL_AUX_NA_SPEC(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(68,17): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> : name< BOOST_MPL_PP_PARAMS(i, T) > \ 1> ^~~~~~~~~~~~~~~~~~~~~~~~~ 1> note: (skipping 6 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^~~~~~ 1> <scratch space>(32,1): note: expanded from here 1> T3 1> ^~ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(32,37): note: expanded from macro 'BOOST_PP_CAT_II' 1> # define BOOST_PP_CAT_II(p, res) res 1> ^~~ 1> z:\vc\x64\include\boost/mpl/eval_if.hpp(29,39): note: template parameter is declared here 1> , typename BOOST_MPL_AUX_NA_PARAM(F2) 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(40,30): error : too many arguments provided to function-like macro invocation 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, identity) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(40,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, identity) 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(40,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/def_params_tail.hpp(97,5): note: expanded from macro 'BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL' 1> BOOST_MPL_PP_DEF_PARAMS_TAIL_IMPL(i, param, BOOST_PP_IDENTITY(=value)) \ 1> ^ 1> note: (skipping 2 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(32,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(40,1): error : template argument for template type parameter must be a type 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, identity) 1> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(68,17): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> : name< BOOST_MPL_PP_PARAMS(i, T) > \ 1> ^~~~~~~~~~~~~~~~~~~~~~~~~ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1> note: (skipping 5 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^~~~~~ 1> <scratch space>(32,1): note: expanded from here 1> T1 1> ^~ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(32,37): note: expanded from macro 'BOOST_PP_CAT_II' 1> # define BOOST_PP_CAT_II(p, res) res 1> ^~~ 1> z:\vc\x64\include\boost/mpl/identity.hpp(23,39): note: template parameter is declared here 1> typename BOOST_MPL_AUX_NA_PARAM(T) 1> ^ 1>z:\vc\x64\include\boost/mpl/identity.hpp(41,30): error : too many arguments provided to function-like macro invocation 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, make_identity) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(41,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC_NO_ETI(1, make_identity) 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_facade.hpp:14: 1> In file included from z:\vc\x64\include\boost/ iterator/iterator_categories.hpp:16: 1>z:\vc\x64\include\boost/mpl/identity.hpp(41,1): error : expected ',' or '>' in template-parameter-list 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(154,47): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC_NO_ETI' 1> #define BOOST_MPL_AUX_NA_SPEC_NO_ETI(i, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(65,9): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL(i, typename T, na) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/def_params_tail.hpp(97,5): note: expanded from macro 'BOOST_MPL_PP_NESTED_DEF_PARAMS_TAIL' 1> BOOST_MPL_PP_DEF_PARAMS_TAIL_IMPL(i, param, BOOST_PP_IDENTITY(=value)) \ 1> ^ 1> note: (skipping 2 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all) 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(22,32): note: expanded from macro 'BOOST_PP_CAT' 1> # define BOOST_PP_CAT(a, b) BOOST_PP_CAT_I(a, b) 1> ^ 1> z:\vc\x64\include\boost/preprocessor/cat.hpp(31,53): note: expanded from macro 'BOOST_PP_CAT_I' 1> # define BOOST_PP_CAT_I(a, b) BOOST_PP_CAT_II(~, a ## b) 1> ^ 1> <scratch space>(61,1): note: expanded from here 1> BOOST_PP_REPEAT_1 1> ^ 1>CL : fatal error : too many errors emitted, stopping now [-ferror-limit=] 1> 20 errors generated. ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ========== Up till now I was using a hacked boost-1.62. So in order to see what would happen, I also built boost-1.63. Apart from a small change in type_with_alignment.hpp (adding a ckeck for _MSC_VER not to exist if __clang__ does exist in line 87), boost-1.63 compiles without a problem (no specific (relevant to the emulation) command line parameters). Is there a macro I should define or is there something else I should set/do in order to use boost-1.64 with Clang 4.0.0 on windows? Any other suggestions? degski -- "*Ihre sogenannte Religion wirkt bloß wie ein Opiat reizend, betäubend, Schmerzen aus Schwäche stillend.*" - Novalis 1798

1 1

[Range, Phoenix] What am I missing...
by Robert Jones 25 Apr '17

25 Apr '17

Hi Folks Can anyone explain the output of this program... #include <iostream> #include <boost/range/algorithm/copy.hpp> #include <boost/range/counting_range.hpp> #include <boost/range/adaptor/reversed.hpp> #include <boost/range/adaptor/transformed.hpp> #include <boost/phoenix/bind/bind_function.hpp> #include <boost/phoenix/core/argument.hpp> int f( int i ) { return i * 2; } int main( ) { using boost::adaptors::reversed; using boost::adaptors::transformed; using boost::counting_range; using boost::copy; using boost::phoenix::arg_names::_1; copy( counting_range( 1, 5 ) | reversed | transformed( f ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; copy( counting_range( 1, 5 ) | reversed | transformed( bind( f, _1 ) ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; } Which is... 8 6 4 2 1768406272 1768406272 1768406272 1768406272 I'm using Gcc 4.6.2 & Boost 1.53 Thx All.

3 4

[Serialization] issue with "Assertion `__null != bpos' failed"
by Francois Mauger 24 Apr '17

24 Apr '17

Hi Robert, all, In some of our libs, we use serialization through a base pointer: We have a base (abstract) class "a::base" which is available from a shared library "liba". We have created a new class "b::foo", inherited from "a::base", hosted in another shared lib "libb", "libb" being explicitly linked to "liba". In "libb", class "b::foo" is exported through : BOOST_CLASS_EXPORT_KEY2(b::foo,"b::foo") (in header foo.hpp) BOOST_CLASS_EXPORT_IMPLEMENT(b::foo) (in some libb's foo-serial.cpp source file) which I think is the right way to process to register a class in a compilation unit. In a test program, I (de)serialize 'b::foo' instances through a 'a::base' pointer. This mechanism has worked for years in all of our software chains. And today it works with our current production software system (ubuntu linux 16.04, g++ 5.4.0, GNU ld 2.26.1, Boost 1.60). However, we now face a runtime error on *some* of our boxes. The message is: <pre> ...test_app...: /path/to/boost/install/include/boost/archive/detail/oserializer.hpp:436: static void boost::archive::detail::save_pointer_type<Archive>::polymorphic::save(Archive&, T&) [ with T = a::base; Archive = boost::archive::xml_oarchive]: Assertion `__null != bpos' failed. Abort (core dumped) </pre> This error only occurs with XML or txt archives, but works like a charm with Christian's EOS portable binary ars. What is strange is that the code works on some of our systems but failed on other ones with the same compiler/linker/boost versions. The exception suggests some problem with class registration but I don't understand this (apparently) arbitrary behaviour. If any of you have a hint to help us to find the solution, it would be appreciated. thanks regards -- François

1 0

really dumb question about quickbook
by Robert Ramey 21 Apr '17

21 Apr '17

I'm struggling with quickbook When I use the following [section:userapi User API] [include types/File.qbk] [include types/Hasher.qbk] [include types/Progress.qbk] [endsect] I don't the files included. But when I use [section:userapi User API] [include types/File.qbk] [include types/Hasher.qbk] [include types/Progress.qbk] [endsect] The other files ARE included. I've looked through the quickbook docs and for the life of me I can't find where the significance (if there is any) of spaces in the markup is explained. Could someone point me in the right direction? Robert Ramey

4 18

[Boost-CRC] Warnings in crc_32_type
by tamas.ruszkai＠leica-geosystems.com 21 Apr '17

21 Apr '17

1 0

[release] Boost 1.64.0
by Rene Rivera 20 Apr '17

20 Apr '17

Release 1.64.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains one new library and numerous enhancements and bug fixes for existing libraries. For details, including download links, see < http://www.boost.org/users/history/version_1_64_0.html> You can also download directly from: < https://dl.bintray.com/boostorg/release/1.64.0/> To install this release on your system, see < http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. Thanks, -- The Boost Release Team Vladimir Prus, Rene Rivera, Marshall Clow, Eric Niebler, Daniel James, Beman Dawes

3 2