- Boost - lists.preview.boost.org

[thread] MinGW/gcc compile error in thread.cpp
by Emil Dotchevski 01 Sep '13

01 Sep '13

Building the trunk version, I get this on MinGW: gcc.compile.c++ ..\..\..\bin.v2\libs\thread\build\gcc-mingw-4.7.2\debug\link-sta tic\threading-multi\win32\thread.o ..\..\..\libs\thread\src\win32\thread.cpp: In member function 'bool boost::threa d::start_thread_noexcept()': ..\..\..\libs\thread\src\win32\thread.cpp:238:9: error: reference to 'uintptr_t' is ambiguous In file included from c:\mingw\bin\../lib/gcc/mingw32/4.7.2/include/stdint.h:3:0 , from c:\mingw\bin\../lib/gcc/mingw32/4.7.2/../../../../include/ wchar.h:479, from c:\mingw\bin\../lib/gcc/mingw32/4.7.2/include/c++/cwchar:4 6, from c:\mingw\bin\../lib/gcc/mingw32/4.7.2/include/c++/bits/pos types.h:42, from c:\mingw\bin\../lib/gcc/mingw32/4.7.2/include/c++/bits/cha r_traits.h:42, from c:\mingw\bin\../lib/gcc/mingw32/4.7.2/include/c++/string:4 2, from ..\..\../boost/date_time/c_time.hpp:18, from ..\..\../boost/date_time/time_clock.hpp:16, from ..\..\../boost/thread/thread_time.hpp:9, from ..\..\../boost/thread/win32/thread_data.hpp:10, from ..\..\../boost/thread/thread_only.hpp:15, from ..\..\..\libs\thread\src\win32\thread.cpp:17: Emil

3 2

[gil::io] clang compiler error
by Christian Henning 31 Aug '13

31 Aug '13

Hi all, I'm trying to fix some compiler errors with clang and the new gil::io. The following trivial code just wont compile: extern "C" { #include <stdio.h> #include <jpeglib.h> } int main() { jpeg_create_compress(NULL); return 0; } The error is: undefined reference to `jpeg_CreateCompress' I guess it's a very simple solution but I'm not much experienced with clang and gcc. Thanks, Christian

2 3

[cpo-proposal] presentation of the idea
by Santiago Tapia 29 Aug '13

29 Aug '13

Hi everyone, I would like to make a proposal for a new library. I only have a draft without documentation but I would like to know people’s opinion about the idea before making a formal proposal. The library will be named CPO (containers for polymorphic objects) and it will provide containers to store dynamic allocated objects from a class hierarchy. I have drafted one container and I have two more in process. The cpo library could be an alternative solution for boost pointer container library or some other solutions that use pointers. In order to understand the idea, I think that the following example of the use of the library might be better than a long explanation: #include <boost/cpo/classifier.hpp> #include <iostream> using namespace boost::cpo; class base { public: virtual int do_something(int a) const = 0; }; class derived_A : public base { public: derived_A(int b) : data(b) {} virtual int do_something(int a) const { return a + data; } protected: int data; }; class derived_B : public base { public: derived_B(int b) : data(b) {} virtual int do_something(int a) const { return a - data; } protected: int data; }; int main(int argc, char** argv) { classifier<base, std::allocator> collection; collection.insert( derived_A(21) ); collection.insert( derived_B(40) ); classifier<base, std::allocator>::iterator i, e = collection.end(); for ( i = collection.begin(); i != e; ++i ) { const base& x = *i; std::cout << x.do_something(6) << std::endl; } return 0; } ---- Program output: 27 -34 ---- Some details and advantages must be remarked in the provided example: - There are not any pointers in the client code (the example). - The container's name is classifier because it classifies objects internally using the RTTI. - The container classifier is _not_ a sequence. - Any iterator of the classifier dereferences to the base class. - The allocator argument in the classifier will be applied to every object added to the classifier. Thus, the allocator is provided without its argument. The std::allocator is the default argument. - The classifier uses continuous storage in memory for objects of the same type, therefore it is expected to improve cache efficiency with respect to solutions that use pointers (and new to allocate objects), especially if the client code uses some cache-aware allocator. I think that the idea will be interesting and useful. Although I have registered a project in sourceforge, classifier_container, I must insist: the library is under development and without documentation. I look forward to your comments and I thank you for them in advance. Best Regards, Santiago Tapia CITEF CENTRO DE INVESTIGACIÓN EN TECNOLOGÍAS FERROVIARIAS | RAILWAY TECHNOLOGY RESEARCH CENTRE UNIVERSIDAD POLITÉCNICA DE MADRID ESCUELA TÉCNICA SUPERIOR DE INGENIEROS INDUSTRIALES Santiago Tapia Fernández José Gutiérrez Abascal, 2 | 28006 Madrid TEL + 34 91 336 4267 | FAX + 34 91 561 8618 E-MAIL stapia(a)etsii.upm.es; www.citef.industriales.upm.es

8 45

about serialization
by lz＠sina 29 Aug '13

29 Aug '13

hi! I'm wonding if I can change the in "interface_oarchive.hpp": template<class T> Archive & operator<<(T & t){ this->This()->save_override(t, 0); return * this->This(); } to template<class T> Archive & operator<<(const T & t){ this->This()->save_override(t, 0); return * this->This(); } and in "polymorphic_oarchive_route.hpp" template<class T> polymorphic_oarchive & operator<<(T & t){ return polymorphic_oarchive::operator<<(t); } to template<class T> polymorphic_oarchive & operator<<(const T & t){ return polymorphic_oarchive::operator<<(t); } , so I can write code like this: enum E {}; class C { private: E e; public: E getE() const; void setE(const E e); }; template<class Archive> inline void save_construct_data(Archive & ar, const C * t, const unsigned int file_version) { // save data required to construct instance ar << t->getE(); // without changing the liberary code, I'll have to write like this: //int x = t->getE(); //ar << x; } I'm not sure about the changes, can anybody verify it? -------------- lz@sina

1 0

FW: [cfe-dev] Documenting Clang: question about how best to deliver the doc
by Paul A. Bristow 29 Aug '13

29 Aug '13

I've copied the posting below because it shows that Doxygen comments syntax are being even more widely used to add documentation of code (as opposed to writing tutorial and other descriptive text). Doxygen comments are post-processed to produce a C++ Reference section in many Boost program docs prepared using Quickbook. I suggest that this is a good method for future proposed libraries. In case you are not familiar with Doxygen, http://www.stack.nl/~dimitri/doxygen/manual/index.html here is a silly example to give the flavour of the comments (they start with the backslash trip character and are within C/C++ comments with an added !). template <typename T> int donowt(int I, char j) { /*! The ! shows that this is a Doxygen-syntax comment. Non-member free function that does nowt useful at all describing the function. \tparam T unused template parameter. \param i is an argument that is ignored completely. \param j Another argument. \pre No preconditions. \post No side effects. \returns -1 always. \throws std::exception if the unthinkable happens. \sa See also another function. */ return -1; } // int donowt(int i) Of course, the value from all this comes from the quality of the *information provided as comments*, describing the use of the parameters, templates, pre and post conditions (documenting but not enforcing concepts) and returns... Doxygen also analyses the code (now optionally using the Clang compiler - it used to get confused by some code, especially code that didn't compile!) and provides many cross-referencing links automatically, a great benefit to the authors and the readers. Doxygen remains under active development thanks to <http://www.stack.nl/%7Edimitri/doxygen/index.html> Dimitri van Heesch. It is Open-Source and entirely free and very widely used for several languages. Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com From: cfe-dev-bounces(a)cs.uiuc.edu [mailto:cfe-dev-bounces@cs.uiuc.edu] On Behalf Of Morrison, Michael Sent: Tuesday, August 27, 2013 10:40 PM To: cfe-dev(a)cs.uiuc.edu Subject: Re: [cfe-dev] Documenting Clang: question about how best to deliver the doc Thanks to everyone on this thread who replied to our query about what approach to take for our Clang documentation. Your thoughtful comments were very helpful to our understanding of the issues and of the preferences of the community. We’ve reviewed your responses to the options that we proposed, and we’ve decided to pursue the following option: > 1a) Maintain the documentation in Doxygen. Any other formats required (HTML, XML, reST/Sphynx, and so on) can be generated on-the-fly from the Doxygen comments as needed. We have a good idea about how to proceed with this option, and we expect that we can begin submitting our updated Doxygen documentation later this summer. Cheers, Michael

1 0

[voronoi]medial axis
by Louis Lavery 29 Aug '13

29 Aug '13

Hello, I'm hoping to use boost voronoi to construct the (internal) medial axis for closed shapes (with holes). I need to work out which vertices of the voronoi are inside, outside and on a boundary. So my first goal is to determine which vertices correspond to the ends of the input segments (boundary vertices). The way I do this at the moment, is to look at each edge and test if its source vertex, vertex0(), is equal to either end point of the segment contained by the edge's cell. (1) If it is then it's a boundary vertex otherwise it's not. Is that correct? (2) When comparing a vertex with an input point can I do an exact compare (==) or should I use a tolerance (epsilon)? Thanks, fuzzy.

1 0

[RPC] Boost.Asio to write *concurrency ready* code
by Niall Douglas 28 Aug '13

28 Aug '13

On 27 Aug 2013 at 12:00, boost-request(a)lists.boost.org wrote: > I am *not sure* if anyone else has made such discovery, anyway, > comment is welcomed. What you have discovered is well known I am afraid. Indeed, proposed Boost.AFIO from this year's GSoC implements an asynchronous chainable closure execution engine on ASIO, and you can read documentation on how AFIO is equivalent to Google's and Microsoft's WG21 closure execution engine proposals here: https://ci.nedprod.com/job/Boost.AFIO%20Build%20Documentation/Boost.AF IO_Documentation/doc/html/afio/quickstart/closure_execution_engines/ho w_boost_afio_relates_to_exisit.html Paul did up a great matrix mapping APIs from those engines to AFIO equivalents at https://ci.nedprod.com/job/Boost.AFIO%20Build%20Documentation/Boost.AF IO_Documentation/doc/html/afio/quickstart/closure_execution_engines/ho w_boost_afio_relates_to_exisit/comparison_of_afio_with_other_cl.html and https://ci.nedprod.com/job/Boost.AFIO%20Build%20Documentation/Boost.AF IO_Documentation/doc/html/afio/quickstart/closure_execution_engines/ho w_boost_afio_relates_to_exisit/other_useful_comparisons.html. If we get time before GSoC closes, we may just go ahead and implement N3562 (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3562.pdf) using AFIO as it would be incredibly trivial to do so. However, the Boost community only voted closure execution support as third most important - they ranked directory change monitoring as highest, so that's what me and Paul are implementing now. (FYI to those interested, we're going to deliver some *seriously* performant directory monitoring. Testing of our direct kernel syscall based implementation suggests watching a 1 million file entry directory for changes will actually work on Windows, albeit pegging a 3.5Ghz 4 core machine at 75-85% of all CPUs. Linux sadly lacks the syscalls to match Windows, but a 100,000 entry directory may well work just fine) Niall -- Currently unemployed and looking for work. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/

4 10

Problem with boost::function on BlackBerry10
by Jens Weller 28 Aug '13

28 Aug '13

Hi boost Community, I've got a little problem with getting boost::function to run on BlackBerry10. So far, I was able to compile, link and run successfully when I do comment out some stuff in boost. Surely not the right way to do it, but proves to me that those lines are the problem, I'm looking for a fix, maybe a define I need to add to let this compile without changing boost headers. In total its only 3 errors, where 2 boil down to the same macro: /home/jweller/cpp/libraries/boost_1_54_0/boost/type_traits/detail/cv_traits_impl.hpp:25: Parenthesis/brace mismatch between #if and #else branches; using #if branch /home/jweller/cpp/libraries/boost_1_54_0/boost/type_traits/detail/cv_traits_impl.hpp:93: Excess closing brace in C++ code (or abuse of the C++ preprocessor) /home/jweller/cpp/libraries/boost_1_54_0/boost/type_traits/msvc/typeof.hpp:43: Ignoring definition of undeclared qualified class These two are in cv_traits_impl.hpp in boost/type_traits/detail/, caused by this line: #if !(BOOST_WORKAROUND(__GNUC__,== 3) && BOOST_WORKAROUND(__GNUC_MINOR__, <= 2)) This line is twice in this fiel, hence the 2 errors. qcc version is gcc 4.6.3. It looks to me like BOOST_WORKAROUND isn't doing the right thing here to me. The 2nd error is more strange. /home/jweller/cpp/libraries/boost_1_54_0/boost/type_traits/msvc/typeof.hpp:43: Ignoring definition of undeclared qualified class Somehow typeof.hpp of msvc is getting pulled in. I've tried also the from BlackBerry provided boost version from https://github.com/blackberry/Boost, which shows exact the same errors. And is the one I (cruely) patched currently. Commenting out the #if !(is < 3.2) resolves the problem, but msvc is still pulled in. Also commenting in this header the cause out lets it compile, but thats nothing then a bad workaround. Currently I have only build for the simulator, but the problem is most likely also existing for the device build chain. At least the first two errors might be caused by BOOST_WORKAROUND, maybe there is a value that isn't configured correctly on this platform. Also how do I get closer to the source of the msvc code being dragged in? So, question is, is there maybe a define to help boost getting digested by the qcc toolchain? kind regards, Jens Weller

2 4

Migrating lists.boost.org
by DongInn Kim 28 Aug '13

28 Aug '13

Dear Boost community, I think it is time to move mailing lists and mail archives of lists.boost.org to the new server (wowbagger.crest.iu.edu) If it is not a bad time, can we migrate the services at 9am (E.T.) on Aug 28th? Date: Wednesday, Aug 28th, 2013 Time: 6:00am-8:00am Pacific US time 7:00am-9:00am Mountain US time 8:00am-10:00am Central US time 9:00am-11:00am Eastern US time 1:00pm-3:00pm GMT The following services may not be available during the migration. - Web services (e.g., http://lists.boost.org/) - Mailing lists: boost boost-announce boost-bugs boost-build boost-cmake boost-commit boost-docs boost-interest boost-mpi boost-test boost-testing boost-users geometry glas proto threads-devel ublas Please let me know if you have any questions or concerns about this migration. Regards, -- - DongInn

2 2

Re: [boost] [cpo-proposal] presentation of the idea
by Santiago Tapia 28 Aug '13

28 Aug '13

>Date: Tue, 13 Aug 2013 07:42:03 -0500 >From: Larry Evans <cppljevans(a)suddenlink.net> >To: boost(a)lists.boost.org >Subject: Re: [boost] [cpo-proposal] presentation of the idea > > What if the class hierarchy is used to model a graph that > contains cycles. For example, something like a spirit grammar > where a non-terminal on the rhs of a non-terminals definition? I don't see any problem, as long as they fulfill the requirements of the classifier container, i.e. the objects to be inserted should be copyable and derived from the base class in the template argument of the classifier. > Wouldn't this require some sort of smart pointer or other > garbage collection method with the ability to collect cycles? > I don't think so, the classifier container should be able to replace any occurence of something like: vector< shared_ptr <base> > in almost in any circunstance. Beside, you could avoid virtual destructors because the classifier will destroy the object directly not from a base* pointer.

5 6

Seeking "lazy piranha fedora 19 64 intel C++11" tester's contact info
by Jim Bell 27 Aug '13

27 Aug '13

Over on the boost-testing list, we're seeking the regression tester for "lazy piranha fedora 19 64 intel C++11". Please reply directly to me (off-list) if you have contact information for this person. Thanks, -Jim

1 0

Modular boost directory structure
by Edward Diener 27 Aug '13

27 Aug '13

I am seeing at https://svn.boost.org/trac/boost/wiki/StartModDev that the modular Boost directory structure is: simple include boost simple twice.hpp test twice_test.cpp Jamfile.v2 doc // from the notes on the page index.html Is this the latest correct information ? I am asking because the original recommended structure was, as I understood it: simple boost simple twice.hpp libs simple test twice_test.cpp Jamfile.v2 doc html index.html I want to make sure I have this right before I modularize my sandbox libraries for git using the correct directory structure. BTW I have not been able to figure out how to add and move directories using git in a local copy. Instead I have just done so using the OS and git seems to figure it out but I have a feeling I have lost git history in doing so.

4 6

[Boost.Log] SimpleEventLog configuration
by Pieter 27 Aug '13

27 Aug '13

LS, I am currently configuring my logging configuration using a property tree. When I include a simple_event_log_backend sink, it does not seem possible (yet) to configure an event type mapping to that sink from the property tree. The source code does contain the following comment: "For now we use only the default level mapping. Will add support for configuration later." so I guess my first question would be whether such support is indeed in the works? My second question would be whether it is possible to add such a mapping after the sink was created and added to the core. In the documentation an example is given where the mapping is done before the sink is added to the core: typedef sinks::synchronous_sink< sinks::simple_event_log_backend > sink_t; boost::shared_ptr< sink_t > sink(new sink_t()); sinks::event_log::custom_event_type_mapping< severity_level > mapping("Severity"); // . define mapping here . sink->locked_backend()->set_event_type_mapper(mapping); // Add the sink to the core logging::core::get()->add_sink(sink); but in the case at hand adding the sink happens behind the scenes when using the configuration utilities. It seems to me that there is no easy way to manipulate the sink in any way once it is added to the core (unless as in the example the shared_ptr to the sink is kept to access the sink maybe). Is this correct? Many thanks, Pieter P.s. BTW, in the section "Simplified library initialization tools" of the documentation Table 1.15 seems to miss a 'Format' parameter that I assume is still needed?

2 1

doubts about python3 support
by Neal Becker 26 Aug '13

26 Aug '13

I'm building using: bjam -d+2 -j8 cxxflags='-march=native -Wno-unused-local-typedefs' -sHAVE_ICU=1 - sEXPAT_INCLUDE=/usr -sEXPAT_LIBPATH=/usr/lib64 --layout=tagged threading=single,multi link=shared stage In user-config.jam I added: using python : 3.3 : /usr/bin/python3 : /usr/include/python3.3m ; I wind up with stage/lib/libboost_python.so stage/lib/libboost_python3.so But AFAICT, they were build the same way. It's be nice if one was built against python2 and the other python3, but that doesn't appear to be true. AFAICT, both were built from the same sources (using /usr/include/python3.3m). What I'd like is to build both python2 and python3 from the same source tree, installing the final shared libs into the same destination dir. Right now I have 2 different source trees, and build switching the one line in user- config.jam.

2 3

MSVC doesn't support "not"?!
by Daryle Walker 26 Aug '13

26 Aug '13

Just checked the regression testing pages. Most of the testing stations that reported fails for Boost.Rational have switched to pass since I've uploaded updates. Besides the stations that haven't run new tests, and the "teeks" team that run Clang tests although it seemingly isn't actually installed, the newly-run MSVC stations report fails. The old errors are gone, but the new error is: ..\libs\rational\test\rational_test.cpp(1012) : error C2065: 'not' : undeclared identifier ..\libs\rational\test\rational_test.cpp(1012) : error C2146: syntax error : missing ')' before identifier 'dummy' ..\libs\rational\test\rational_test.cpp(1012) : error C2059: syntax error : ')' This happens with MSVC 10.0 and 11.0. Hasn't "not" been an alternate symbol for "!" since C++98? I'll change it to "!", but that doesn't excuse not fixing it for 15 years! What happened? (I think some of the MSVC authors lurk here.) Daryle W.

6 7

[config] BOOST_NO_SFINAE_EXPR and GCC 4.6.4
by Agustín K-ballo Bergé 26 Aug '13

26 Aug '13

According to this table http://gcc.gnu.org/projects/cxx0x.html, GCC supports "Solving the SFINAE problem for expressions" since 4.4. According to Boost.Config, it is since 4.5. The following test case works fine with 4.8.1, but fails miserably with 4.6.4: http://ideone.com/RzgXKM Errors include invalid conversion from X const* to X*, and use of non-member-ptr in member-ptr expression. GCC 4.7.3 (tested by zao at #boost) shows similar results: https://www.acc.umu.se/~zao/kbsfinae11.txt Should BOOST_NO_SFINAE_EXPR be adjusted according to the results of this test case? Regards, -- Agustín K-ballo Bergé.- http://talesofcpp.fusionfenix.com

3 7

[RPC] Boost.Asio to write *concurrency ready* code
by microcai 26 Aug '13

26 Aug '13

Hi, boost experts! This is my first mail. Although I am not boost newbee, I am indeed new to the boost community. == I was using Boost.Asio for a long time, for *Async Network I/O*, but up till recently, I made an amazing discover that Boost.Asio is NOT ONLY a Network library, but indeed a very *general* toolkit for building concurrent algorithm. I made the first discover when my friend show up an concurrent sum ``` #include <iostream> #include <vector> #include <algorithm> #include <numeric> #include <future> template <typename RAIter> int parallel_sum(RAIter beg, RAIter end) { typename RAIter::difference_type len = end-beg; if(len < 1000) return std::accumulate(beg, end, 0); RAIter mid = beg + len/2; auto handle = std::async(std::launch::async, parallel_sum<RAIter>, mid, end); int sum = parallel_sum(beg, mid); return sum + handle.get(); } int main() { std::vector<int> v(10000, 1); std::cout << "The sum is " << parallel_sum(v.begin(), v.end()) << '\n'; } ``` Here the actual calculations are done async and concurrently. But, the problem remains: ** The total threads that this algorithm spawn is not predictable and not configurable. ** And that's why we will not like such algorithm altogether. Days later, when I am review an old code that was doing an *async directory walk through* , I soon discover an general *concurrency ready* algorithm that the number of threads utilized can be fully controlled. The code utilized *any number of threads that is doing io_service::run()* Here is the good old demo that uses recursive algorithm : ``` // this is sequential recursing version void hanoi_sync(int n, char A, char B, char C) { if (n == 1) { printf("Move disk %d from %c to %c\n", n, A, C); } else { hanoi_sync (n-1, A, C, B); printf("Move disk %d from %c to %c\n", n, A, C); hanoi_sync (n-1, B, A, C); } } ``` But with Boost.Asio, we turn it into parallelism algorithm: ``` // concurrent hannoi tower solver void hanoi_async(boost::asio::io_ service& io, int n, char A, char B, char C) { if (n == 1) { printf("thread id %d, Move disk %d from %c to %c\n", boost::this_thread::get_id(), n, A, C); } else { io.post(boost::bind(&hannoi_async, boost::ref(io), n-1, A, C, B)); printf("thread id %d, Move disk %d from %c to %c\n", boost::this_thread::get_id(), n, A, C); io.post(boost::bind(&hannoi_async, boost::ref(io), n-1, B, A, C)); } } ``` Thanks to the amazing io_service.post, we can now turing any (if not mostly) *recursing code* into *parallelism code*. And the threads that used by such *parallelism code* is fully controlled. If one thread is calling io_service::run(), then it is simple an async version of the sequential recursing one, if more that one thread is doing io_service::run(), then you know that the job is now run in parallel. And yet there needs only one place to control how may threads is used. Want it to be faster? spawn more threads to call io_service::run()! The code will *automatically* use all threads that you have allocated to Boost.Asio. I am *not sure* if anyone else has made such discovery, anyway, comment is welcomed.

1 0

[type_triats] [move] is_copy_constructible<T> trait
by Antony Polukhin 26 Aug '13

26 Aug '13

Hi, I have an implementation of is_copy_constructible<T> trait. It works great with C++11, in C++03 it detects constructors assuming that if type is derived from boost::noncopyable or uses BOOST_MOVABLE_BUT_NOT_COPYABLE macro - it has no copy constructor. Questions are: * May I add that trait to trunk version of Boost.TypeTraits (with documentation and tests, as usual)? * May I or Boost.Move maintainer apply this patch to BOOST_MOVE_IMPL_NO_COPY_CTOR_OR_ASSIGN in boost/move/core.hpp : #ifdef BOOST_NO_CXX11_DELETED_FUNCTIONS #define BOOST_MOVE_IMPL_NO_COPY_CTOR_OR_ASSIGN(TYPE) \ private:\ TYPE(TYPE &);\ TYPE& operator=(TYPE &);\ + public: \ + typedef int boost_move_no_copy_constructor_or_assign; \ + private: \ // #else Why do I need this trait? Well, it allows to implement move_if_noexcept() that is required for circular_buffer and possibly for other containers. -- Best regards, Antony Polukhin

2 4

[git] Some questions on Git transition
by Daryle Walker 26 Aug '13

26 Aug '13

* I see we have a GitHub account at https://github.com/boostorg, with repositories for each library. If we add a new library, and it has been Git-based, are we going to mirror it in the Boost account? That'll make sure if something happens to the original, we still have a last-known-good to work with. Would having all the libraries (or copies/mirrors) under the same account make scripts easier? What about non-Git libraries, will they be copied over? Would a bridge be used? (There's at least bridges for Git connecting to either Subversion or Mercurial.) * We currently ship all the libraries merged together as a single archive. Some package managers even provide the Boost libraries as a single item. When we go Git, is that still going to be in place (with the release managers doing some sort of merging script), or are we and every user going to move to doing several dozen downloads instead? (And everyone has to figure out how to use more than one Boost library at once.) * Are we eventually going to use something like http://nvie.com/posts/a-successful-git-branching-model/? If so, are we going to use that to script releases? (At release-time, grab the latest version of each library from their master branches, apply the merging script, run tests, then ship.) Daryle W.

2 3

[release] How do you make a library update official?
by Daryle Walker 24 Aug '13

24 Aug '13

I just uploaded changes ([85417] and [85418]) to Boost.Rational that fix the two major problems showing up on the regression tests. How do I get them on the official distribution? I know we don't read off the SVN-trunk directly; there's some staging area first. (That's why the shippers occasionally declare a code freeze deadline.) I know we have a "release" branch, but I'm not sure that's still being used. I want to blaze ahead making tweaks to Boost.Rational, but not if you can't "make official" a non-HEAD change-set. Even if I miss the deadline for these other tweaks, I want the two I just already did to be in Boost 1.55. Daryle W.

8 9

[admin] [svn] Boost.Commit list is not working
by Michel Morin 23 Aug '13

23 Aug '13

It seems that Boost.Commit mailing list has suspended for ten days. Regards, Michel

1 0

How not to use auto-link?
by Daryle Walker 23 Aug '13

23 Aug '13

Recently, I've been using CodeLite for Windows to do my Boost work. I have it running a MinGW-builds version of GCC 4.8 by default. I've enabled CodeLite to use Visual C++, since I have a copy of the Express version and want to avoid missing MSVC-related errors in the future. After telling CodeLite where MSVC and its directories are, I ran "rational_test.cpp" by itself, which gave up a linking error for Boost.Test. The linker was looking for those fancy named libraries that I didn't automatically make since I usually include all the source files. (And I'm using Boost from a Subversion download instead of a fixed one.) I added the source files from Boost.Test and #defined BOOST_ALL_NO_LIB=1 from the project options. The project-make system was still looking for library files! (I don't recall if it was asking for the same library file.) As I already built those files while experimenting with the documentation system, I added that directory to the search list and everything worked. I thought defining BOOST_ALL_NO_LIB was sufficient to disable auto-linking. What did I mess up? Daryle W.

2 1

[rational] Which way should std::numeric_limits::min go?
by Daryle Walker 23 Aug '13

23 Aug '13

The default implementation of a std::numeric_limits<T> instantiation is to have all static data member be set to static_cast<X>(0) and all the static member functions return T{}. When an instantiation is manually written, you're supposed to leave members for the types of numbers (integer vs. floating vs...) that you're NOT as in the unimplemented case. The static member function "min" has a defect. The function "denorm_min" returns the smallest positive value that can be represented (denormalized or not), and is implemented only for floating types. The function "lowest," new to C++11, returns the regular (i.e. not Infinity or NaN, etc.) value closest to negative-infinity. Lowest was introduced because for C++98/03, "min" returned "denorm_min" for the built-in floating types and "lowest" for built-in integer types! You can't get generic code out of that (without checking some more flags from numeric_limits). Which version of "min" should boost::rational take? I was think of "denorm_min," since I'll be implementing that. The built-in integer types use "lowest" for "min," but don't define the other one at all. Daryle W.

2 2

concurrent_unordered_map request
by Eugene Gordienko 23 Aug '13

23 Aug '13

TBB and Microsoft have it. Why not to have it in boos?

5 6

Reboot the boost web server machine
by DongInn Kim 22 Aug '13

22 Aug '13

Dear Boost community, There is a system upgrade on the boost web server machine and we need to reboot the machine to activate this change. Can we setup a schedule to reboot the server machine (wowbagger.crest.iu.edu) sometime this week? It would not take long to reboot the system (e.g., less than 10mins). If it does not cause too much disturbance, can we reboot the system at 9am tomorrow (Aug 22, 2013)? Regards, -- - DongInn

1 1

[rational] Updated for fix; run tests
by Daryle Walker 22 Aug '13

22 Aug '13

Earlier today, I uploaded a fix a narrowing-conversion bug to boost::rational. (Ticket #5855, change-set [85418]) But I did another check-in first (change-set [85417]). The lower-numbered change represented a problem while fixing the ticket. C++11 adds two static members to std::numeric_limits. One of them, max_digits10, represents how many digits are needed to be printed to (near) guarantee text/binary conversion. Boost.Test uses it in its C++11 code, so it expects any version of numeric_limits to have it, which caused errors with Boost.Rational since that part of the test code hasn't been touched since it was written nearly 7 years ago! (There was a minor tweak over 5 years ago.) One advantage with Git is that I could have checked both changes separately. Here, for Subversion, I had to back out the second change, commit the first, then redo the second to get them recorded independently. I just did a quick look at our regression tests, and most of them involve one or both of the issues I just fixed. So can everyone do a test cycle sooner rather than later? (The "teeks99-08(e|f|g|h)-Ubnutu12.04-64" teams need to make sure Clang is installed and in the PATH.) Daryle W.

1 0

[countertree] Concurrent set and map with random access iterators
by Francisco José Tapia 21 Aug '13

21 Aug '13

Hi this message is to announce the version 2.0 of the [countertree + suballocator] library. *This library provide a **concurrent** and **thread safe** implementation of the tree based data structures (**set, multiset, map** and **multimap**, plus a new data structure named **vector_tree**) with **random access iterators** and **access by position** like a vector. * *This permit to distribute the elements stored in the trees, between an arbitrary number of threads, identically as do with the vectors, making easy the design of **parallel algorithms** applied to the tree based data structures (as you can see in 2.3.- Examples<https://dl.dropboxusercontent.com/u/8437476/works/countertree_2.0/doc/P2.3_…>and 3.6.- Examples<https://dl.dropboxusercontent.com/u/8437476/works/countertree_2.0/doc/P3.6_…>) , and their use by the **multicore development tools** as **OpenMP, Threading Building Blocks ...* *You can find the documentation and the code in the GitHub* *https://github.com/fjtapia/countertree_2.0*<https://github.com/fjtapia/countertree_2.0> or you can see online in my dropbox page : https://dl.dropboxusercontent.com/u/8437476/works/countertree_2.0/index.html<https://dl.dropboxusercontent.com/u/8437476/works/countertree_2.0/doc/index…> If you prefer download a file with all the code and the documentation : https://github.com/fjtapia/countertree_2.0/blob/master/doc/countertree_2.0.… Perhaps the most interested parts of the documentation are : 1.4.- Concurrent version where explain the problems and new functions implemented 1.5.- Next improvements. Where explain the future development of the library and the concurrent algorithms 1 year ago I presented the request for the evaluation of the [countertree+ suballocator] version 1.0. The approval process is stopped due to the absence of review managers, and in the meanwhile I continued with the develop of this version 2.0. This version is big ( 50.000 lines ) and involve many programming areas ( algorithms, memory management, threads, locks ...) In the design process I must took many decision according my knowledge. I am sure there are many things to correct and improve. In the Boost community there are many people with knowledge and experience, and I trust they can help me in order to provide to the C++ users a good library. If you find an error, or you miss something in the library or have any idea or comment about it, please mail me and I will correct as soon as possible. Sincerely yours Francisco Tapia fjtapia(a)gmail.com *The Boost Formal Review Schedule is in http://www.boost.org/community/review_schedule.html where you can see the projects and their situation.

1 0

Re: [boost] Request to allow contribution to Boost.Multiprecision cpp_bin_float
by Jyotesh Choudhari 20 Aug '13

20 Aug '13

Thanks for your replies. >>> I would like to contribute to the development of Boost.Multiprecision >>> cpp_bin_float library. Can I work on it? If yes, then how can I start? >> Hi Jyotesh, >> Paul Bristow, Chris Kormanyos and I have been discussing this off-list. >> There is a prototype implementation in the sandbox under the >> multiprecision.cpp_bin_float directory.? The current code is pretty much >> complete, but under-tested.? The binary-decimal and decimal-binary >> conversion routines used are also brain-dead and do not round correctly (I >> have a mostly working version that does this correctly on my hard drive, but >> it's not quite ready for commit yet). > Yes. But remember, Jyotesh, John has taken a different direction > than my original code in the sandbox. His implementation is in > a different directory, and it's likely that we will stick with John's > and leave my prototyping to rest. May I know which directory is this? >> So one of the things we need is for >> folks to try this out and see what breaks (or rather to see what they can >> break!). > Such as try some simple math functions or to use it in > conjunction with boost::math::constants for, say, computing > a few hundred digits of pi or log(2). OK. I will try these. >> Some of the std lib function test cases in the sandbox also fail >> currently as their error rates are too high.? Many are also much slower than >> say MPFR.? Chris, would have a better idea which most need working on. > Always important are square root, sine, cosine, and log. >> And finally, the implementation uses all integral arithmetic internally (via >> cpp_int), so one big improvement we need is for someone to write Karatsuba >> and FFT based multiplication routines for cpp_int (Karatsuba is probably the >> higher priority).? Oh and we have no docs yet. > Yes, very important, as this is a huge limitation of cpp_dec_float --- > at least for the digit hunters among us. :-) I will implement Karatsuba algorithm and let you know when I am finished. Thanks and Regards, Jyotesh Choudhari >> Anything there look like something you'd like to work on? >> Thanks for the interest, John. > Thanks for the interest. > Sincerely, Chris.

2 1

Is there BOOST_ENABLE_IF macro now?
by TONGARI J 20 Aug '13

20 Aug '13

Hi folks, It's over 2 years since this post: http://boost.2283326.n4.nabble.com/New-powerful-way-to-use-enable-if-in-C-0… The macro looks sweet and I wonder if we have this macro in Boost in case that I missed it. Thanks.

5 27

Re: [boost] [boost::spirit::basic_hold_any] needs non template operator=
by Hartmut Kaiser 20 Aug '13

20 Aug '13

> I found that hold_any template operator= is not used during assignment to > another hold_any (as intended by its developer). Instead compiler uses > self generated version of operator= which doesn't forward to assign(const > basic_hold_any&). This leads to memory corruption. > The fix is simple - you need to add explicit operator=(const > basic_hold_any&). > My compiler is gcc 4.4.7 and I use option -std=c++0x Version of boost is > 1.53 but I don't see that something changed in 1.54 so it should have the > same issue. Please provide a patch which I will gladly apply. Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu

1 0

[thread] Dividing into Boost.Thread and Boost.Sync
by Andrey Semashev 20 Aug '13

20 Aug '13

Hi, In our private conversation Vicente J. Botet Escriba, Tim Blechmann and myself have formed a proposal to split the current Boost.Thread library into two libraries: Boost.Thread and Boost.Sync. The former will retain its thread management features, such as thread class, futures and TLS. The latter will contain all thread synchronization components, such as: - locks - mutexes - condition variables - call_once Mutexes and condition variables in Boost.Sync will not support thread interruption and will be as simple and lightweight as possible. For example, one of the benefits I'd like to achieve with this is that synchronization primitives should become decoupled from the timing libraries. I'm not sure we'll be able to make the whole library header-only, but we will try to. If some component is header-only, it will not require linking to Boost.Sync. We plan to add new components to Boost.Sync after the extraction is made. The current candidates for addition are: - spin_mutex and yield_spin_mutex. There are several implementations in Boost, namely in Boost.SmartPtr, Boost.Log and Boost.Atomic. The plan is to refine them into two flavors of spin mutex and move to Boost.Sync and then switch these libraries to the common implementation, if possible. - once blocks from Boost.Log. - portable Windows-style events. There is a prototype implementation in Boost.Log. Boost.Thread will depend on Boost.Sync and will retain headers and possible glue code for backward compatibility. For instance, I think it will have to implement interruptible condition variable. Comments are welcome.

6 17

[serialization] Portable binary archive
by Renato Forti 19 Aug '13

19 Aug '13

Hi All, I am using boost serialization to transfer files, because of portability, I am using: boost::archive::text_oarchive boost::archive::text_iarchive But in testing I've done, it seems to quadruple the size of the file! I saw it in serialization test folder: boost_1_54_0/libs/serialization/example 4 files to work in binary mode (that are very more efficient way): portable_binary_iarchive.cpp (hpp) portable_binary_oarchive.cpp (hpp) My Question: Why not this files are on the library? Anyone ever used them in production? Are safe? How to use? How build serialization lib with these files? I need change bjam of serialization to include these files? One more question: Someone has used Google Protocol Buffer? Could compare with boost serialization? <https://code.google.com/p/protobuf/> https://code.google.com/p/protobuf/ Thanks

1 0

Request to allow contribution to Boost.Multiprecision cpp_bin_float
by Jyotesh Choudhari 19 Aug '13

19 Aug '13

I would like to contribute to the development of Boost.Multiprecision cpp_bin_float library. Can I work on it? If yes, then how can I start? Thanks and regards, Jyotesh Choudhari

3 2

[asio] how to limit speed of tcp socket on asio?
by Renato Forti 19 Aug '13

19 Aug '13

Hi All, Anyone can help-me! I want know if have some way to limit speed of tcp socket on asio? For sample if my app open a socket and start to send a file to my server! How to limit upload speed? If I want limit to 100kb/s, have any way? Anyone have any idea: how I can achieves this? Thanks

2 1

Re: [boost] [cpo-proposal] presentation of the idea
by Santiago Tapia 19 Aug '13

19 Aug '13

> Date: Fri, 16 Aug 2013 13:00:57 +0200 > From: Thorsten Ottosen <thorsten.ottosen(a)dezide.com> >> int main(int argc, char** argv) >> { >> classifier<base, std::allocator> collection; >> >> collection.insert( derived_A(21) ); >> collection.insert( derived_B(40) ); >> >> classifier<base, std::allocator>::iterator i, e = collection.end(); >> >> for ( i = collection.begin(); i != e; ++i ) >> { >> const base& x = *i; >> std::cout << x.do_something(6) << std::endl; >> } >> >> return 0; >> } > > I would like to see the use of forwrding in-place construction: > > collection.push_back<derived_A>( 21 ); > > using variadic templates. OK, I will try. > >> - The container's name is classifier because it classifies objects >> internally using the RTTI. > > I had similar ideas that I wanted to implement. I didn't expect to use > RTTI. Basically I wanted the class hierarchy's base class to derive from > a class with pure virtual functions that allowed the container to > perform the inplace-contruction, copying and alignment stuff. I am trying to make the interface of the container as easy as possible. I think using RTTI is an easy solution. > >> - The container classifier is _not_ a sequence. > > I would expect the container to allow forward iteration. I assume you > mean that erase/insert into the middle is prohibited? I imagined that > only push_back/pop_back was supported. > >> - The classifier uses continuous storage in memory for objects of the >> same type, therefore it is expected to improve cache efficiency with respect >> to solutions that use pointers (and new to allocate objects), especially if the >> client code uses some cache-aware allocator. > > I wanted to call my class template polymorphic_vector, taking base class > and allocator template arguments. I imagined that the storage > would be completely contigious, even when many different types of > objects where stored into the container. This would give maximum cache > efficiency. Then if the user wanted to sort or otherwise manipulate the > sequence, he could just create an std::vector<T*> of the elements > (Thus, push_back should probably return a pointer to the constructed > element). I am thinking about including that std:vector<T*> internally in another container, thus, I could provide a random access iterator. That could be "sequence_classifier". But I see a problem: if we only sort the vector<T*> then the objects in memory of consecutive iterations will not be contigous in memory and we will lose some of the cache efficiency. I will try to provide another kind of iteration, actually a two-levels iteration, like in a matrix, in order to gain access to the vectors of objects. That way we might sort objects of the same type without drawbacks. > > All in all, I hope you will persue this idea. I certainly have many > use-cases for it in code where efficiency matters, and in code where > using Boost.Intrusive is just must more work. > > kind regards > > Thorsten > Date: Fri, 16 Aug 2013 19:20:36 -0500 > From: Larry Evans <cppljevans(a)suddenlink.net> >> Yes, that is the idea. Actually, whether the implementation uses a collection >> of vectors or other mechanism is an implementation detail. I use a map >> of vectors in the classifier container, but I will try other implementations. > Is the map key something like the type_info: > > http://www.cplusplus.com/reference/typeinfo/ Yes, actually a wrapper of typeinfo because of a problem with typeinfo I could not workaround. But that is an implementation detail, I mean, that will be an inner detail of the library and I might find a better solution without changing the interface of the classifier container. > > If there is a separate vector for each type, then the storage for a > container containing more than one type can't be contiguous, > since the vectors for the containers for the types cannot be > contiguous, or am I missing something? I think what Thorsten > was aiming at in this post: > > http://article.gmane.org/gmane.comp.lib.boost.devel/243504 I could not follow the link... ? > > was each element in the container was truly contiguous. IOW, > given a container, c, then. > > c.insert(T1()); > c.insert(T2()); > > The T1 inserted into c would be contigous with the T2. No, in the prototype of the classifier T1 will not be contigous with T2, but: c.insert(T2()); c.insert(T2()); first object of T2 will be contigous with second object of T2. > > [snip] >>> Date: Tue, 13 Aug 2013 23:33:25 +0400 >>> From: Andrey Semashev <andrey.semashev(a)gmail.com> >>>> >>>> - The container classifier is _not_ a sequence. >>> >>> Why? Is this intentional? >> >> Both intentional and accidental, because I want to allocate objects >> contiguously in memory I have to store them in a collection of >> vectors, the container is not a sequence but a collection of sequences, >> one sequence for every class in the classifier. >> I will implement a sequence, but later. >> > > The above reinforces my above conclusion that T1 and T2 elements > cannot be contiguous in the container. A container might store T1 and T2 contigously, but up to now, that is not my idea, because it is more difficult and I am not sure about the efficiency of that alternative. Actually, I have read somewhere that there is a cache memory for functions, in that case, classifying the objects by type could be a good implementation because the virtual methods could be stored in the cache until the objects of that type were finished. > Date: Sat, 17 Aug 2013 08:12:48 -0400 > From: Rob Stewart <robertstewart(a)comcast.net> > To: "boost(a)lists.boost.org" <boost(a)lists.boost.org> > Subject: Re: [boost] [cpo-proposal] presentation of the idea > > On Aug 16, 2013, at 9:21 AM, Santiago Tapia <santiago.tapia(a)upm.es> wrote: > >>> Date: Tue, 13 Aug 2013 23:33:25 +0400 >>> From: Andrey Semashev <andrey.semashev(a)gmail.com> >>> >>>> - The allocator argument in the classifier will be applied to every object added to the classifier. Thus, the allocator is provided without its argument. The std::allocator is the default argument. >>> >>> You can use the standard interface for allocator rebinding: >>> >>> typedef allocator<T> allocator_T; >>> typedef typename allocator_T::template rebind::other allocator_U; >>> >>> You can use std::allocator<void> by default then. >> >> I am not sure how to do this. I need a allocator with a parameter in order to get: allocator<triangle>, allocator<square>, ... this allocator must be instantiated when an object of a new class is inserted in the classifier. > > That's the point of rebind. Starting with allocator<A>, you can get allocator. The spelling of allocator just looks odd: > > typename allocator<A> template ::rebind::other > > ___ > Rob > Understood, thank you both for the comment. > Date: Sat, 17 Aug 2013 09:20:14 -0500 > From: Larry Evans <cppljevans(a)suddenlink.net> > > The attached demonstrates, I believe, what Thorsten was aiming at > an shows the storage of *different* types in contiguous storage. > > HTH. > > > -regards, > Larry > >

3 2

[AFIO] AFIO Proposed feature Voting announcement
by Paul Kirth 19 Aug '13

19 Aug '13

Hello Boost-dev and Boost-users, I’m Paul Kirth, and I am the student working on the upcoming AFIO library this summer as part of GSoC. As of last week AFIO is fully ported to Boost and is now building cleanly on all of the last three major releases of the three most popular C++ compilers. Niall Douglas, my mentor for AFIO, has previously mentioned on the list that we would be asking for your feedback regarding which new features would be most beneficial to the Boost community. We would like to accommodate you all, but with GSoC being limited in time and ending in just one month’s time now, we’re going to limit the current additions to the top 3 most requested features. I plan to stay involved with AFIO for as long as I am able, so I’m sure many more of these features can be supported by AFIO in the future. I have set up a voting site on https://boostafio.uservoice.com to help with the voting. You may vote 10 times as you see fit, and you can give more (or all!) votes to those features you prefer the most. You may also add additional features not currently up for voting, so we encourage you to read the whole list of proposed additions before adding your own. Try to be descriptive with your feature request including a rationale, as not everyone involved with Boost may have the same expertise as you do. Including an example of how this feature would useful will help make a good case for your feature request, and help voters identify what is important. Finally, if you are not familiar with AFIO, we encourage you to take a look at our documentation at https://ci.nedprod.com/view/All/job/Boost.AFIO%20Build%20Documentation/Boos…. A link is also present on the voting site for your convenience. Additionally you will find our project on github at https://github.com/BoostGSoC/boost.afio, if you wish to dive into the source code for yourself. Voting is open right now, so please be sure to vote before the voting period ends on 8/23/13 at 11:59 PM GMT-8:00. We look forward to seeing which features are most important to the community, and hope to meet your expectations. Quick list of the features already proposed: Directory Monitoring Support Permissions and ACL Support Support for Boost Iostreams Improve Formal Closure Execution Engine Support Asynchronous Directory Enumeration Memory Mapped File Support Support for STL Iostreams Linux Kernel AIO Backend POSIX aio_* Asynchronous I/O Backend -- Paul Kirth

1 0

[Interprocess] Named pipe interface proposal
by Geoff Shannon 18 Aug '13

18 Aug '13

I emailed the list a while ago that I was starting to work on a named pipe implementation for potential inclusion in the Boost.Interprocess library, and now I finally have some concrete evidence of progress. I've come up with a header file for my proposed interface and I would really appreciate any and all feedback on it. Particularly, I'm interested in ideas for an appropriate replacement for using char *'s as the data buffers for reading and writing. As a point of interest this interface is meant to be extremely simple. I don't intend to initially support ANYTHING except for basic creation and reading and writing. Thanks! -- Geoff Nothing is ever easy.

9 36

about bessel function
by llwaeva＠gmail.com 17 Aug '13

17 Aug '13

Hi all, I am testing the bessel function boost::math::cyl_bessel_j in gnu compiler with boost 1.51.0, I am testing boost::math::cyl_bessel_j(2000, 0.9) boost::math::cyl_bessel_j(4000, 0.9) the first one give zero but the second one gives infinity while it should give zero also. I wonder why it doesn't work when the order is bigger than 4000?

2 1

Re: [boost] [Interprocess] Named pipe interface proposal
by John Venarchick 15 Aug '13

15 Aug '13

> > > > I would URGE you to make this exclusively a Boost.ASIO implementation. > > I also agree, an ASIO implementation is the way to go with this. > > 3. There seemed to be some confusion regarding named pipes on POSIX. > > > The only difference between Windows and POSIX named pipes is that the > > > former use the NT kernel namespace, within which the filing systems > > > are mount points, whereas the latter use the filing system namespace > > > directly. In my own code, I use a magic directory in /tmp as the > > > namespace for all my named pipes in the system in an attempt to > > > replicate a similar behavior to Windows, but there are many other ways > > > of doing the same thing. > > > > > > > Hmmm, I see what you're saying and I agree with it, but I'm also not sure > that > > it's strictly true that this is the "only" difference. > also a +1 to using POSIX pipes instead of domain sockets. I don't think you'd need to copy Niall's /tmp/ magic directory or if so make that an option. > > Also, FYI, I'm doing this project as an independent study through my CS > program. > > I'm getting close to the end of the quarter and I need to have something > > concrete to show for my efforts. Since I've already started down the > path > of > > implementing this not inside of Boost.ASIO, for the purposes of my school > > project I'm going to continue with that. However, I plan to continue > working on > > it after the scholastic bit is finished, and then I would be interested > in > > implementing it as part of ASIO. > > That's pretty cool as a CS project. I hope you get a good grade. I've done far too much with Windows pipes and would definitely like to see an ASIO interface if not just to replace what I'm doing now. -John V

1 0

Endian Library?
by Andrew Ho 15 Aug '13

15 Aug '13

Hi, I'm curious what the status for endian/byte order support in Boost is (namely, detecting system byte order and swapping between byte orders)? I did a quick search of the include dir and it seems that Spirit has some endian support, though I haven't found any documentation. There's also boost/detail/endian.hpp which has detection of the endian-ness, but doesn't provide any structure for switching between endians/byte-orders. I also found endian.h in predef, which appears to do something similar to boost/detail/endian.hpp. Searching through the list, there were at least 2 different proposals for Boost.Endian (a few years ago), though as far as I can tell neither of these implementations were formally adopted into Boost. I couldn't find any reason why they weren't included.

2 1

server error on ci.boost.org?
by Anthony Foiani 15 Aug '13

15 Aug '13

[Sorry for sending this to the dev list, but I didn't see a server admin email address anywhere obvious. Or I just went right past it, one of the two...] I was searching for something on Google, and one of the hits was on ci.boost.org: http://ci.boost.org/websvn/filedetails.php?repname=repos+1&path=%2Ftrunk%2F… [shortened: http://preview.tinyurl.com/lkvqbo3 ] When I went there, I got the navigation elements, but the actual content was missing, and instead there was a yellow warning box with this message: Unable to cat file: svn: Can't write to stream: No space left on device Thought you all might like to know. Thanks, Anthony Foiani

2 4

[Asio] Commit-rollback on asynchronous operations - cancel / close may fail
by Sorin Fetche 15 Aug '13

15 Aug '13

Hi, I noticed that functions for canceling asynchronous operations or closing objects on which they are executed are documented as being possible to fail. This is the case at least for the acceptor objects (basic_socket_acceptor or ip::tcp::acceptor), socket objects (basic_socket or ip::tcp::socket) and even timer objects (deadline_timer or steady_timer). In this case what are the options for implementing commit-rollback for asynchronous operations? By rollback I mean canceling a successfully started first operation in case a second operation in the batch of operations fails (as exemplified in the attached test code). As described in [1] a rollback operation absolutely relies on no-throw operations. What is supposed to happen with the handler associated with the asynchronous operation that failed to be canceled? Handlers, most often, at least for non-trivial programs are carrying shared resources with them and, if not called, may leave the application in a hanged state waiting for an event that will never come. I didn't find in the documentation any guarantees given regarding the handlers associated with the async-operations that they can or cannot be lost (that is never called). This of course, as long as io_service::run is running or the control returns to it after an exception. Also, as shown in [2] and as demonstrated by the attached test program, at least for async_write, invoking the destructor of an object on top of which asynchronous operations are being executed is not correct either and may lead to undefined behavior (crash). [1] Exception-Safety in Generic Components; section 6 http://www.boost.org/community/exception_safety.html [2] BoostCon 2011: Thinking Asynchronously; slide 47 https://github.com/boostcon/2011_presentations/raw/master/mon/thinking_asyn… Thank you, Sorin Fetche

1 0

[serialization] How are floating point values handled?
by John Maddock 14 Aug '13

14 Aug '13

I can't find anything in the docs about how floating point types are handled by the serialization lib. It seems like text archives print however many digits are specified in the ostream's precision is that correct? If so I think this needs to be raised as a big red flag, because it means that floating point values, uniquely compared to other primitives, do not round trip by default. Except actually they do when using a binary archive. This actually raises a problem when using text archives with floating point data - if you want to be able to round trip the values, then how many digits precision should you set the stream to? Particularly if you're saving a complex structure containing different floating point types of differing precisions? I would have thought it would be better for the serialization lib to set the stream precision before outputting a primitive type - to std::numeric_limits<T>::max_digits10 (or std::numeric_limits<T>::digits10+2 if max_digits10 is not available). However, I recognize that this is a difficult issue! Cheers, John.

4 15

Pre-build MSVC Boost binaries
by Fredrik Orderud 13 Aug '13

13 Aug '13

Over the last year, I've set up a small SourceForge "WinBin" project [1] for distributing Microsoft Windows binaries for Boost (and some other projects). The repository is sorted by Boost version, compiler version and shared vs. static linking. Each file archive contains pre-build boost in debug/release for both 32/64-bit, following a include/lib[64]/bin[64] folder structure. There also seems to be some other sources for pre-built boost around (e.g. https://sourceforge.net/projects/boost/files/boost-binaries/ and http://boost.teeks99.com/bin/) However, these do not seem to provide boost built for both static and shared linking. Also, they do not appear to adhere to the "quasi standard" include/lib[64]/bin[64] folder naming convention used by many libraries. Finally, they seem to lack information on which version of python (and possibly other 3rd party SW) they are compiled against. Therefore, I decided to set up my own boost-binaries webpage. Please let me know if you might be interested in either improving the "WinBin" project, or somehow joining forces to merge the various sources of Boost binaries into a single, more "authoritative" repository. I would be more than happy to shut WinBin down if "similar enough" binaries can be downloaded elsewhere. Thanks in advance, Fredrik Orderud [1] https://sourceforge.net/projects/winbin/files/boost/

5 10

[utility] Fixes to value_init docs
by Robert Kawulak 13 Aug '13

13 Aug '13

I've made some small fixes to value_init docs (patch attached) that I want to commit. Any objections? Best regards, Robert

2 1

Line endings fixes
by Vitaly Budovski 13 Aug '13

13 Aug '13

Hi, Please see the attached files. boost_endings1.patch just sets some of the cpp and other text files to have file endings consistent with the rest of the repository. boost_endings2.patch may be controversial as it does the same but for the svg files. Some of them are marked as text, others as binary. It's a real mess. Most of the svg files are generated from other sources so should probably be omitted from the repository and simply regenerated when docs are built. Came across these issues when checking out the modularised boost git repository. Regards, Vitaly

7 32

unique_ptr for C++03
by Andrew Ho 13 Aug '13

13 Aug '13

Hi, I implemented std::unique_ptr using C++03 features plus a few other Boost Libraries. Incidentally, I also implemented default_delete (which binds to std::default_delete if available) because it's required for unique_ptr. https://github.com/helloworld922/unique_ptr The library binds to std::unique_ptr if standard library support is available. There are a few things I don't think I'll be able to emulate exactly. Namely: - I don't think the deleter can ever be forwarded correctly (limitation of C++03). Ideas/suggestions for how to best handle this are welcome (currently, I move the deleter if E == D and copy otherwise, I think) - There's no explicit conversion overloads in C++03. Currently I have operator bool() implemented non-explicitly if there's no compiler support, relying on the user to only use it "as-if explicit". An alternative solution is to remove the typecast operator and force users to use get() == NULL_VALUE. - functions relying on nullptr_t are only enabled if compiler support is available. Again, I don't think there's any possible work-around for C++03. There are also a few missing features (still working on the implementation): - make_unique (part of c++14) - nullptr_t comparison operators Current dependencies (assuming no C++11 std::unique_ptr): - Boost.Config - Boost.Move - Boost.TypeTraits Comments/Feedback is welcome.

10 23

Location for library-specific utility files in Subversion trunk
by Jeremiah Willcock 12 Aug '13

12 Aug '13

I have a file containing the list of unmerged changes from BGL and some command lines to simplify merging changes from the trunk to the release branch and to help in writing release notes. They are not useful to have in a release, but I would like to have them stored somewhere other than just my home directory. Is there a path designated for that? Somewhere inside tools/release/? -- Jeremiah Willcock

1 0

Inspection report: revision used?
by Joaquin M Lopez Munoz 11 Aug '13

11 Aug '13

Hi, The current inspection report, dated 15:30:32 UTC, Saturday 10 August 2013: http://boost.cowic.de/rc/docs-inspect-release.html fails to state the SVN revision being inspected The files checked were from unknown at revision unknown As it happens, whatever revision of the code is being used it has to be older than Aug 10, since the error reported at http://boost.cowic.de/rc/docs-inspect-release.html#flyweight has been fixed as of Aug 6, i.e. four days before: https://svn.boost.org/trac/boost/changeset/85227 Just a heads up in case there's something to fix on the inspection report running engine. Joaquín M López Muñoz Telefónica Digital

1 0

[mixin] New library reminder
by Borislav Stanimirov 11 Aug '13

11 Aug '13

Hello, Some of you might remember the previous discussion on the subject (archived here: http://lists.boost.org/Archives/boost/2013/01/200598.php) Anyway, in short, I'm developing a library with the intention to formally submit it to Boost by the end of the year. You can find it here: https://github.com/iboB/boost.mixin The latest news about it is that I think that the library's features for the formal submission are done and all that's left are minor tweaks, bug fixes, tests, examples, and, most importantly, a complete documentation. In the meantime, I again invite you all to check it out. Any comments, suggestions, and questions will be greatly appreciated. Thanks, -- Borislav

3 17

Fwd: Line endings fixes
by Vitaly Budovski 11 Aug '13

11 Aug '13

Hi, On 10 Aug 2013 18:55, "Paul A. Bristow" <pbristow(a)hetp.u-net.com> wrote: > > I'm confused, but does it help you to know that the many SVG files for Booth.Math are generated by a > C++ program that we run. > > This program writes html and end of line as std::endl;. > Regardless of the method, any text based formats should be checked into SVN with mime-type text/plain and native eol. > These SVG files are used to generate the PDF version of Boost.Math docs (because using PNG produces > very poor display). > No disagreement about SVG being the better choice where possible. > These SVG files are also converted to PNG for the html version. > <snip> > > HTH > > Paul Cheers, Vitaly

3 3

Releasing Boost Dependency Analyzer 1.1
by Jens Weller 11 Aug '13

11 Aug '13

Hello boost community, a short notice that I just have released the version 1.1 of my dependency analyzing tool for boost. For now I have only managed to get a proper Windows Version, Linux Version will follow later. New Features: Configuration - the tool remembers the path to bcp now - select the source for libraries - maintainers.txt - libraries.xml - 2 filter options - filter libraries by name - filter edges by type, for now its header, source/lib, test and documentation. Export: - Export CSV File which has all libraries and the number of dependencies (sorted) libraries.xml - this is now a optional source for the library names Some feedback: libraries.xml as a lib name source is nice, but not quite perfect. I've seen different results from maintainers.txt and libraries.xml. As maintainers.txt also libraries.xml contains duplicates, some of its library names don't fit the expectation of bcp, so I applied some fixes for this in my program. The Dependency filter is yet not perfect, especially in detection. More details about this version and the download for it at my blog: http://www.meetingcpp.com/index.php/br/items/releasing-boost-dependency-ana… kind regards, Jens Weller

4 5

Boost 1.54 build problem: --without-context not honoured?
by Steve M. Robbins 11 Aug '13

11 Aug '13

Hi, I'm digging into a build problem and noticed that even though I specify "./bjam --without-context", Boost.Context is still built! The bjam configuration output states that Context is not to be built: Component configuration: - atomic : building - chrono : building - context : not building - coroutine : building - date_time : building - exception : building But it is built nonetheless. This causes a build failure for architectures which are not supported; see build log [1]. Compare that to the build for 1.53 [2] which works fine. I've diffed the libs/context directory between 1.53 and 1.54 and nothing jumps out at me as the cause. Has anyone noticed and fixed this already? Thanks, -Steve [1] https://buildd.debian.org/status/fetch.php?pkg=boost1.54&arch=ia64&ver=1.54… [2] https://buildd.debian.org/status/fetch.php?pkg=boost1.53&arch=ia64&ver=1.53…

4 4

[preprocessor] nested for_each not working like expected
by Eric Niebler 10 Aug '13

10 Aug '13

I can't figure out what I'm doing wrong. According to the docs, this should work: #define S0 (0)(1)(2)(3) #define S1 (5)(6)(7)(8) #define M4(R, DATA, ELEM) (DATA,ELEM) #define M2(R, DATA, ELEM) BOOST_PP_SEQ_FOR_EACH_R(R, M4, ELEM, S1); BOOST_PP_SEQ_FOR_EACH(M2, ~, S0) I expect to get a sequence like (0,1)(0,2)... for each combination. I get gibberish. (Please don't tell me to use FOR_EACH_PRODUCT. In my real use case, M2 and M4 are far more complicated, and a simple product won't do.) Can anybody please tell me what I'm doing wrong? TIA, -- Eric Niebler Boost.org

5 11

[chrono] Outdated information in documentation
by Björn Pollex 10 Aug '13

10 Aug '13

In the getting started section [1] it refers to an issue with the BOOST_ERROR_CODE_HEADER_ONLY macro which seems to be fixed by now. Regards, Björn [1] http://www.boost.org/doc/libs/1_54_0/doc/html/chrono/users_guide.html#chron…

2 1

[date time] std::out_of_range thrown on date 2012-5-29
by Matthijs Möhlmann 09 Aug '13

09 Aug '13

Hello all, Following piece of program gives a std::out_of_range exception: #include <boost/date_time/posix_time/posix_time.hpp> int main(int argc, char **argv) { boost::posix_time::ptime datetime; datetime = boost::posix_time::time_from_string("2012-5-29"); return 0; } Compiled with the following line: g++ -o main -lboost_date_time -g -std=c++11 main.cpp Output: matthijs@hammer % ./main terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at zsh: abort ./main Platform: x86_64 Boost version: 1.54 Compiler version: gcc 4.8 Where can I officially report bugs? Regards, Matthijs Möhlmann

3 3

[move] forward with lvalue ref template param
by Andrew Ho 08 Aug '13

08 Aug '13

Hi during my implementation of unique_ptr I noticed that boost::forward doesn't play nicely with lvalue ref types. int a; int &b = a; int &c = std::forward<int&>(b); // compiles fine int &d = boost::forward<int&>(b); // compiler error I did a little playing around with the declarations of forward and I managed to get this to work: // if T is not a lvalue ref and movable template <class T> inline typename ::boost::move_detail::enable_if_c < enable_move_utility_emulation<T>::value && ::boost::move_detail::is_rv<T>::value && !::boost::move_detail::is_lvalue_reference<T>::value, const T &>::type forward(typename ::boost::move_detail::identity<T>::type &x) BOOST_NOEXCEPT { return const_cast<T&>(x); } // if T is not a lvalue ref and not movable template <class T> inline typename ::boost::move_detail::enable_if_c < enable_move_utility_emulation<T>::value && !::boost::move_detail::is_rv<T>::value && !::boost::move_detail::is_lvalue_reference<T>::value, const T &>::type forward(const typename ::boost::move_detail::identity<T>::type &x) BOOST_NOEXCEPT { return x; } // if T is a lvalue ref template <class T> inline typename ::boost::move_detail::enable_if_c < ::boost::move_detail::is_lvalue_reference<T>::value , T>::type forward(T x) BOOST_NOEXCEPT { return x; } Basically, this forces all calls to forward<A&> to simply return the lvalue ref (const-ness is maintained, I think), otherwise it does whatever boost::forward did before. As far as I can tell, this doesn't break boost::forward, and it enables it to properly handle taking lvalue refs. Am I right in my assumptions? Are there any cases where this would fail to produce standard-compliant/desired results?

1 0

[git] eol issues and fetchRecurseSubmodules = on-demand
by Ahmed Charles 08 Aug '13

08 Aug '13

Two things: 1. tools\build\v2\engine\build.bat has LF instead of CRLF for line endings, which causes bootstrap.bat (which has the right endings) to not work properly. It seems like the top level .gitattributes doesn't apply to submodules. 2. After cloning and fetching modular boost each day for a while, I finally figured that waiting an hour or so to sync could probably be improved. So I read the docs and tested adding fetchRecurseSubmodules = on-demand for each submodule in .gitsubmodules and it seems to work much faster with the same result. (It would result in differences once the submodules can change without the super-project changing, but currently, I don't think that is the case.) Perhaps it's with considering?

2 5

[boost/spirit] numeric policy
by Brian Schrom 07 Aug '13

07 Aug '13

I've had the case where I needed to retain formatting information for a number (general, fixed, scientific) and was nicely accomplished by extending the policy, but needed to have a begin_parse() and end_parse() for the policy to be complete. It seems that it makes some sense or is this accomplished another way? Maybe something to consider for policies in general? Index: qi/numeric/real_policies.hpp =================================================================== --- qi/numeric/real_policies.hpp (revision 85166) +++ qi/numeric/real_policies.hpp (working copy) @@ -28,6 +28,18 @@ static bool const allow_trailing_dot = true; static bool const expect_dot = false; + template <typename Attribute> + static void + begin_parse(Attribute& attr_) + { + } + + template <typename Attribute> + static void + end_parse(Attribute& attr_,bool /* result */) + { + } + template <typename Iterator> static bool parse_sign(Iterator& /*first*/, Iterator const& /*last*/) Index: qi/numeric/detail/real_impl.hpp =================================================================== --- qi/numeric/detail/real_impl.hpp (revision 85166) +++ qi/numeric/detail/real_impl.hpp (working copy) @@ -133,6 +133,7 @@ parse(Iterator& first, Iterator const& last, Attribute& attr, RealPolicies const& p) { + p.begin_parse(attr); if (first == last) return false; Iterator save = first; @@ -257,6 +258,7 @@ // If we got a negative sign, negate the number traits::assign_to(traits::negate(neg, n), attr); + p.end_parse(attr, true); // maybe this should return a bool and be the return value? // Success!!! return true; }

4 7

[intrusive] Compilation problem with gcc 4.7
by Hartmut Kaiser 07 Aug '13

07 Aug '13

In code which compiled just fine I'm now seeing: In file included from /opt/boost/trunk-debug/boost/intrusive/slist_hook.hpp:24:0, from /opt/boost/trunk-debug/boost/intrusive/slist.hpp:21, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/lcos/local/mu tex.hpp:23, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/runtime/compo nents/server/wrapper_heap.hpp:20, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/runtime/compo nents/server/managed_component_base.hpp:13, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/lcos/base_lco .hpp:12, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/lcos/base_lco _with_value.hpp:11, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/performance_c ounters/counters.hpp:12, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/runtime/compo nents/server/runtime_support.hpp:32, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/hpx/runtime.hpp:1 2, from /opt/buildbot/slave/hpx_gcc47_x8664_boosttrunk_debug/build/src/hpx_main.cpp: 7: /opt/boost/trunk-debug/boost/intrusive/detail/generic_hook.hpp: At global scope: /opt/boost/trunk-debug/boost/intrusive/detail/generic_hook.hpp:134:55: error: declaration of typedef struct boost::intrusive::hooktags<typename GetNodeAlgorithms::type::node_traits, Tag, LinkMode, BaseHookType> boost::intrusive::generic_hook<GetNodeAlgorithms, Tag, LinkMode, BaseHookType>::hooktags [-fpermissive] /opt/boost/trunk-debug/boost/intrusive/detail/generic_hook.hpp:84:8: error: changes meaning of hooktags from struct boost::intrusive::hooktags<typename GetNodeAlgorithms::type::node_traits, Tag, LinkMode, BaseHookType> [-fpermissive] Ion, could you fix this, please? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu

2 2

MinGW test failures
by Andrey Semashev 07 Aug '13

07 Aug '13

Hi, I can see that almost all MinGW tests (jc-bell.com runner) for trunk are failing, at least for Boost.Log [1] and Boost.Atomic [2]. However, test logs don't show any errors, only compiler warnings. Does anyone know what is the problem? Also, this is not the first time when I see no errors in logs while the test is marked as failed. This is really unhelpful. Are some logs being lost by the test running suite? [1] http://www.boost.org/development/tests/trunk/developer/log.html [2] http://www.boost.org/development/tests/trunk/developer/atomic.html

2 1

[predef] Boost detail/endian.hpp
by Rene Rivera 07 Aug '13

07 Aug '13

FYI.. I just tested, locally, and checked in the replacement for the "boost/detail/endian.hpp". This file is now non-BSL license free. If this is a header you rely on I would appreciate it if you could do your own testing to make sure it lives up to the previous header's functionality. Thanks, Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

2 1

Re: [boost] Removing old config macro and increasing compiler requirements.
by Brian Wood 07 Aug '13

07 Aug '13

Dave Abrahams wrote: >>on Tue Aug 06 2013, Brian Wood <woodbrian77-AT-gmail.com> wrote: >> >> I was going to ask for an update on these things, but this >> will do. I think it's just morass without an e. It sounds like >> it's time to reboot. I haven't followed this real closely, but >> know a lot of effort has gone into trying to preserve >> information in the conversion. That may be too much to ask. > > Boy, you really haven't been paying attention: that part is done. > Throwing out all that work at this point because you get the sense "it's > time to reboot" would be... well, pick your adjective. Too many are > flying through my brain right now to choose. I thought the use of the word morass was honest and putting it mildly. I'm not saying to abandon the goal. I recommend a modular approach, but it seems the years are passing without much happening. -- Brian Wood Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

1 0

Re: [boost] Removing old config macro and increasing compiler requirements.
by Brian Wood 07 Aug '13

07 Aug '13

Dave Abrahams wrote: > That's how Boost works. One of the ideas of the Git separation (and > hopefully eventual Ryppl) transition is to give maintainers more of a > sense of control over these things. I'm sure the commitment to quality > is there, but I think there's probably a lot of resignation over the > seemingly-intractable morasse. I was going to ask for an update on these things, but this will do. I think it's just morass without an e. It sounds like it's time to reboot. I haven't followed this real closely, but know a lot of effort has gone into trying to preserve information in the conversion. That may be too much to ask. -- Brian Wood Ebenezer Enterprises - So far G-d has helped us. http://webEbenezer.net

3 2

[mpl] at<> example bug?
by Mostafa 06 Aug '13

06 Aug '13

Looks like the example found here: http://www.boost.org/doc/libs/1_54_0/libs/mpl/doc/refmanual/at.html is buggy: BOOST_MPL_ASSERT_RELATION( (at< range, int_<0> >::value), ==, 10 ); It should be: BOOST_MPL_ASSERT_RELATION( (at< range, int_<0> >::type::value), ==, 10 ); Mostafa

3 3

How do folks test serialization code?
by John Maddock 06 Aug '13

06 Aug '13

Title almost says it all, how do you verify that your classes serialization code is truly platform independent, and doesn't accidently break later? I have some trivial tests that round trip to a stringstream using boost::archive::text_i/oarchive, but of course that only verifies that platform-specific serialization works. So what do folks do - generate text archives on different platforms, deserialize and compare? How does Boost.Serialization itself verify this? Cheers, John.

6 17

[git] Deleted file in detail module
by Daniel James 05 Aug '13

05 Aug '13

Hi, I just look in the detail module, and it contains this file: boost/functional/detail/container_fwd.hpp This file was deleted from trunk in r80288 and from release in r81356. https://svn.boost.org/trac/boost/changeset/80288 https://svn.boost.org/trac/boost/changeset/81356 Would it be possible to reflect that? Btw. I would have put it in functional, but that isn't a big deal. thanks, Daniel

2 1

[move] Documentation example typo.
by Jurko Gospodnetić 04 Aug '13

04 Aug '13

Hi. Just reporting a slight typo in boost::move library documentation's file_descriptor class example code for closing the OS file descriptor. It says: > if(!os_descr_) operating_system_close_file(os_descr_); in its destructor & assignment operator when it should in fact say: > if(os_descr_) operating_system_close_file(os_descr_); [notice the removed ! operator] Hope this helps. Best regards, Jurko Gospodnetić

2 1

[asio] condition_variable for coroutine-powered ASIO
by TONGARI J 04 Aug '13

04 Aug '13

Hi, Since Boost 1.54, ASIO introduced yield_context, which is very helpful to alleviate the pain of writing async ops. Unlike multi-threading, with cooperative multi-tasking, generally we don't have to worry about synchronization, but we still need some sort of mechanism to sync the coroutines in cases like producer-consumer for waiting the data... While I haven't seen any sync tool for asio/coroutine, having a condition_variable or such may be very useful, what do you think? Attached is the poor-man's implementation...

2 1

[timer] May I apply trivial fix?
by Antony Polukhin 03 Aug '13

03 Aug '13

Hi, As far as I know Beman is almost always busy, so may I apply trivial fix described in this ticket https://svn.boost.org/trac/boost/ticket/8956 ? This fix is essential for running regression tests with Intel compiler. -- Best regards, Antony Polukhin

5 6

[utility] [swap] How about Boost.Move?
by Antony Polukhin 03 Aug '13

03 Aug '13

Hi, Sources of Boost.Variant have a swap implementation that takes advantage of move emulation. That code can be useful for Boost.Swap. The idea is not to use std::swap in case of ADL failure, but use a swap implementation that is aware of move emulation: namespace boost_swap_impl { namespace swap_move_emulated { template <typename T> inline void swap(T& lhs, T& rhs) { T tmp( boost::move(lhs) ); lhs = boost::move(rhs); rhs = boost::move(tmp); } } template<class T> void swap_impl(T& left, T& right) { //using namespace std;//use std::swap if argument dependent lookup fails using namespace boost_swap_impl::swap_move_emulated; swap(left,right); } // ... With that code types that use move emulation can be swapped faster and even move only types can be swapped. So, what do the community think about such optimization? -- Best regards, Antony Polukhin

5 8

boost::lockfree::spsc_queue and destructors
by Taylor Holliday 03 Aug '13

03 Aug '13

Hey Boost, I was passing some shared_ptrs between threads using a boost::lockfree::spsc_queue and it would seem that the shared_ptr destructor isn't called upon popping from the queue. So spsc_queue differs from a typical queue in that regard. Why is that? thanks! - Taylor

2 1

[git-help] New libraries?
by Rene Rivera 03 Aug '13

03 Aug '13

Today I checked in the new Predef library and I'm wondering, not just for it but in general, if this interim period of svn to git transition what happens to new libraries? Will they automatically show up in the git repos? What are the procedures if the new library is already, originally in git and modularized? Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

3 5

Reboot of the boost server machine
by DongInn Kim 02 Aug '13

02 Aug '13

Dear All, For the system maintenance, we need to reboot the following server machines today. I am sorry for such a short notice. - milliways - eddie - wowbagger (Boost websites and mailing lists) - deep-thought (NFS server) Date: Aug 2, 2013 Time: 4:00pm-4:30pm (E.T.) - 1:00pm-1:30pm Pacific US time - 2:00pm-2:30pm Mountain US time - 3:00pm-3:30pm Central US time - 4:00pm-4:30pm Eastern US time - 8:00pm-8:30pm GMT The following services would not be available during the system maintenance. - Web services (e.g., www.boost.org) - Subversion (e.g., svn.boost.org) - mailing lists (e.g., boost(a)lists.boost.org, …) - Login to the NFS $HOME mounted system - Mail archives - Send mail - NFS Please let me know if you have any issues or questions about this sudden reboot. Regards, -- - DongInn

1 0

Suppressing boost.thread and boost.system symbols in shared library
by Philip Bennefall 02 Aug '13

02 Aug '13

Hi all, I am building a shared library for Linux, for which I would like to export as few symbols as possible (ideally only the functions that my library users actually need to call). When building my project, I have the following options: -fvisibility=hidden -fvisibility-inlines-hidden I then mark all the functions that I am exporting as having default visibility. I link to static versions of boost.thread and boost.system. When I then say: nm -DC libtest.so I get a large number of symbols such as: 0002abe0 V typeinfo name for boost::exception_detail::clone_impl<boost::exceptio n_detail::bad_exception_> 0002ace0 V typeinfo name for boost::exception_detail::bad_exception_ 00029920 V typeinfo name for boost::exception_detail::error_info_injector<boost: :lock_error> 00029b00 V typeinfo name for boost::exception_detail::error_info_injector<boost: :condition_error> 00029860 V typeinfo name for boost::exception_detail::error_info_injector<boost: :thread_resource_error> 0002970f V typeinfo name for boost::thread_exception 00029a7b V typeinfo name for boost::thread_interrupted 00029740 V typeinfo name for boost::thread_resource_error 0002ac40 V typeinfo name for boost::enable_shared_from_this<boost::detail::threa d_data_base> 0002a720 V typeinfo name for boost::detail::thread_data_base 0002ad20 V typeinfo name for boost::detail::sp_counted_impl_p<boost::detail::thr ead_data_base> 0002adc0 V typeinfo name for boost::detail::sp_counted_impl_p<boost::exception_d etail::clone_impl<boost::exception_detail::bad_alloc_> > 0002ad60 V typeinfo name for boost::detail::sp_counted_impl_p<boost::exception_d etail::clone_impl<boost::exception_detail::bad_exception_> > 000296f1 V typeinfo name for boost::system::system_error I see this after having stripped the binary. Is there any way to get rid of these? Do I need to build Boost with some special cxxflags? Kind regards, Philip Bennefall

3 6

[predef] FYI..
by Rene Rivera 01 Aug '13

01 Aug '13

FYI.. to those that care.. I checked in changes to SVN to inject the Predef library into Boost. I say inject because the source is not actually in the SVN repo, it's external and still in github. But is being brought in through their SVN interface. Some testers have already runs the tests for it.. And at some point to be determined with some coordination with the community I will switch the "boost/detail/endian.hpp" header to point to the Predef compatibility equivalent... I suspect at the earliest one more week for that assuming no problems surface. Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

6 10

[predef] A few questions
by Andrey Semashev 01 Aug '13

01 Aug '13

Hi, I have a few questions/nitpicks regarding Boost.Predef: - I see that all headers have extension .h. Why is it not .hpp, like with the rest of Boost? It this intentional? - There is a tab in predef/version_number.h. There are also tabs in tests. - There are __SunOS_5_10, __SunOS_5_11 and similar macros defined on Solaris, which allow to detect OS version. These are not always available but I think SunPro defines them. Could these macros be used to select the proper OS version? - If I'm not mistaken, BOOST_COMP_GNUC and BOOST_COMP_MSVC will get defined not only for the real GCC and MSVC but also for pretenders. Is this intentional? If so, could we have special macros to detect these particular compilers? Boost.Config defines BOOST_MSVC and BOOST_GCC for this purpose. - There is considerable overlap with Boost.Config. Is there any plan to reduce the duplication? Maybe move some things from Boost.Config to Boost.Predef?

3 2

[boost.thread] Trouble building with MinGw 4.7.0
by Philip Bennefall 01 Aug '13

01 Aug '13

Hi all, Up until now I have been developing exclusively with VC++ 2010, and there my project builds just fine and without warnings. However, I am also planning to target Unix so I figured that a first step would be to make sure my project builds with MinGw. I set up my path environment variable to include the location of the MinGw 4.7.0 bin directory, and I built Boost with the following parameters: b2 variant=release link=static runtime-link=static threading=multi toolset=gcc Everything seems to be working fine (stage/lib contains all the .a files that I would expect). However, when I attempt to build my program I get tons of errors like the following: myprog_main.o:myprog_main.cpp:(.text+0x28ef): undefined reference to `__imp___ZN5boost6thread9interruptEv' myprog_main.o:myprog_main.cpp:(.text+0x294f): undefined reference to `__imp___ZNK5boost6thread6get_idEv' myprog_main.o:myprog_main.cpp:(.text+0x295d): undefined reference to `__imp___ZN5boost11this_thread6get_idEv' myprog_main.o:myprog_main.cpp:(.text+0x2973): undefined reference to `__imp___ZN5boost6thread13join_noexceptEv' myprog_main.o:myprog_main.cpp:(.text+0x2981): undefined reference to `__imp___ZN5boost6thread6detachEv' myprog_main.o:myprog_main.cpp:(.text+0x4600): undefined reference to `__imp___ZN5boost11this_thread18interruptible_waitEPvNS_6detail7timeoutE' myprog_main.o:myprog_main.cpp:(.text+0x49c2): undefined reference to `__imp___ZN5boost11this_thread18interruptible_waitEPvNS_6detail7timeoutE' myprog_main.o:myprog_main.cpp:(.text+0x667e): undefined reference to `__imp___ZN5boost11this_thread18interruptible_waitEPvNS_6detail7timeoutE' myprog_main.o:myprog_main.cpp:(.text+0x90a9): undefined reference to `__imp___ZN5boost6thread21start_thread_noexceptEv' myprog_main.o:myprog_main.cpp:(.text+0x9134): undefined reference to `__imp___ZN5boost6thread21start_thread_noexceptEv' myprog_main.o:myprog_main.cpp:(.text+0x917e): undefined reference to `__imp___ZN5boost6thread9interruptEv' myprog_main.o:myprog_main.cpp:(.text$_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvPFvPN5myprog5themeEENS2_5list1INS2_5valueIS6_EEEEEEED1Ev[boost::detail::thread_data<boost::_bi::bind_t<void, void (*)(myprog::theme*), boost::_bi::list1<boost::_bi::value<myprog::theme*> > > >::~thread_data()]+0x7): undefined reference to `__imp___ZN5boost6detail16thread_data_baseD2Ev' myprog_main.o:myprog_main.cpp:(.text$_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvPFvPN5myprog5themeEENS2_5list1INS2_5valueIS6_EEEEEEED0Ev[boost::detail::thread_data<boost::_bi::bind_t<void, void (*)(myprog::theme*), boost::_bi::list1<boost::_bi::value<myprog::theme*> > > >::~thread_data()]+0xe): undefined reference to `__imp___ZN5boost6detail16thread_data_baseD2Ev' myprog_main.o:myprog_main.cpp:(.text$_ZN5boost6threadD1Ev[boost::thread::~thread()]+0x9): undefined reference to `__imp___ZN5boost6thread6detachEv' Etc... I tried to specify -DBOOST_NO_LIB and add all the libraries manually, but no luck. Then I thought that maybe there's a problem with the fact that there are spaces in some of my directory names, so I copied the relevant .a files to the same directory as the program itself but still with no success. At this point, I'm swamped. I have managed to compile MinGw programs in the past that used Boost Thread, so I have no idea why it is not working with this version of Boost. Any suggestions would be highly appreciated. Kind regards, Philip Bennefall

2 5

Re: [boost] [multimethods] Proposal: Open Multi-Methods
by Daryle Walker 01 Aug '13

01 Aug '13

//================================================================= From: Jean-Louis Leroy Sent: ‎Saturday‎, ‎July‎ ‎27‎, ‎2013 ‎8‎:‎26‎ ‎PM I am working on library that pretty much implements what Pirkelbauer, Solodkyy and Stroustrup describe in their paper "Open Multi-Methods for C++" - although there are some divergences. I have posted it on GitHub: https://github.com/jll63/multimethods. Please examine the files in the "examples" directory to get an idea of how to use it. [SNIP] The library is essentially feature complete (if anything ever is). I am now going to work on the documentation, a build system, some clean up and compatibility (I tested it only with g++ 4.7.2 only so far). Is there interest in the Boost community for this stuff? If yes, I will adapt it to the guidelines and submit it for formal review. Of course, suggestions are welcome. //================================================================= Are virtual base classes supported? Maybe “virtual_” should be renamed to “virtualize” or “virtualized,” to avoid having a trailing underscore in a non-member name. A good way to document is to write a Doxygen comment as you write your class, function, or macro prototype. It makes you have to think about what the public side of your code has to do. But looking at your “next.cpp” example, you should start with documenting the “selector,” “virtual_,” “MM_CLASS,” “MM_INIT,” “MULTIMETHOD,” “BEGIN_METHOD,” “END_METHOD,” and “initialize” items. Anything in your implementation classes that don’t have to be seen by public code can be make private. Non-public types can go in a detail namespace. Daryle W.

3 2

[boost thread] Catching interrupted exception?
by Philip Bennefall 31 Jul '13

31 Jul '13

Hi all, I have a quick question regarding the interruption of Boost threads. I am making fairly heavy use of the interrupt method call of the thread class, and I am wondering whether I should be catching the boost::thread_interrupted exception from within my thread function? I currently do not and my program runs fine, but I am wondering whether this is defined behavior or whether I should always be catching the exception and returning from the function inside the handler? Kind regards, Philip Bennefall

2 2

Re: [boost] [asio] Randomly having problems reading from the socket
by Marat Abrarov 30 Jul '13

30 Jul '13

> Posted a Bug Report here: Ticket #8937 > <https://svn.boost.org/trac/boost/ticket/8937> Seems like a bug/feature of Windows 7/Vista (or a bug/feature of Windows socket subsystem) - something in background/foreground process scheduling or a memory management issue. Nevertheless it is interesting to know the Asio author's point of view. It will be more clear if the topic starter rewrites his (simple) examples to use WinSock directly rather than through the Asio (use the same time measurement - by means of boost::posix_time). I think that such rewritten examples will show the same behavior. Regards, Marat Abrarov.

1 0

[preprocessor] ARRAY_REPLACE bug?
by Mostafa 30 Jul '13

30 Jul '13

On Windows 7/Cygwin, using boost 1.53, preprocessing the following snippet: pp_array.cc ----------- #include <boost/preprocessor.hpp> //#define BOOST_PP_TUPLE_REM_0() // nothing #define ARRAY (3, (a, x, c)) BOOST_PP_ARRAY_REPLACE(ARRAY, 1, b) via: g++ -E -P -I /... pp_array.cc gives the following incorrect result: (3, (BOOST_PP_TUPLE_REM_0 () a, b , c)) Uncommenting the pound define in the snippet gives the correct result for the preprocessor. Is this a bug?

3 5

[type_erasure] move
by Christophe Henry 29 Jul '13

29 Jul '13

Hi Steven, I'm looking for a crash I get in my own code with g++4.8.1 (4.5 - 4.7 are ok). Maybe you can help me: - there is a copy_constructible concept, but no moveable. Is it enough to add one on the same model? It looks like you std::forward so I'd say yes. Correct? template<class T = _self> struct move_constructible : ::boost::mpl::vector<constructible<T(T&&)>, destructible<T> > {}; - If I std::move a copy_constructible any type by accident, what do I get? A copy? A crash? Thanks, Christophe

2 2

Re: [boost] [asio] Randomly having problems reading from the socket
by FlorianGeorge 29 Jul '13

29 Jul '13

Posted a Bug Report here: Ticket #8937 <https://svn.boost.org/trac/boost/ticket/8937> -- View this message in context: http://boost.2283326.n4.nabble.com/asio-Randomly-having-problems-reading-fr… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

New failing tests in circular buffer on some platforms
by Paul A. Bristow 29 Jul '13

29 Jul '13

I note that there are some new failing tests for circular buffer on some platforms http://www.boost.org/development/tests/trunk/developer/circular_buffer.html on MSVC noncopyable_movable_noexcept_t is causing trouble base_test.cpp C:\boost_regression\trunk\boost\boost/circular_buffer/base.hpp(694) : error C2558: struct 'noncopyable_movable_noexcept_t' : no copy constructor available or copy constructor is declared 'explicit' C:\boost_regression\trunk\boost\boost/circular_buffer/base.hpp(673) : while compiling class template member function 'noncopyable_movable_noexcept_t *boost::circular_buffer<T>::linearize(void)' with [ T=noncopyable_movable_test_t ] c:\boost_regression\trunk\boost\libs\circular_buffer\test\common.ipp(2160) : see reference to function template instantiation 'noncopyable_movable_noexcept_t *boost::circular_buffer<T>::linearize(void)' being compiled with [ T=noncopyable_movable_test_t ] c:\boost_regression\trunk\boost\libs\circular_buffer\test\common.ipp(2236) : see reference to class template instantiation 'boost::circular_buffer<T>' being compiled with [ T=noncopyable_movable_test_t ] C:\boost_regression\trunk\boost\boost/circular_buffer/base.hpp(697) : error C2558: struct 'noncopyable_movable_noexcept_t' : no copy constructor available or copy constructor is declared 'explicit' ON gcc and Clang there are warnings and failure Running 60 test cases... ../libs/circular_buffer/test/common.ipp(2303): error: in "check_containers_exception_specifications": check boost::has_nothrow_constructor<circular_buffer<int> >::value has failed Can any experts shed light on this? I do not believe that the underlying circular buffer code has changed recently. Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

2 2

[thread] Questions about broken_promise
by Klaim - Joël Lamotte 29 Jul '13

29 Jul '13

I have a few questions concerning broken promises (exception): 1. is the broken_promise exception a standard, or future standard behaviour? So far I assumed it wasn't because http://en.cppreference.com/w/cpp/thread/promise/~promise don't say anything about this and I only read about broken_promise exceptions on Boost.Thread documentation. I would like to know if I should expect the future standard library to have the same concept. I see no configuration macro to deactivate these exceptions. I don't want to actually, but if I'm correct that it's not standard or future standard, then it's surprising that I can't setup a standard-like setup. 2. I have a case that could be summarized like this: ///////////////////////////////////////////// Updated by thread A: struct X { /*... */ }; struct K { future<shared_ptr<X,U>> m_ft_x; shared_ptr<X,U> m_x; K( Foo& foo ) : m_ft_x( foo.create<X>() ) {} void update() // this is always called by a loop in the thread A { if( !m_x ) { if( m_ft_x.has_value() ) m_x = m_ft_x.get(); } else work(); } void work(); // uses m_x }; Updated by thread B: // special deleter which will just push a task in Foo work queue for deleting the object // in sync with thread B struct U { /* ... */ }; struct Foo { template< class T > future<shared_ptr<T,U>> create() // will push a creation task in a work queue updated in update() void update(); // called by a loop in the thread B, will execute all the work pushed in the work queue. }; ///////////////////////////////////////////// (this is an exageratedly simplified version of what I'm doing) It works nicely (even if I think it could be improved with future.then and other tools) but there is a minor problem appearing when an instance of K is constructed then almost immediately destructed, before the instance of Foo executed the creation of the X instance. In this case, visual studio (which is configured to detect all throw calls) detect a broken_promise exception thrown from the destructor of the promise which was in the code generated by Foo::create() and pushed in a work queue. I look at the destructor and I see: if(!future_->done && !future_->is_constructed) { future_->mark_exceptional_finish_internal(boost::copy_exception(broken_promise()), lock); } Here is the full copy_exception code: template <class T> inline exception_ptr copy_exception( T const & e ) { try { throw enable_current_exception(e); } catch( ... ) { return current_exception(); } } This code triggers actually two "first-chance" exceptions this is the first one) which are catch immediately intentionally. My question is: why is copy_exception necessary and why does it have to do it this way? It's a very minor problem as just re-setting my visual studio debugging settings to default makes the exception transparent -only visible in the console log. However each time I activate debug breaking on all c++ exception so that I can debug some potential issues, I can have a breakpoint which is actually "noise" as it is only used to implement a copy of exception. Is it possible to eliminate this noise? Or, as I'm guessing, is there a language or compiler limitation which forces this code to be written this way? Thanks for your time. Joel Lamotte

2 2

safe bool not safe enough ?
by John Maddock 28 Jul '13

28 Jul '13

Just discovered (oops!) that the so called safe bool ideom is not as safe as it appears, for example: class Testable { bool ok_; typedef void (Testable::*bool_type)() const; void this_type_does_not_support_comparisons() const {} public: explicit Testable(bool b=true):ok_(b) {} operator bool_type() const { return ok_==true ? &Testable::this_type_does_not_support_comparisons : 0; } }; Testable t(true); bool b = t; // Compiles OK - Ooops! Which is causing multiprecision to misbehave when used in conjunction with uBlas: https://svn.boost.org/trac/boost/ticket/8292#comment:2 I guess making the conversion explicit in C++11 mode would help (I still need to test that), but is there a C++03 solution? Thanks, John.

4 9

radix sort
by Sourav 28 Jul '13

28 Jul '13

Hi All, I wanted to know if someone is/was working on Radix Sort or not. I did check the SoC listings and did not see radix sort in the list. If no one is working, may someone help me provide some pointers/details as to what the expectation is with regards to Radix sort for boost ? Regards, -Sourav

7 27

boost::python help?
by David M. Cotter 26 Jul '13

26 Jul '13

i'd like my app to be "available" to python while it's running. for example, say my app is "FooBar.app". when my FooBar.app is running, now there is a python interface available to python, and the user can write python scripts to make use of it with their scripts, they can control my running application when FooBar.app is NOT running, perhaps making use of any of the python functions of "FooBar.app" would either return an error, or possibly launch "FooBar.app". can boost::python help with this? i've never worked with extending or embedding python, so any help would be super great

4 5

Patch bonanza for VS2013 Preview support
by Lars Viklund 25 Jul '13

25 Jul '13

Hi list. What's the best way to spend your vacation if not trying to get Boost to build on bleeding-edge compilers. I set out to see how well Boost 1.54.0 behaved on the newly released go-live-ready Visual Studio 2013 Preview. Below is the list of bugs filed against Boost and Microsoft. Enjoy. With these patches in place, I can get a complete build working with all libraries normally available on a fresh machine (means that I didn't test Python, MPI, ICU, compressed streams). I haven't been able to find out how to run the tests in any human-readable form, but this should not cause any regressions as it's either increasing workaround bounds or adding headers that the standard mandates already. Boost.Config VS2013 Preview version bump https://svn.boost.org/trac/boost/ticket/8753 The Visual Studio 2013 Preview toolchain has _MSC_VER 1800 and _MSC_FULL_VER 180020617. See the attached patch for the minimum changes that are needed to get anywhere at all. Boost.Build needs support for the VS2013 Preview toolset (18.00.20617.1) https://svn.boost.org/trac/boost/ticket/8754 Visual Studio 2013 Preview is out and claims to be 12.0. I copy-pasted everything related to 11.0 to refer to 12.0 and it Works On My Machine, see attached patch. Boost.Signals VS2013 Preview version bump https://svn.boost.org/trac/boost/ticket/8755 The BOOST_WORKAROUND macros at boost/signals/detail/named_slot_map.hpp:130 and libs/signals/src/named_slot_map.cpp:27 needs to be increased to <= 1800 in order to encompass the Visual Studio 2013 Preview compiler. Boost.MPL VS2013 Preview version bump https://svn.boost.org/trac/boost/ticket/8756 The BOOST_WORKAROUND macros at boost/mpl/assert.hpp lines 37 and 247 need to be changed to also consider BOOST_MSVC, == 1800, patch attached. Boost.Serialization lacks algorithm header include for std::min https://svn.boost.org/trac/boost/ticket/8757 The <algorithm> header providing std::min is not included in boost/archive/iterators/transform_width.hpp, this breaks on Visual Studio 2013 Preview due to library changes. Boost.Asio lacks algorithm header include for std::min https://svn.boost.org/trac/boost/ticket/8758 The <algorithm> header providing std::min is not included in boost/asio/detail/impl/win_iocp_io_service.hpp, this breaks on Visual Studio 2013 Preview due to library changes. std::bind broken with boost/tuple/tuple.hpp or anything else providing a ADL tie https://connect.microsoft.com/VisualStudio/feedback/details/792163/std-bind… Not our fault, I filed a bug on Connect and am hoping that they'll notice it before RTM. 'std::bind' finds our 'tie' if a type from a boost namespace is used in the 'std::function' argument type list. -- Lars Viklund | zao(a)acc.umu.se

13 35

[preprocessor] ARRAY_REPLACE bug?
by Mostafa 25 Jul '13

25 Jul '13

On Windows 7/Cygwin, using boost 1.53, preprocessing the following snippet: pp_array.cc ----------- #include <boost/preprocessor.hpp> //#define BOOST_PP_TUPLE_REM_0() // nothing #define ARRAY (3, (a, x, c)) BOOST_PP_ARRAY_REPLACE(ARRAY, 1, b) via: g++ -E -P -I /... pp_array.cc gives the following incorrect result: (3, (BOOST_PP_TUPLE_REM_0 () a, b , c)) Uncommenting the pound define in the snippet gives the correct result for the preprocessor. Is this a bug?

1 0

[dynamic_bitset] Compiler intrinsics to accelerate. whos agree?
by Jairo Andres Velasco Romero 25 Jul '13

25 Jul '13

I noted detail for dynamic_bitset<> is not using the far old ASM instruction BSF which could accelerate find_first() and find_next() methodsI checked asm generated with current table based implementation.On x64 and x86 BSF and BSR are available long time ago.Population count can be implemented with LZCNT for performance oriented ways to build.Core i7 with AVX2 enable new wide block bit manipulation but it needs to code with specific GNU g++ intrinsics and MSVC intrinsics. Someone agree? Jairo.

2 1

semi lock-free Signals/Slots
by Andrew Ho 24 Jul '13

24 Jul '13

Hi, I've been doing some testing with implementing a semi lock-free Signals/Slots library. Basically: 1. emits are lock-free thanks to atomic shared_ptr's/other atomic operations. 2. Only a single writer is allowed at a time, uses a mutex for locking. The primary goal is to improve low and no slot-count signal emit performance. In tests, I have been able to get substantial performance boosts (~2 to 5 times) on low slot-count signals, approaching the same performance as signals2 in low-contention (basically, single thread testing). I haven't tested high emit contention performance, though I suspect this library will excel quite well here because there is no locking on emit. The test implementation is still incomplete, and notably uses many C++11 features, though I don't think any of features I'm using can't be ported one way or another for C++03 support. Even if the library isn't used in full, some of the ideas might be implemented into the existing Signals2 library. link: https://github.com/helloworld922/signals3

2 2

Announcing boost dependency analyzer
by Jens Weller 24 Jul '13

24 Jul '13

Hello to the boost community, I'd like to announce the release of a small tool, that allows you analyze the dependencies in boost. It is based on bcp, requirement is that you have bcp build and well a version of boost to analyze installed. Simply select the boost directory (the tool also might find BOOST_ROOT) and the location of bcp, and the tool will start. This will take a little time, depending on your machine, on my multicore intel ist 90 seconds - 2 minute. The tool will store this information into a database, so that with the next start, this will be a lot shorter. The tool allows to analyze the dependcies of a single boost library, but also of all of boost. Its build with Qt for the UI and processing part, and uses boost graph for the layout. Full information + download you'll find at my blogpost: http://www.meetingcpp.com/index.php/br/items/boost-dependency-analyzer.html Current Issues: What libraries might be missing? I'm reading the libs from maintainers.txt, which isn't all the boost libs. For example, lexical_cast is missing, and function_types is twice in there. (C&P error or missing library?) So far Windows is supported, linux support planned and improving, currently ownly the (beta) binaries for linux available. kind regards, Jens Weller

5 9

Re: [boost] [build][msvc] create PDBs
by Ahmed Charles 24 Jul '13

24 Jul '13

The size difference is LTCG, not debug info. ________________________________ From: Daniela Engert Sent: 7/23/2013 9:40 AM To: boost(a)lists.boost.org Subject: Re: [boost] [build][msvc] create PDBs Am 23.07.2013 17:47, schrieb Andrey Semashev: > On Tue, Jul 23, 2013 at 7:39 PM, Daniela Engert <dani(a)ngrt.de> wrote: >> >> libboost_log_setup-vc120-mt-1_54.lib 188.671.120 >> libboost_log_setup-vc120-mt-1_54.pdb 132.616.192 >> libboost_log_setup-vc120-mt-gd-1_54.lib 220.099.308 >> libboost_log_setup-vc120-mt-gd-1_54.pdb 132.837.376 >> libboost_log-vc120-mt-1_54.lib 53.565.446 >> libboost_log-vc120-mt-1_54.pdb 7.942.144 >> libboost_log-vc120-mt-gd-1_54.lib 32.516.250 >> libboost_log-vc120-mt-gd-1_54.pdb 8.114.176 >> > > It looks like static libs contain debug info anyway as they are always > larger than the generated pdb. In many cases, your observed size relationship is true, but not in all of them. E.g.: libboost_exception-vc120-mt-1_54.lib 53.642 libboost_exception-vc120-mt-1_54.pdb 102.400 libboost_exception-vc120-mt-gd-1_54.lib 11.440 libboost_exception-vc120-mt-gd-1_54.pdb 102.400 To exhibit the size advantage of PDBs over 'old-style' debug info embedded into static libs, I've rebuilt Boost.Log with link=static debug-store=object. This is the result: libboost_log_setup-vc120-mt-1_54.lib 343.234.460 libboost_log_setup-vc120-mt-gd-1_54.lib 374.488.888 libboost_log-vc120-mt-1_54.lib 79.564.296 libboost_log-vc120-mt-gd-1_54.lib 59.539.544 Ciao Dani _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

clang AST based static analysers - Booster's experience
by Niall Douglas 23 Jul '13

23 Jul '13

Dear Boost Devs, I was wondering what the experience of the list is with clang AST based static analysers? They need not be clang AST based of course, so long as they are based on the frontend of a real compiler rather than trying their own implementation based on regex or something even worse. For this list's information, here are the three clang AST based static analysers I know of: 1. Clang's static analyser http://clang-analyzer.llvm.org/ 2. OCLint http://oclint.org/ 3. The commercial tool CppDepend can now use a clang AST (http://blog.llvm.org/2013/04/static-analysis-tools-using-clang-in.html) Some quick notes of mine which may be of dubious accuracy: Clang's static analyser is the more mature tool, but according to http://code.google.com/p/chromium/wiki/ClangStaticAnalyzer which was updated Mar 2013 it feels its default bundled C++ tests is lacking. The real strength in the clang static analyser is for writing your own tests (http://clang-analyzer.llvm.org/checker_dev_manual.html) which enforce specific coding patterns or constraints (usually on others, and usually pre-commit with commit rejection if fail). OCLint is a newer tool, but appears to have fuller support for C++ (http://docs.oclint.org/en/dev/rules/index.html) though many of those rules appear to check C syntax only (which also covers Objective C). Similar to clang's static analyser, new custom rules are easy to write (http://docs.oclint.org/en/dev/internals/rules.html) This project, at least from the outside, seems to have more legs than clang's static analyser. CppDepend I have no experience of, but there is a reasonably positive review at http://www.asawicki.info/news_1511_cppdepend.html. One of the CppDepend developers talks about how they added clang's AST at http://www.codeproject.com/Articles/475254/ClangplusRocks. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

1 0

[build][msvc] create PDBs
by Daniela Engert 23 Jul '13

23 Jul '13

Hi list! For various reasons I always preferred to have debug info separate from the binaries. Unfortunately, emitting debug info to PDBs doesn't work so well, in particular when it comes to static libs and precompiled headers. Because of that I tried to rectify this and created a patch against msvc.jam. (see ticket #8889 https://svn.boost.org/trac/boost/ticket/8889) This (and a tiny script to collect all generated PDBs into the library directory) got me there: boost_log_setup-vc120-mt-1_54.dll 1.158.656 boost_log_setup-vc120-mt-1_54.lib 24.244 boost_log_setup-vc120-mt-1_54.pdb 123.055.104 boost_log_setup-vc120-mt-gd-1_54.dll 3.206.144 boost_log_setup-vc120-mt-gd-1_54.lib 24.408 boost_log_setup-vc120-mt-gd-1_54.pdb 219.220.992 boost_log-vc120-mt-1_54.dll 486.400 boost_log-vc120-mt-1_54.lib 241.174 boost_log-vc120-mt-1_54.pdb 10.857.472 boost_log-vc120-mt-gd-1_54.dll 1.071.616 boost_log-vc120-mt-gd-1_54.lib 242.278 boost_log-vc120-mt-gd-1_54.pdb 18.918.400 libboost_log_setup-vc120-mt-1_54.lib 188.671.120 libboost_log_setup-vc120-mt-1_54.pdb 132.616.192 libboost_log_setup-vc120-mt-gd-1_54.lib 220.099.308 libboost_log_setup-vc120-mt-gd-1_54.pdb 132.837.376 libboost_log-vc120-mt-1_54.lib 53.565.446 libboost_log-vc120-mt-1_54.pdb 7.942.144 libboost_log-vc120-mt-gd-1_54.lib 32.516.250 libboost_log-vc120-mt-gd-1_54.pdb 8.114.176 Boost.Log was chosen for exhibition only. All files were built with debug-symbols=on debug-store=database. Link-time code generation was enabled for all release builds, too. May be, someone finds this helpful. Ciao Dani

2 2

[format] doc fix
by Tim Blechmann 23 Jul '13

23 Jul '13

not sure, how well-maintained boost.format is these days ... any objection if i commit this documentation fix? cheers, tim

1 0

Fwd: Re: Announcing boost dependency analyzer
by Stephen Kelly 23 Jul '13

23 Jul '13

Jens Weller wrote: >> Unfortunately the Boost dependency graph is as huge a hairball as I was >> afraid :-/ > > Hi, thanks for the feedback. Yes, dependency graph for boost is quite > large... I think with boost in git and modules available, this is going to > improve. That won't happen automatically. The git conversion is separate to reorganizing to resolve the solvable interdepency issues: http://thread.gmane.org/gmane.comp.programming.tools.ryppl.devel/201/focus=… The salient point is: > By modularizing and making the interdependencies explicit, we hope to > encourage developers to refactor. But we can only solve one problem at a > time. So, if you want to work on resolving interdependencies, don't wait for the git conversion to be done, because it won't help, and do pick up your editor and dig, because only that will help. Thanks, Steve.

1 0

Regression tests report page cycling slow
by Joaquin M Lopez Munoz 23 Jul '13

23 Jul '13

Hi, the page http://www.boost.org/development/tests/trunk/developer/summary.html seems to update very unfrequently, every two days or longer. Can something be done to speed this up? Thank you in advance, Joaquín M López Muñoz Telefónica Digital

2 1

Requesting number crunchers for trial complex classes
by Daryle Walker 22 Jul '13

22 Jul '13

I just pushed out commit "aaeabbd3fcc04956c4fd3d3825f6202355ab9297" of my trial hypercomplex number classes at https://github.com/CTMacUser/Complex. The classes now have all the arithmetic operators. They already have the condition functions (norm and conj), norm functions (taxi (ex L1), abs, sup, and sgn), and equality operators. There is an output operator, but not input. There are constructors for: default (both garbage bits and all zeros), copy and move (automatically defined), component (single or list), cross version, smaller hypercomplex (single and list), and (head of) larger hypercomplex. Look at the unit tests for usage examples. I haven't done any utility or transcendental functions yet, so let me know if you need them before proceeding. I just want people who do hard-core number crunching with complex, quaternion, and/or octonion numbers to see if my classes are worth it, performance-wise. You can also use the array-of-hypercomplex to array-of-many-reals reinterpret_cast trick. Everything should have Doxygen comments. I run this code on GCC 4.7.1 off MinGW for 32-bit Windows 8 Pro, so tests on other compilers will be appreciated. (It probably can't run on Visual C++, but GCC 4.8 and Clang 3.x will probably work.) Note on octonions: a month ago I found out, while looking for online octonion calculators, that octonion (and above) multiplication isn't standardized. I'm using the same philosophy from Wikipedia, which is also used by the existing Boost.Octonion. (Actually, I found a bug in B.O.'s octonion times quaternion code, since that author manually lists all the sub-terms, and my code is more automatic. I had to do the multiplication by hand to check who had it right.) So if your octonion products are different, it may not be a bug. I've tried to make as many constructors/operators/functions constexpr as possible. (That's why no std::initializer_list.) That may help move data into ROM, but you have to force non-inline-ness when you need to test runtime performance. Daryle W.

1 0

[Locale] does generator("") deliver the system's default locale?
by Michael Schinner 22 Jul '13

22 Jul '13

boost 1.54.0 When I use boost::locale::generator and generator("") I get different results for the decimal point than using std::locale(""). Boths methods are supposted to deliver the system's default locale. Example: // windows 7, de_AT std::use_facet<std::numpunct<char> >(std::locale("")).decimal_point(); // delivers a , boost::locale::generator generator; std::use_facet<std::numpunct<char> >(generator("")).decimal_point(); // delivers a . What does generator("")) deliver? Is it wanted that a '.' is deliverd as decimal point for a german locale? Best regards, Michael

2 1

[system] Do we need this library with latest (almost C++0x) compilers?
by Tonko Juricic 22 Jul '13

22 Jul '13

Can somebody please explain what is missing in current compiler implementations? What is preventing other libraries to have a macro like: #ifdef _CPP11_THREAD_ #include <thread> #include <mutex> #include <condition_variable> #else #include <boost/thread.hpp> #include <boost/thread/mutex.hpp> #include <boost/thread/condition_variable.hpp> #endif also when it comes to error codes and conditions? Thanks, Tony

3 2

windows_shared_memory - does memory block exists?
by piotr.ns 21 Jul '13

21 Jul '13

Hi, Why native windows shared memory does not include any means to check for existance of memory block without throwing exceptions? A small function would be enough: // boost::interprocess::windows_shared_memory static bool exists(const std::string &a_path) { using namespace boost::interprocess; try { unsigned long file_map_access = winapi::page_readonly; unsigned long map_access = winapi::file_map_read; void *test_handle = winapi::open_file_mapping(map_access, a_path.c_str()); bool res = (test_handle != NULL); if(res) winapi::close_handle(test_handle); return res; } catch(...) { return false; } } Without this I have to use Boost internals (winapi::*) in my application. Would somebody consider including this code or something similar? Regards, Piotr

1 0

Status of various Boost initiatives?
by Robert Ramey 21 Jul '13

21 Jul '13

I'm trying to get a handle on the current state of the various boost migrations which have been underway. a) migration to GIT b) migration to CMake c) status of rypll when I try to track this down I find many dead links, repeated information. I also don't find some blogs I used to be able to find on these subjects. Anyone up to provide an current status snapshot? Robert Ramey

5 14

Mag Gam
by Mag Gam 21 Jul '13

21 Jul '13

http://yumaonline.it/bau/bcjk.xvdhjqpdiniqwmxf Mag Gam 7/21/2013 7:26:51 AM

1 0

Re: [boost] [regression] patch for running tests in parallel and out-of-sync files
by Robert Kawulak 20 Jul '13

20 Jul '13

> From: Robert Kawulak > When I was running tests in parallel (using b2 -j option) I was getting random > warnings in the results table because "msvc.manifest" lines were interleaved with > compile/link actions. I've fixed this with the attached patch - is it OK to apply > it to trunk/release? Due to the lack of feedback I've gone ahead and applied the fix in trunk for now. If nobody objects or reports issues, I'll merge it into release later. > BTW, I've noticed that the following files in tools/regression/src haven't been > updated in release branch even though they've been changed in trunk a long time > ago: > compiler_status.cpp (trunk date 2012-01-21, release date 2011-10-06) > library_status.cpp (trunk date 2013-03-25, release date 2013-03-09) > Is it OK to update these in release branch? Likewise, I've updated the two files in release. I've also added tools/regression/build/bin directory to ignore list (it's created when invoking b2 from tools). Best regards, Robert

1 0

[git conversion] type_traits problems; spurious headers
by Beman Dawes 20 Jul '13

20 Jul '13

libs/type_traits/include/boost has these files: aligned_storage.hpp call_traits.hpp config.hpp smart_ptr.hpp timer.hpp type_traits.hpp utility.hpp AFAIK, call_traits.hpp and type_traits.hpp are supposed to be there, but the rest are spurious, and are causing "b2 headers" to create some incorrect links that are preventing testing many libraries. --Beman

2 1

[git-help] Status?
by Rene Rivera 20 Jul '13

20 Jul '13

I started looking at making the final minor set of changes to the regression testing scripts to have the option of testing the modular git version of the boost super-project. Unfortunately it now seems that the super-project no longer has *any* of the references to the library sub-projects. Me not being able to get this work done now is rather annoying as it likely means that the testing will not be ready early in the 1.55 release cycle. Which is the release currently scheduled to switch to git. What is the status of the git transition? When will the Boost release team be able to start working on the switch? Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

5 11

Re: [boost] A more convenient Variant visitation syntax
by Charlls Quarra 19 Jul '13

19 Jul '13

________________________________ De: Dave Abrahams <dave(a)boostpro.com> Para: boost(a)lists.boost.org Enviado: sábado, 14 de abril de 2012 22:49 Asunto: Re: [boost] A more convenient Variant visitation syntax on Sat Apr 14 2012, Thomas Heller <thom.heller-AT-googlemail.com> wrote: > On Sat, Apr 14, 2012 at 5:41 PM, Mathias Gaunard > <mathias.gaunard(a)ens-lyon.org> wrote: >> On 14/04/12 17:00, Kevin Wu Won wrote: >>> >>> This is C++11 only because it's quite pointless without lambda >>> functions. I've tested it with gcc 4.7. It doesn't work on gcc 4.6, >>> which can't handle the variadic templates. >> >> >> It can be done in C++03 and expression-template-based lambdas just fine as >> well. >> >> All you need to do is generate a function object that inherits recursively >> from a set of other function objects. >> >> The function objects in question need to be either monomorphic or to be >> sufficiently constrained with SFINAE so that each operator() overload is not >> ambiguous. >> >> Unfortunately, Boost.Phoenix was never extended to support this. > > I really like the idea, and i think the C++11-based solution above is > nice! I didn't have the time yet to glance through the code though ... > > Phoenix didn't tackle that yet because it is a hard problem ... the > main problem is the syntax how to express which lambda is responsible > for what types. The above solution with C++11 lambdas is nice indeed! Yeah, the first time I've actually been happy that non-polymorphic lambdas exist! Nice idea, Kevin! > However, what's missing is something like a "catch all" aka a > templated lambda ... ...ah, yes... there's the rub. And my day is now spoiled :-) There is a catch all case. Just provide a lambda for boost::blank. See the original thread on StackOverflow where Me and R. Martinho Fernandes came up with the template syntax. There is also a complete code snippet with test cases on the post http://stackoverflow.com/q/7867555/170521

1 1

Boost Mingw w64 compilation issues and fixes
by Andrew Ho 19 Jul '13

19 Jul '13

Hi, I've been working on getting Boost to compile properly with Mingw w64 on Windows x64 (specifically, Mingw w64 with GCC 4.8.1 rev 2/Windows threads, http://sourceforge.net/projects/mingwbuilds/files/host- windows/releases/4.8.1/64-bit/threads-win32/seh/). Link to trac bug reports/patches: Boost config/Boost thread: https://svn.boost.org/trac/boost/ticket/8817 I believe this fix works with all target platforms, though I can't test with Windows CE to verify that it works. At least works with VS2012 and Mingw w64. Boost Python: https://svn.boost.org/trac/boost/ticket/8818 This fix again works with VS2012 and Mingw w64. It moves an #undef hypot directive (which python.h unfortunately uses) to be used any time python.h decides it needs to define it. I don't know if any platforms/compilers rely on having hypot being defined as a macro. Doesn't link for me because I think the official Windows Python release is built with VS, I'll need to find/build Python with Mingw w64 to see if it works. Boost Log: https://svn.boost.org/trac/boost/ticket/8819 (apparently has already been reported as https://svn.boost.org/trac/boost/ticket/8786) Boost Math: TBD There is some compile error with Boost Math which is causing my compiler to crash. I don't know if this is on the Boost Math side, or is a bug with Mingw w64. I'll submit a bug report and possibly a patch when I have a bit more time to dig into the issue. I think these are the main outstanding issues with getting Boost to compile with Mingw w64 on x64 Windows. I was able to get everything else to compile smoothly with Mingw w64 and VS2012 (targeting x64).

3 9

invalid "this is an old version of boost" links
by Mathieu Champlon 19 Jul '13

19 Jul '13

Hi, All the links at the top of documentation pages for previous versions of boost seem to have suddenly become invalid as they all link to http://www.boost.org/doc/libs/ For instance see http://www.boost.org/doc/libs/1_48_0/libs/config/doc/html/boost_config/boos… I cannot remember when I first noticed it, maybe a couple of weeks ago. Cheers, MAT.

2 1

[serialization][static_assert] Moving BOOST_STATIC_WARNING to Boost.StaticAssert?
by Petr Machata 19 Jul '13

19 Jul '13

Hi there, do you think it would make sense to move static_warning.hpp from boost/serialization up directly under boost/, and perhaps move it conceptually under Boost.StaticAssert umbrella? It seems strange how a serialization library exposes such general-purpose service. We could still provide a forwarding header in Serialization namespace for backward compatibility. Shall I prepare a patch to that effect? Thanks, PM

2 3

[git] creating symlinks in the git layout
by Beman Dawes 19 Jul '13

19 Jul '13

Steven added "Initial supprort for creating symlinks in the git layout" in changeset 84524. How is this support used? Is it working reliably? Thanks, --Beman

2 2

[bitstream] Copy stream buffer or pass pointer?
by Paul Long 18 Jul '13

18 Jul '13

While working on a bitstream library I proposed a while back (http://article.gmane.org/gmane.comp.lib.boost.devel/242574) I came across a design decision for which I'd like to get some feedback. The proposed bitstream library (https://github.com/dplong/bitstream) mimics the std::stringstream class hierarchy and semantics as close as possible. In general, when the consumer of the std::stringstream/stringbuf classes provides a string for the stream buffer, a copy gets made; likewise, when it retrieves the stream buffer, it gets a copy of the string. For example, the following snippet prints "hello, goodbye". char c[BUFSIZ] = "hello"; istringstream iss(c); strcpy(c, "goodbye"); cout << iss.str() << ", " << c; However, the library I'm working on doesn't copy. Instead, pointers are passed in and out. So, for example, this code prints "goodbye, goodbye". char c[BUFSIZ] = "hello"; ibitstream ibs(c); strcpy(c, "goodbye"); cout << ibs.data() << ", " << c; I don't think either way is more correct than the other. The reason I don't copy is for memory and CPU performance, thinking that the streams a bit-stream library typically processes are larger than the streams that a string-stream library processes and are more time critical. I very well may be mistaken, though. Anyway, what do you people think? Copy or don't copy? Maybe I should do copies just to follow the semantics of std::stringstream. Oh, also, am I being presumptuous by including "[bitstream]" in the Subject header of this post since it's just a _proposed_ library? IOW, should I stop doing that? Paul

3 3

[build] bootstrap.sh is triply broken on MinGW
by Stephan T. Lavavej 18 Jul '13

18 Jul '13

Hi, For over a year I've been suffering from bootstrap.sh being broken on MinGW, although I figured out a horrible hackaround. In 1.54.0 two more breaks appeared, and I figured out real fixes for them. I'd like to offer my real fixes here, and request two things: (A) a real fix to replace my horrible hackaround for the original bug, and (B) bootstrap.sh to be tested on MinGW for each release, because it's clearly not receiving sufficient coverage. The first break appears to be tracked by https://svn.boost.org/trac/boost/ticket/5680 and https://svn.boost.org/trac/boost/ticket/6350 . The problem is that bootstrap.sh and b2.exe don't agree on what MinGW should be called: is it mingw or is it gcc? No permutations of toolsets passed on the command lines work. I've used the following horrible hackaround in 1.49.0 through 1.54.0 inclusive: diff -aurN boost_1_54_0/bootstrap.sh boost_1_54_0-fixed/bootstrap.sh --- boost_1_54_0/bootstrap.sh 2013-03-09 14:55:05 -0800 +++ boost_1_54_0-fixed/bootstrap.sh 2013-07-18 00:12:38 -0700 @@ -215,7 +215,7 @@ if test "x$BJAM" = x; then echo -n "Building Boost.Build engine with toolset $TOOLSET... " pwd=`pwd` - (cd "$my_dir/tools/build/v2/engine" && ./build.sh "$TOOLSET") > bootstrap.log 2>&1 + (cd "$my_dir/tools/build/v2/engine" && ./build.sh mingw) > bootstrap.log 2>&1 if [ $? -ne 0 ]; then echo echo "Failed to build Boost.Build build engine" Of course, this is completely unacceptable for other toolsets, but I basically know nothing about Boost's build machinery, so I can't figure out a real fix. Ideally, bootstrap.sh followed by b2.exe would work automatically, without toolsets being specified. However, I would still be extremely happy if it worked with manually specified toolsets, as long as I didn't have to patch or sed files. The second and third breaks are new to 1.54.0 and are tracked by https://svn.boost.org/trac/boost/ticket/8762 . Here are my fixes that should work for all platforms: diff -aurN boost_1_54_0/tools/build/v2/engine/build.jam boost_1_54_0-fixed/tools/build/v2/engine/build.jam --- boost_1_54_0/tools/build/v2/engine/build.jam 2013-05-20 21:14:18 -0700 +++ boost_1_54_0-fixed/tools/build/v2/engine/build.jam 2013-07-18 00:12:43 -0700 @@ -483,8 +483,8 @@ make.c make1.c mem.c object.c option.c output.c parse.c pathsys.c regexp.c rules.c scan.c search.c subst.c w32_getreg.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c class.c cwd.c native.c md5.c - modules/set.c modules/path.c modules/regex.c modules/property-set.c - modules/sequence.c modules/order.c ; + [ .path modules set.c ] [ .path modules path.c ] [ .path modules regex.c ] + [ .path modules property-set.c ] [ .path modules sequence.c ] [ .path modules order.c ] ; if $(OS) = NT { jam.source += execnt.c filent.c pathnt.c ; It appears that build.jam needs to use this .path machinery to generate either forward slashes or backslashes. When forward slashes are literally used, the bootstrap complains that it doesn't know how to make the corresponding object files. Once this is fixed, the final break is revealed: diff -aurN boost_1_54_0/tools/build/v2/engine/build.sh boost_1_54_0-fixed/tools/build/v2/engine/build.sh --- boost_1_54_0/tools/build/v2/engine/build.sh 2013-05-20 21:14:18 -0700 +++ boost_1_54_0-fixed/tools/build/v2/engine/build.sh 2013-07-18 00:12:43 -0700 @@ -247,18 +247,18 @@ BJAM_SOURCES="\ command.c compile.c constants.c debug.c execcmd.c frames.c function.c glob.c\ hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c\ - object.c option.c output.c parse.c pathsys.c pathunix.c regexp.c rules.c\ + object.c option.c output.c parse.c pathsys.c regexp.c rules.c\ scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c\ builtins.c class.c cwd.c native.c md5.c w32_getreg.c modules/set.c\ modules/path.c modules/regex.c modules/property-set.c modules/sequence.c\ modules/order.c" case $BOOST_JAM_TOOLSET in mingw) - BJAM_SOURCES="${BJAM_SOURCES} execnt.c filent.c" + BJAM_SOURCES="${BJAM_SOURCES} execnt.c filent.c pathnt.c" ;; *) - BJAM_SOURCES="${BJAM_SOURCES} execunix.c fileunix.c" + BJAM_SOURCES="${BJAM_SOURCES} execunix.c fileunix.c pathunix.c" ;; esac (It took me quite some time to figure out this one.) Although pathunix.c compiles on MinGW, it doesn't work, causing the bootstrap to complain about not being able to write its command file. The correct pattern to follow (as correctly done in build.jam; you can see half of it at the bottom of the build.jam diff here) is for pathnt.c to be used for mingw and pathunix.c to be used for all other build.sh platforms (i.e. real Unixes). Thanks, Stephan T. Lavavej

1 0

[container][set, map, flat_set, flat_map, +multi_xxx] operator< and operator== seems to ignore custom KeyCompare
by Thorsten Ottosen 18 Jul '13

18 Jul '13

Hi Ion & others, I think that there might be a problem in the implementation of operator< for these containers. There might be a problem with operator== too. The problem is that they all use some variant of the following definition: template <class Key, class Value, class KeyOfValue, class KeyCompare, class A> inline bool operator<(const rbtree<Key,Value,KeyOfValue,KeyCompare,A>& x, const rbtree<Key,Value,KeyOfValue,KeyCompare,A>& y) { return std::lexicographical_compare(x.begin(), x.end(), y.begin(), y.end()); } There is no KeyCompare (or other compare object) passsed to lexicographical compare. Reading up on the standard, it seems that all standard containers are implemented this way. Consequence: when having e.g. set<T*>, the comparison is not portable, since only std::less<T*> is guaranteed to be. So isn't this a defect? The other issue is perhaps more sensitive. What should users expect from typedef set<std::string,CaseInsensitiveLess> Set; Set s1{ "foo", "BAR" }; Set s2{ "FOO", "bar" }; assert( s1 < s2 ); // true? assert( s1 == s2 ); // true? I was at least surprised by this behavior. regards Thorsten

3 4

Git Modularization example Boost .gitattributes
by Niall Douglas 16 Jul '13

16 Jul '13

> > Shouldn't the repositories contain a .gitattributes file indicating the > > eol flavor to be used for text files where it has significance? > > Perhaps! I don't know anything about .gitattributes. Where can I find > out more? Dave, I can probably save you some work here with my "perfect" mirror of Boost's EOL and MIME type config into a .gitattributes with which I configured my subgit to mirror my git repo into Boost sandbox. Taken from https://github.com/ned14/TripleGit/blob/master/.gitattributes: * text=auto !eol svneol=native#text/plain *.gitattributes text svneol=native#text/plain # Scriptish formats *.bat text svneol=native#text/plain *.bsh text svneol=native#text/x-beanshell *.cgi text svneol=native#text/plain *.cmd text svneol=native#text/plain *.js text svneol=native#text/javascript *.php text svneol=native#text/x-php *.pl text svneol=native#text/x-perl *.pm text svneol=native#text/x-perl *.py text svneol=native#text/x-python *.sh eol=lf svneol=LF#text/x-sh configure eol=lf svneol=LF#text/x-sh # Image formats *.bmp binary svneol=unset#image/bmp *.gif binary svneol=unset#image/gif *.ico binary svneol=unset#image/ico *.jpeg binary svneol=unset#image/jpeg *.jpg binary svneol=unset#image/jpeg *.png binary svneol=unset#image/png *.tif binary svneol=unset#image/tiff *.tiff binary svneol=unset#image/tiff *.svg text svneol=native#image/svg%2Bxml # Data formats *.pdf binary svneol=unset#application/pdf *.avi binary svneol=unset#video/avi *.doc binary svneol=unset#application/msword *.dsp text svneol=crlf#text/plain *.dsw text svneol=crlf#text/plain *.eps binary svneol=unset#application/postscript *.gz binary svneol=unset#application/gzip *.mov binary svneol=unset#video/quicktime *.mp3 binary svneol=unset#audio/mpeg *.ppt binary svneol=unset#application/vnd.ms-powerpoint *.ps binary svneol=unset#application/postscript *.psd binary svneol=unset#application/photoshop *.rdf binary svneol=unset#text/rdf *.rss text svneol=unset#text/xml *.rtf binary svneol=unset#text/rtf *.sln text svneol=native#text/plain *.swf binary svneol=unset#application/x-shockwave-flash *.tgz binary svneol=unset#application/gzip *.vcproj text svneol=native#text/xml *.vcxproj text svneol=native#text/xml *.vsprops text svneol=native#text/xml *.wav binary svneol=unset#audio/wav *.xls binary svneol=unset#application/vnd.ms-excel *.zip binary svneol=unset#application/zip # Text formats .htaccess text svneol=native#text/plain *.bbk text svneol=native#text/xml *.cmake text svneol=native#text/plain *.css text svneol=native#text/css *.dtd text svneol=native#text/xml *.htm text svneol=native#text/html *.html text svneol=native#text/html *.ini text svneol=native#text/plain *.log text svneol=native#text/plain *.mak text svneol=native#text/plain *.qbk text svneol=native#text/plain *.rst text svneol=native#text/plain *.sql text svneol=native#text/x-sql *.txt text svneol=native#text/plain *.xhtml text svneol=native#text/xhtml%2Bxml *.xml text svneol=native#text/xml *.xsd text svneol=native#text/xml *.xsl text svneol=native#text/xml *.xslt text svneol=native#text/xml *.xul text svneol=native#text/xul *.yml text svneol=native#text/plain boost-no-inspect text svneol=native#text/plain CHANGES text svneol=native#text/plain COPYING text svneol=native#text/plain INSTALL text svneol=native#text/plain Jamfile text svneol=native#text/plain Jamroot text svneol=native#text/plain Jamfile.v2 text svneol=native#text/plain Jamrules text svneol=native#text/plain Makefile* text svneol=native#text/plain README text svneol=native#text/plain TODO text svneol=native#text/plain # Code formats *.c text svneol=native#text/plain *.cpp text svneol=native#text/plain *.h text svneol=native#text/plain *.hpp text svneol=native#text/plain *.ipp text svneol=native#text/plain *.tpp text svneol=native#text/plain *.jam text svneol=native#text/plain *.java text svneol=native#text/plain Hope that's useful. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

2 4

detail/endian.hpp replacement?
by Philip Bennefall 15 Jul '13

15 Jul '13

Hi all, I just wanted to ask about the possibility of getting the Boost licensed fix for detail/endian.hpp into the next release of Boost? It would be great to have that license ambiguity resolved for version 1.55.0. Kind regards, Philip Bennefall

2 2

[thread] Is future.then( scheduler , task ) abandoned?
by Klaim - Joël Lamotte 15 Jul '13

15 Jul '13

On this page: http://www.boost.org/doc/libs/1_54_0/doc/html/thread/future.html And in the task list: https://svn.boost.org/trac/boost/query?status=!closed&component=thread We can see that there are plans to add async( scheduler, task ). However there are no tasks for future.then( scheduler, task ). The documentation suggests that it will be implemented in a future release. So I just wanted a confirmation: is it still planned or is it abandoned? Or is it just a missing task? Joel Lamotte

2 2

Git Modularization hiccups
by Beman Dawes 15 Jul '13

15 Jul '13

* "git clone --recursive http://github.com/boostorg/boost modular-boost" is mostly working fine here (on Win7) but is producing one set of error messages: Cloning into 'libs/assign'... fatal: reference is not a tree: 57ec5d1534810090649b18c88e66a46f48cdcf1c ... Unable to checkout '57ec5d1534810090649b18c88e66a46f48cdcf1c' in submodule path 'libs/assign' The remaining hiccups are in the root directory, comparing trunk to master: * boost.css is missing content from revisions 36243 and 53553. * boost-build.jam has different comments and history. Something is totally whacky. * boostcpp.py contents are the same, but the trunk file has Unix line endings, the master file has Windows line endings. * Same problem with bootstrap.sh. IIRC, it is important that the .sh files have the Unix line endings. * c++boost.gif not present in trunk, present in master. * index.html missing in master. * Jamfile.v2 and Jamroot.jam not present in trunk, present in master. * INSTALL missing in master. * LICENSE_1_0.txt has Unix line endings in trunk, Windows line endings in master. * project-config.jam missing in master. * rst.cc missing in master. * README.txt not present in trunk, present in master. HTH, --Beman

9 17

Release branch now open for merging
by Marshall Clow 15 Jul '13

15 Jul '13

The release branch (https://svn.boost.org/svn/boost/branches/release) is open for merging all stable changes from trunk, including bug fixes and major upgrades to existing libraries. Breaking changes should be coordinated via the mailing list with the developers of the other libraries affected. New libraries may be added, but require permission of a release manager. In other words, merging *does not* require permission from a release manager, except for new libraries. Boost Calendar with the release schedule: http://www.boost.org/development/index.html Release schedule explanation: http://svn.boost.org/trac/boost/wiki/ReleaseSchedule Release practices for developers: http://svn.boost.org/trac/boost/wiki/ImprovingPractices -- The Release Managers, Beman Dawes Daniel James Eric Niebler Marshall Clow Rene Rivera Vladimir Prus

1 0

[function] type conversion ambiguity?
by Andrew Ho 15 Jul '13

15 Jul '13

Consider the overloaded functions foo and bar: typedef boost::function<void(void)> function_type1; typedef boost::function<void(int)> function_type2; typedef std::function<void(void)> function_type3; typedef std::function<void(int)> function_type4; void foo(const function_type1 &a) { // blah } void foo(const function_type2 &a) { // blah } void bar(const function_type3 &a) { // blah } void bar(const function_type4 &a) { // blah } calling foo with a function pointer is ambiguous, but calling bar is not: void doit1(void) {} void doit2(int) {} foo(&doit1); // ambiguous bar(&doit2); // compiles and runs fine This occurs despite the fact that boost::function<void(void)>(&doit2) can be caught at compile time. Is there some way to fix the definition of boost::function such that this is no longer ambiguous?

2 1

Nullable types
by Bjorn Reese 15 Jul '13

15 Jul '13

It seems like different Boost libraries use different nullable types. * Optional uses boost::none * Tribool uses boost::logic::indeterminate_keyword_t * Tuple uses boost::tuples::null_type * Variant uses boost::blank And there are possibly more. What are your opinions about unifying these?

4 3

Extremely large Visual Studio libboost_log_setup* binaries
by Tom Kent 14 Jul '13

14 Jul '13

In the 1.54.0 release, I noticed that the size of the binaries built with visual studio was more than twice that of the previous releases. For example the msvc-8.0-64 build went from 2GB to 5GB. Upon further investigation, almost all of that increase was in the libboost_log_setup* binaries, which were each in the 100s of MBs. Does anyone know if there is a reason for this? Is it a configuration error? Tom Kent

8 22

Boost.Operators and make_shared
by Pieter 13 Jul '13

13 Jul '13

LS, I have noticed that using Boost.Operators has a side-effect which I can't explain. I am using std::make_shared as a default, however, some of the boost libraries I use pull in boost::make_shared as well. When using some class T2 derived from one of the boost.operators classes, this causes MSVC2010 to not compile when invoking make_shared<T2> as the compiler can no longer resolve between the two overloaded versions of make_shared for some reason. I am hoping that someone out can explain what is happening here. A minimal example is included here: #include <memory> #include <boost\operators.hpp> #include <boost\make_shared.hpp> struct T1 {}; struct T2 : boost::equality_comparable<T2> {}; int main( int argc, const char* argv[] ) { T1 Object1; T2 Object2; using std::make_shared; std::shared_ptr<T1> Ptr1 = make_shared<T1>(Object1); // OK std::shared_ptr<T2> Ptr2 = make_shared<T2>(Object2); // error C2668: 'boost::make_shared' : ambiguous call to overloaded function return 1; } Thanks in advance! Pieter

4 6

[regression] patch for running tests in parallel and out-of-sync files
by Robert Kawulak 13 Jul '13

13 Jul '13

When I was running tests in parallel (using b2 -j option) I was getting random warnings in the results table because "msvc.manifest" lines were interleaved with compile/link actions. I've fixed this with the attached patch - is it OK to apply it to trunk/release? BTW, I've noticed that the following files in tools/regression/src haven't been updated in release branch even though they've been changed in trunk a long time ago: compiler_status.cpp (trunk date 2012-01-21, release date 2011-10-06) library_status.cpp (trunk date 2013-03-25, release date 2013-03-09) Is it OK to update these in release branch? Best regards, Robert

1 0

[log] Set default log source name
by Renato Forti 12 Jul '13

12 Jul '13

Hi All, Have any way to define a custon log source name on simple_event_log_backend! I foud a method to get (get_default_source_name), but where is "set" method! HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\do kagent simple event source I want set/change default name (in my case) : "dokagent simple event source" Thanks

2 1

[config] Feature request: BOOST_OVERRIDE
by Borislav Stanimirov 12 Jul '13

12 Jul '13

Hi, I think it will be a nice feature to add BOOST_OVERRIDE to Boost.Config in a manner similar to BOOST_CONSTEXPR. It's a nice keyword and it would be nice if people could make use of it when it's available. -- Borislav

5 4

multi_index broken on gcc4.7
by Hartmut Kaiser 12 Jul '13

12 Jul '13

In code which compiled just fine until yesterday I'm now seeing: /opt/boost/trunk-release/boost/multi_index/detail/index_base.hpp: In member function 'std::pair<typename boost::multi_index::detail::multi_index_node_type<Value, IndexSpecifierList, Allocator>::type*, bool> boost::multi_index::detail::index_base<Value, IndexSpecifierList, Allocator>::final_emplace_(Args&& ...)': /opt/boost/trunk-release/boost/multi_index/detail/index_base.hpp:214:29: error: expected primary-expression before ')' token /opt/boost/trunk-release/boost/multi_index/detail/index_base.hpp: In member function 'std::pair<typename boost::multi_index::detail::multi_index_node_type<Value, IndexSpecifierList, Allocator>::type*, bool> boost::multi_index::detail::index_base<Value, IndexSpecifierList, Allocator>::final_emplace_hint_(boost::multi_index::detail::index_base<Value , IndexSpecifierList, Allocator>::final_node_type*, Args&& ...)': /opt/boost/trunk-release/boost/multi_index/detail/index_base.hpp:233:16: error: expected primary-expression before ')' token OS: Debian Unstable Kernel: Linux 3.2 GCC: 4.7 (C++11, x86-64) Boost: SVN Trunk Build Type: Release Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu

2 2

[variant] Applying a portion of fixes
by Antony Polukhin 12 Jul '13

12 Jul '13

Hi, I'd like to fix this issue: https://svn.boost.org/trac/boost/ticket/8772 Apply patch for this issue: https://svn.boost.org/trac/boost/ticket/7911 And take care of this: https://svn.boost.org/trac/boost/ticket/8717 Patches and ideas for fixes are described in tickets. If there'll be no objections till next weekend I'll commit the fixes. -- Best regards, Antony Polukhin

1 0

Boost 1.54.0 released!
by Marshall Clow 11 Jul '13

11 Jul '13

Release 1.54.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 five new libraries and numerous enhancements and bug fixes for existing libraries. New Libraries: Log: Logging library, from Andrey Semashev. TTI: Type Traits Introspection library, from Edward Diener. Type Erasure: Runtime polymorphism based on concepts. For details, including download links, see http://www.boost.org/users/news/version_1.54.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.54.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Beman Dawes Daniel James Eric Niebler Marshall Clow Rene Rivera Vladimir Prus

5 9

Regression tests report page stuck
by Joaquin M Lopez Munoz 11 Jul '13

11 Jul '13

Hi, the trunk testing bot http://www.boost.org/development/tests/trunk/developer/summary.html seems to be stuck since ~1.5 days ago. Thank you, Joaquín M López Muñoz Telefónica Digital

1 1

[gil] Portability of new code issue.
by Harg Tholan 11 Jul '13

11 Jul '13

Hi all, Christian has been working on some new features for GIL, such code works fine in Windows 7 with VS11, but it will fail to compile with GCC in Debian Wheezy. I've been trying to figure out why is this failing and possible workarounds with no success. For those with time wanting to help: 1. You will need boost-trunk. 2. I have attached the "bleeding edge" code (a pair of .hpp) as well as a test case. 3. Compile: g++ subsampled_test.cpp -o ss -lboost_unittesting_framework My Compiler Version: g++ (Debian 4.7.2-5) 4.7.2 Errors: yuv_image.hpp:234:38: error: expected primary-expression before ‘,’ token subsampled_test.cpp:28:41: required from here ../yuv_image.hpp:234:5: error: ISO C++ forbids comparison between pointer and integer Note: I have attached the code here because I had to fix some template code, adding/removing 'tyepename', as well as prevention of template parameter shadowing. As you already know, Microsoft's compiler is very 'flexible', allowing non-standard code to compile. Regards, Juan.

1 0

[filesystem] Please take care of #8706
by Antony Polukhin 10 Jul '13

10 Jul '13

Hi, There is a ticket https://svn.boost.org/trac/boost/ticket/8706 and patch in it that fixes compilation of Boost.Filesystem under Android NDK. Tested patch under latest NDK and it works well. Fix is required to start regression tests for droid platform. -- Best regards, Antony Polukhin

4 8

[function] Bind to std::function if supported?
by Andrew Ho 09 Jul '13

09 Jul '13

The boost::move library binds to std::move/T&&/etc. when the compiler supports such features, and only uses work-around mechanisms when the compiler lacks such support. Should we add similar support for boost::function? something like: #ifdef BOOST_FUNCTION_USE_STANDARD_LIBRARY_FUNCTION // alternative: #ifndef BOOST_NO_CXX11_HDR_FUNCTIONAL #include <functional> namespace boost { using ::std::function; } #else // whatever boost::function currently does #endif // ... something similar for boost::bind and std::bind I haven't looked at boost::atomic yet, but we could also consider similar bindings to std::atomic if the library doesn't already do so.

3 3

[shared_array] Why not in C++11 ?
by Sid Sacek 09 Jul '13

09 Jul '13

Does anyone know why 'boost::shared_array<>' was not made part of C++11, since pretty much all the other smart pointers were? -Sid

10 41

[context] SSE/AVX registers preservation
by Andrey Semashev 09 Jul '13

09 Jul '13

Hi, I've been looking at Boost.Context and wondering whether it preserves SSE/AVX state on context switches. From the code it doesn't look like the case - only jump_x86_64_ms_pe_masm.asm contains the code that saves some (not all) xmm registers and ymm registers are never saved. Is this intentional or the library simply doesn't support SSE/AVX? And why not use xsave/xrstor to consistently support all future extensions?

2 2

Re: [boost] Interest in a 'Boost.property' library?
by Joe Mucchiello 08 Jul '13

08 Jul '13

Personally, I always consider properties with getters/setters an anti-pattern for OOP languages like C++. Class interfaces should include only those methods that describe logically valid actions one might take on instances of the class. The idea of properties might sometimes be appropriate. But often times, programs will see a hammer and treat everything they see after it as nails. It becomes easy to add a few more getters and setters for "the rest" of the implementation details and you lose proper encapsulation. Usually when I find a class with lots of get/set methods I find a class with very little thought used when that class was designed.

4 7

[log] Setup Windows event log backends
by Renato Forti 08 Jul '13

08 Jul '13

Work well, on win 7/vc 11! Win 8/vc 11, don't work! mc is not detected! On Thu, Jul 4, 2013 at 11:38 PM, Renato Forti <re.tf(a)acm.org> wrote: > Hi, > I did, but don't work! I have mc, and I remove bin.v2. But boost build > don't find my mc :( > > - message-compiler : no > - compiler-supports-ssse3 : yes > - compiler-supports-avx2 : yes > - gcc visibility : no > - long double support : yes > > C:\boost_1_54_0>mc > Microsoft (R) Message Compiler Version 1.12.9200 Copyright (c) > Microsoft Corporation. All rights reserved. > > No cached! I am on Windows 8, and vc11! Thanks again! Hm, that's strange. Perhaps, a Win 8 thing? What does bin.v2/config.log say? _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

[unordered] a strange limitation for move emulation in Boost.Unordered
by Joaquin M Lopez Munoz 08 Jul '13

08 Jul '13

Here: http://www.boost.org/doc/html/unordered/compliance.html#unordered.complianc… it reads: "Non-copyable objects can be stored in the containers, but without support for rvalue references the container will not be movable." Why not? Container movement does not ever touch its elements, so I don't see the connection. Joaquín M López Muñoz Telefónica Digital

2 5

boost-1.54 needs a bugfix!
by Oliver Kowalke 08 Jul '13

08 Jul '13

unfortunately boost-1.54 needs a bugfix - because my request to merge boost.coroutine into release a required bugfix was not applied :( I'm wondering because the regression-tests are passed?! what to do? should I modify the fix in boost-release and archives of boost-1.54 are rebuild?

11 24

[fusion] Adapter for std::array
by Mateusz Loskot 07 Jul '13

07 Jul '13

Hi, I have prototyped Fusion adapter for std::array, as an attempt to clear the related feature request: https://svn.boost.org/trac/boost/ticket/8241 Here is the functional and testable code of the adaptor : https://github.com/mloskot/boost_fusion_std_array I will appreciate any critique and comments. Unfortunately, I have hit the apparently well-known problem. It is the Fusion begin/end ADL issues with C++0x range-based for and such, as discussed and reported here: http://lists.boost.org/Archives/boost/2010/12/174199.php https://svn.boost.org/trac/boost/ticket/4028 There has been no feedback to the ticket #8241, so I'm not sure what is the Fusion authors' view on std::array adoption. So, a couple of questions: Do the Fusion authors consider any cure for the ADL issues? If not, despite the inconvenience of use of qualified names, would it be still possible to accept std::array into Fusion? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

4 7

Interest in a 'Boost.property' library?
by Metodi Todorov 07 Jul '13

07 Jul '13

Is there any interest of "C# property" like library? struct vec2 { float get_x() const{...} float set_x() const{...} ... property_rw<float, vec2, &vec2::get_x, &vec2::set_x> x; vec2() : y(this) {} }; vec2 v; v.x = 15.0f; cout << v.x << endl; Example: http://sourceforge.net/projects/cproperty/?source=dlp Regards, Metodi Todorov

5 5

Benchmarking for performance?
by Arpan Sen 07 Jul '13

07 Jul '13

Hi Boost Dev, What sort of benchmarking does the community do for performance when moving from one revision to another? Kind of regression numbers for benchmark tests I would say for memory and time required. Does not have to be at an application level - even at a data structure level is a good start. Thanks a lot. Arpan

1 0

Historic of regression tests?
by Joaquin M Lopez Munoz 07 Jul '13

07 Jul '13

The regression tests at http://www.boost.org/development/tests/release/developer/summary.html are constantly updated (of course), but I seem to remember that the version manager used to backup a snapshot of this at each release. Am I right (I found nothing searching through boost.org)? Is there some sort of historic info on regression tests? Thank you, Joaquín M López Muñoz Telefónica Digital

2 1

[log] Setup Windows event log backends
by Renato Forti 06 Jul '13

06 Jul '13

Hi, I am trying setup a basic: <http://www.boost.org/doc/libs/1_54_0/libs/log/doc/html/log/detailed/sink_ba ckends.html#log.detailed.sink_backends.event_log> Windows event log, and I copy and past code from log documentation. My app link with: 1> main.cpp 1> Linking to lib file: boost_filesystem-vc110-mt-gd-1_54.lib 1> Linking to lib file: boost_system-vc110-mt-gd-1_54.lib 1> Linking to lib file: boost_log-vc110-mt-gd-1_54.lib 1> Linking to lib file: boost_thread-vc110-mt-gd-1_54.lib 1> Linking to lib file: boost_log_setup-vc110-mt-gd-1_54.lib 1> Linking to lib file: boost_date_time-vc110-mt-gd-1_54.lib 1> Linking to lib file: boost_chrono-vc110-mt-gd-1_54.lib But I have some link problems: 1>qt.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall boost::log::v2_mt_nt5::sinks::basic_simple_event_log_backend<char>::basic_si mple_event_log_backend<char>(void)" (__imp_??0?$basic_simple_event_log_backend@D@sinks@v2_mt_nt5@log@boost@@QAE@ XZ) referenced in function "class boost::shared_ptr<class boost::log::v2_mt_nt5::sinks::basic_simple_event_log_backend<char> > __cdecl boost::make_shared<class boost::log::v2_mt_nt5::sinks::basic_simple_event_log_backend<char> >(void)" (??$make_shared@V?$basic_simple_event_log_backend@D@sinks@v2_mt_nt5@log@boos t@@@boost@@YA?AV?$shared_ptr@V?$basic_simple_event_log_backend@D@sinks@v2_mt _nt5@log@boost@@@0@XZ) 1>qt.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall boost::log::v2_mt_nt5::sinks::basic_simple_event_log_backend<char>::~basic_s imple_event_log_backend<char>(void)" (__imp_??1?$basic_simple_event_log_backend@D@sinks@v2_mt_nt5@log@boost@@QAE@ XZ) referenced in function "public: void * __thiscall boost::log::v2_mt_nt5::sinks::basic_simple_event_log_backend<char>::`scalar deleting destructor'(unsigned int)" (??_G?$basic_simple_event_log_backend@D@sinks@v2_mt_nt5@log@boost@@QAEPAXI@Z ) 1>qt.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: void __thiscall boost::log::v2_mt_nt5::sinks::basic_simple_event_log_backend<char>::set_even t_type_mapper(class boost::log::v2_mt_nt5::aux::light_function<enum boost::log::v2_mt_nt5::sinks::event_log::event_type __cdecl(class boost::log::v2_mt_nt5::record_view const &)> const &)" (__imp_?set_event_type_mapper@?$basic_simple_event_log_backend@D@sinks@v2_mt _nt5@log@boost@@QAEXABV?$light_function@$$A6A?AW4event_type@event_log@sinks@ v2_mt_nt5@log@boost@@ABVrecord_view@456@@Z@aux@345@@Z) referenced in function "void __cdecl init_logging(void)" (?init_logging@@YAXXZ) 1>qt.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: void __thiscall boost::log::v2_mt_nt5::sinks::basic_simple_event_log_backend<char>::consume( class boost::log::v2_mt_nt5::record_view const &,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (__imp_?consume@?$basic_simple_event_log_backend@D@sinks@v2_mt_nt5@log@boost @@QAEXABVrecord_view@345@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocat or@D@2@@std@@@Z) referenced in function "protected: void __thiscall boost::log::v2_mt_nt5::sinks::basic_formatting_sink_frontend<char>::feed_rec ord<class boost::log::v2_mt_nt5::aux::fake_mutex,class boost::log::v2_mt_nt5::sinks::basic_simple_event_log_backend<char> >(class boost::log::v2_mt_nt5::record_view const &,class boost::log::v2_mt_nt5::aux::fake_mutex &,class boost::log::v2_mt_nt5::sinks::basic_simple_event_log_backend<char> &)" (??$feed_record@Vfake_mutex@aux@v2_mt_nt5@log@boost@@V?$basic_simple_event_l og_backend@D@sinks@345@@?$basic_formatting_sink_frontend@D@sinks@v2_mt_nt5@l og@boost@@IAEXABVrecord_view@234@AAVfake_mutex@aux@234@AAV?$basic_simple_eve nt_log_backend@D@1234@@Z) What is wrong? Thanks

3 10

[log] Build fail : log (1.44.0) on vc 11 using cxxflags=-Zc:wchar_t-
by Renato Forti 05 Jul '13

05 Jul '13

Hi All, I need use cxxflags=-Zc:wchar_t-, because I will use boost with my QT project! I build boost like this (debug in this case): bjam toolset=msvc-11.0 variant=debug threading=multi link=shared cxxflags=-Zc:wchar_t- But log lib fail with this: call "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"..\..\..\bin.v2\libs\log\build\msvc-11.0\debug\threading-mul ti\formatter_parser.obj.rsp" ...failed compile-c-c++ ..\..\..\bin.v2\libs\log\build\msvc-11.0\debug\threading -multi\formatter_parser.obj... ...skipped <p..\..\..\bin.v2\libs\log\build\msvc-11.0\debug\threading-multi>boos t_log_setup-vc110-mt-gd-1_54.dll for lack of <p..\..\..\bin.v2\libs\log\build\ms vc-11.0\debug\threading-multi>boost_log-vc110-mt-gd-1_54.lib... ...skipped <p..\..\..\bin.v2\libs\log\build\msvc-11.0\debug\threading-multi>boos t_log_setup-vc110-mt-gd-1_54.lib for lack of <p..\..\..\bin.v2\libs\log\build\ms vc-11.0\debug\threading-multi>boost_log-vc110-mt-gd-1_54.lib... ...skipped <p..\..\..\bin.v2\libs\log\build\msvc-11.0\debug\threading-multi>boos t_log_setup-vc110-mt-gd-1_54.pdb for lack of <p..\..\..\bin.v2\libs\log\build\ms vc-11.0\debug\threading-multi>boost_log-vc110-mt-gd-1_54.lib... ...failed updating 4 targets... ...skipped 6 targets... Anyone can helpeme? Thanks

3 6

gmp-5.1.2 / boost-1.54 / multiprecision lib
by Fred Schneider 05 Jul '13

05 Jul '13

Hello, I'm a bit of a newbie and I ran into some issues using gmp with boost. After building gmp-5.1.2, I tried to build a simple file: boostMathExample.cpp, based on the documentation (using the multiprecision library + referencing gmp): ////////////////////////////////////////// #include <boost/multiprecision/gmp.hpp> using namespace boost::multiprecision; int main(int argc, const char *argv[]) { mpz_int v = 1; // Do some arithmetic: for (unsigned int i = 1; i <= 1000; ++i) v *= i; std::cout << v << std::endl; } /////////////////////////////////////////////// I received the following missing symbol errors when trying to build: g++ -I ~/Dev/C++/gmp-5.1.2 -I ~/Dev/C++/boost boostMathExample.cpp -O2 -o boostMathExample Undefined symbols: "_main", referenced from: start in crt1.10.6.o "___gmpz_init", referenced from: __static_initialization_and_destruction_0(int, int)in cccOFSnR.o __static_initialization_and_destruction_0(int, int)in cccOFSnR.o "___gmpz_clear", referenced from: ___tcf_1 in cccOFSnR.o __static_initialization_and_destruction_0(int, int)in cccOFSnR.o "___gmpz_set_si", referenced from: __static_initialization_and_destruction_0(int, int)in cccOFSnR.o ld: symbol(s) not found collect2: ld returned 1 exit status ======================================== I'm running the following version of g++: i686-apple-darwin10-g++-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) I configured gmp, version 5.1.2 with the following flags: ./configure --enable-cxx CXX=g++ CXXFLAGS=-O2 CC=g++ CFLAGS="-g -O2" and then ran "make" and "make check". Any insight would be appreciated. Thanks, Fred

3 3

[algorithm][minmax_element] implementation question
by Michael Marcin 04 Jul '13

04 Jul '13

I was looking at minmax_elemement to try and understand the algorithm. I noticed that the boost implementation looks significantly more complicated than the clang libc++ implementation. Mainly due to the potential_min_result variable that exists in the boost version. Is there a reason for this discrepancy? Is there a bug in the clang implementation? http://llvm.org/svn/llvm-project/libcxx/trunk/include/algorithm http://www.boost.org/doc/libs/1_54_0/boost/algorithm/minmax_element.hpp

3 2

Re: [boost] [utility][thread] result_of - erroneous result type from a C++11 lambda
by Klaim - Joël Lamotte 04 Jul '13

04 Jul '13

On Tue, Apr 2, 2013 at 7:16 PM, Vicente J. Botet Escriba < vicente.botet(a)wanadoo.fr> wrote: > I've started to use C++11 lambda functions with Boost.Thread. > > The following works with clang-3.2 > > boost::future<int> f1 = boost::async( []() -> int {return 123;} ); > > > But it fails with gcc-4.6.2, 4.7.2 and 4.8.0 > > ../example/lambda_future.cpp:**25:91: erreur: conversion from > ‘boost::future<void>’ to non-scalar type ‘boost::future<int>’ requested > boost::future<int> f1 = boost::async( []() -> int {return 123;} ); > > The current implementation of boost::async uses boost::result_of to get > the result type of the callable parameter. > > Is this a know bug on boost::result_of or gcc compiler? > I'm seeing exactly the same behaviour in *VS2012 Update 2*. I'm using Boost 1.54.0 beta *r84748* To be more precise: 1) I first was just using boost::future and tried to use the new .then(), here is a full repro: #include <boost/thread/future.hpp> auto ft = boost::async( []{ return 42; } ).then( []( boost::future<int> r ){ return 666; } ); This fails because boost::async() returned a future<void> instead of a future<int>. I suspect the then() call to have the same problem. I can provide the full error log but I think it's not that useful. 2) Just to be sure I tried this full test: #include <boost/thread/future.hpp> int main() { auto ft = boost::async( []{ return 42; } ); // SUCCEED: static_assert( std::is_same< decltype(ft), boost::future<void> >::value, "WTF???" ); // FAILS: static_assert( std::is_same< decltype(ft), boost::future<int> >::value, "Not the expected type!" ); } Both asserts confirm that I don't get what I want. 3) I remembered that there were some issues from usage of boost::result_of in Boost.Log, so to clarify the situation I setup the following full test: #include <boost/utility/result_of.hpp> #include <type_traits> int top() { return 42; } struct K { int operator()(){ return 42; } typedef int value_type; }; auto F = []{ return 42; }; int main() { // A: ALL SUCCEED static_assert( std::is_same< decltype(K()()), int >::value, "Not the expected type!" ); static_assert( std::is_same< decltype(top()), int >::value, "Not the expected type!" ); static_assert( std::is_same< decltype(F()), int >::value, "Not the expected type!" ); // B: ALL SUCCEED static_assert( std::is_same< std::result_of<K()>::type, int >::value, "Not the expected type!" ); static_assert( std::is_same< std::result_of<decltype(top)>::type, int >::value, "Not the expected type!" ); static_assert( std::is_same< std::result_of<decltype(F)()>::type, int >::value, "Not the expected type!" ); // C: ALL SUCCEED std::result_of<K()>::type a = K()(); std::result_of<decltype(top)>::type b = top(); std::result_of<decltype(F)()>::type c = F(); // D: ALL FAILS static_assert( std::is_same< boost::result_of<K()>::type, int >::value, "Not the expected type!" ); static_assert( std::is_same< boost::result_of<decltype(top)>::type, int >::value, "Not the expected type!" ); static_assert( std::is_same< boost::result_of<decltype(F)()>::type, int >::value, "Not the expected type!" ); // E: ALL FAILS boost::result_of<K()>::type d = K()(); // error C2182: 'd' : illegal use of type 'void' boost::result_of<decltype(top)>::type e = top(); // error C2182: 'e' : illegal use of type 'void' boost::result_of<decltype(F)()>::type f = F(); // error C2182: 'f' : illegal use of type 'void' } This shows clearly that: 1. boost::result_of don't behave like std::result_of on this platform (and from previous discussions, on other platforms too). 2. both std::result_of and decltype() provide the result I expect from reading documentations about these. So far I'm assuming that the problem really is from boost::result_of, but I might be wrong because the differences with std::result_of are not clear to me. ---- Unfortunately this makes future.then() unusable if we expect return types. I don't know if it impacts other libraries (I suspect Boost.Log). Should I report a bug or is it known, already fixed or a misuse? Joel Lamotte

5 12

[result_of] Documentation update for ticket 7753
by Nathan Crookston 03 Jul '13

03 Jul '13

Hi Daniel & all, I'm updating the patch for ticket 7753 ( https://svn.boost.org/trac/boost/ticket/7753) I've made the requested changes to the patch, but I had a question on how to best explain which macro to define if, for example, you want result_of to work with C++11 lambdas. In the past, users with a pre-N3276 decltype have been advised to just #define BOOST_RESULT_OF_USE_DECLTYPE, with the explanation that "it's probably just going to work." While that advice is true, there are cases where this doesn't work; hence the addition of BOOST_RESULT_OF_USE_TR1_WITH_DECLTYPE_FALLBACK. To explain why you'd define the FALLBACK macro over the USE_DECLTYPE macro, I'm thinking of including a paragraph like the following. "The question naturally arises on why have both BOOST_RESULT_OF_USE_DECLTYPE and BOOST_RESULT_OF_USE_TR1_WITH_DECLTYPE_FALLBACK. In many situations, BOOST_RESULT_OF_USE_DECLTYPE will work well, even with pre-N3276 decltype. However, there are cases where a post-N3276 decltype is required to correctly deduce the return type of a functor. If a translation unit includes a functor whose return type is only deducible with TR1 or a post-N3276 decltype, using result_of with, e.g. a C++11 lambda function, will fail without BOOST_RESULT_OF_USE_TR1_WITH_DECLTYPE_FALLBACK. If the macro BOOST_NO_CXX11_DECLTYPE_N3276 is defined and BOOST_NO_CXX11_DECLTYPE is not defined when including result_of.hpp, defining BOOST_RESULT_OF_USE_TR1_WITH_DECLTYPE_FALLBACK is the safest option that will allow you to deduce C++11 lambda return types." My question is, am I over explaining it? Of course, I'd rather have BOOST_RESULT_OF_USE_TR1_WITH_DECLTYPE_FALLBACK defined automatically for compilers like VC10, g++4.5, etc., and include text like the following: "If you rely on the result of calling a nullary functor to be void, regardless of the actual return type, or if your code is not written to handle cases other than BOOST_RESULT_OF_USE_TR1 and BOOST_RESULT_OF_USE_DECLTYPE, you may wish to explicitly define one of those symbols prior to including result_of." Either way, comments welcome. Thanks, Nate

3 4

Want to contribute, need advice.
by Manmohit Rekhi 03 Jul '13

03 Jul '13

Hello, Am Manmohit Rekhi, a 2nd year computer engineering student at Nirma university, India. I have some programming experience in c and c++. Am interested in contributing to Boost, and would like to ask a few questions, to help me get started. I would be really grateful is, i could get the following questions answered. 1) Do i need to be familiar with the code of the standard c++ libraries, and if so, where do i start? 2) What other per-requisites are there? 3) Where do i start reading the boost libraries(i mean which file to read first)? Thanking You, Manmohit Rekhi

2 1

[Serialization] Constructor for polymorphic archives
by Bjorn Reese 03 Jul '13

03 Jul '13

I have a set of my own Boost.Serialization archives (e.g. [1]) that I wish to write polymorphic variants of. I have tried to follow the blueprint from polymorphic_text_iarchive, which inherits from polymorphic_iarchive_route. The problem is that the constructor of my archives takes iterators (begin and end) as arguments, but the polymorphic_iarchive_route constructor expects a std::stream argument. Is there any workaround for this? [1] http://sourceforge.net/p/protoc/code/ci/master/tree/include/protoc/transenc…

3 4

[Operators] Update, const-correctness and operator chaining
by Andrew Ho 02 Jul '13

02 Jul '13

Hi, I was doing some testing with Daniel Frey/Marc Glisse's proposed 4- overload set for binary operators. For reference, here's the overload set applied to commutative addition: friend T operator +( const T& lhs, const T& rhs) { T nrv(lhs); nrv += rhs; return nrv; } friend T operator +(T&& lhs, const T& rhs) { return std::move(lhs += rhs); } friend T operator +(const T& lhs, T&& rhs) { T nrv(lhs); nrv += boost::move(rhs); return nrv; } friend T operator +(T&& lhs, T&& rhs) { return boost::move(lhs += boost::move(rhs)); } This allows this to be done: val1 + val2 = val3; changing the return type to const T would allow the compiler to catch this, but now doing val1 + val2 + val3 must always use copy semantics instead of move semantics. I can't think of a way which would fix this issue without breaking the use of move semantics. How should we proceed with this? It's obviously bad usage, but the compiler should be able to catch this since it's easy to mistype + as =. Interestingly enough, doing testing with std::string shows the same "problem": std::string str1("hello"), str2(" "), str3("world"); str1 + str2 = str3; I tested this issue with std::string and found it in vs2012, gcc 4.3.2, and mingw/gcc 4.8.0. I don't have access to a compiler which pre-dates C++0x/C++11 so I don't know if this issue has always been present. Compiling with gcc 4.8.0 with - std=c++03 still has the issue.

3 3

Any interest in bitstream class?
by Paul Long 02 Jul '13

02 Jul '13

Same semantics as, e.g., stringstream, but it operates on binary data. I already have the analogues to istringstream/stringbuf (you can take a look at ibitstream/bitbuf at https://github.com/dplong/bstream) There are some interesting features, but I won't go into them here. If there is interest, I would implement obitstream and bitstream and possibly support Boost::dynamic_bitset. The rationale is _succinct_ expression of predictive parsing of binary data. I've used ibitstream in production code for decoding RTP headers and frames of various video encodings. Below is a simple function that decodes an RTP header using ibitstream; I also have a GitHub repo that contains more complex code for high-level parsing of H.264 frames at https://github.com/dplong/rtspudph264 struct RtpHeader { bool padding, marker; bitset<7> payloadType; WORD sequenceNumber; DWORD timestamp, ssrcIdentifier; vector<DWORD> csrcIdentifier; struct { bool present; WORD identifier; vector<BYTE> contents; } extension; }; bool ParseRtpHeader(const BYTE *buffer, RtpHeader &rtp) { ibitstream bin(buffer); static const bitset<2> version(0x2); bitset<4> csrcCount; WORD extensionLength; bin >> version >> rtp.padding >> rtp.extension.present >> csrcCount >> rtp.marker >> rtp.payloadType >> rtp.sequenceNumber >> rtp.timestamp >> rtp.ssrcIdentifier >> setrepeat(csrcCount.to_ulong()) >> rtp.csrcIdentifier; if (rtp.extension.present) { bin >> rtp.extension.identifier >> extensionLength >> setrepeat(extensionLength * sizeof(DWORD)) >> rtp.extension.contents; } return bin.good(); }

10 47

Re: [boost] [system] Static initialization of boost shared objects question
by Chris Stylianou 02 Jul '13

02 Jul '13

Has anyone looked into this issue, I am also experiencing the deadlock issue described above when using the boost libraries build in debug mode (GCC 1.48.0, 64bit) -- View this message in context: http://boost.2283326.n4.nabble.com/Static-initialization-of-boost-shared-ob… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 1

zlib not building (fedora x86_64)
by Neal Becker 02 Jul '13

02 Jul '13

I noticed zlib are not being built. I don't know why. rpm -qa zlib* zlib-1.2.7-9.fc18.i686 zlib-1.2.7-9.fc18.x86_64 zlib-devel-1.2.7-9.fc18.x86_64 bjam cxxflags=-march=native -sHAVE_ICU=1 -sEXPAT_INCLUDE=/usr - sEXPAT_LIBPATH=/usr/lib64 --layout=tagged threading=single,multi link=shared stage warning: No toolsets are configured. warning: Configuring default toolset "gcc". warning: If the default is wrong, your build may not work correctly. warning: Use the "toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html Performing configuration checks - 32-bit : no - 64-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : yes error: No best alternative for libs/coroutine/build/allocator_sources next alternative: required properties: <link>static <target-os>windows <threading>multi not matched next alternative: required properties: <link>static <segmented-stacks>on <threading>multi not matched next alternative: required properties: <link>static <threading>multi not matched - has_icu builds : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : no - iconv (libc) : yes - icu : yes - compiler-supports-ssse3 : yes - compiler-supports-avx2 : yes - gcc visibility : yes - long double support : yes warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. error: No best alternative for libs/coroutine/build/allocator_sources next alternative: required properties: <link>static <target-os>windows <threading>multi not matched next alternative: required properties: <link>static <segmented-stacks>on <threading>multi not matched next alternative: required properties: <link>static <threading>multi not matched - zlib : no (cached) Component configuration: - atomic : building - chrono : building - context : building - coroutine : building - date_time : building - exception : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - system : building - test : building - thread : building - timer : building - wave : building

1 0

boost 1.54.0 support for VS2013
by Charles_J_Wilson＠Dell.com 01 Jul '13

01 Jul '13

Has visualc.hpp been updated to support VC++12? (this was released in Visual Studio 2013 preview). I get the following issue with 1.54.0 beta built with VC++11 when compiling using VC++12: Error 1 error C2039: 'assert_not_arg' : is not a member of 'boost::mpl' (..\..\..\Logging\source\Core.cpp) C:\Users\Charles_J_Wilson\Documents\Projects\external\open_source\boost\1.54.0\boost_1_54_0\boost\iterator\detail\facade_iterator_category.hpp 166 Which is: # if !BOOST_WORKAROUND(BOOST_MSVC, <= 1300) BOOST_MPL_ASSERT_NOT((is_iterator_category<Traversal>)); # endif The beta doesn't recognize the compiler version and suggests running the config tests. Where are the instructions for that? Charles Wilson Principal Software Development Engineer Dell | Enterprise Solutions Group

2 1

[range] Time to merge Oven-to-Boost Extensions?
by Michel Morin 30 Jun '13

30 Jun '13

Hi, IIRC, the formal review is not necessary for the merge of Akira's Oven-to-Boost Extensions; only the range authors' review/permission are necessary. Neil, Nate, could we merge the extensions in the near future? I think everyone wants * `dropped` adaptor * `elements` adaptor * `taken` adaptor * `regular` utility so merging these first (and eventually merging the rest) would make the users happy. Regards, Michel

4 4

Re: [boost] Any interest in bitstream class?
by Brian Wood 30 Jun '13

30 Jun '13

From: Rob Stewart > On Jun 28, 2013, at 6:50 PM, Paul Long <plong(a)packetizer.com> wrote: > >> Correct, but it is important to note that integrals are always encoded big endian in the bitstream. I >>suppose it's possible that someone would want some other endian, but that's got to be an obscure use >>case. > > There are plenty of little endian only contexts that would want to avoid the host->network->host > conversions for all transfers. The C++ Middleware Writer uses a "receiver makes right" approach to support that. There's a SameFormat class here: http://webEbenezer.net/misc/Formatting.hh that's used when both sides have the same endian-ness. -- Brian Ebenezer Enterprises - Was Eisenhower the last decent US President? http://webEbenezer.net

2 1

Re: [boost] [Boost-users] Herb Sutter on C++ Standardization and Visual Studio
by Nathan Ridge 30 Jun '13

30 Jun '13

> Herb Sutter on C++ Standardization at Microsoft. > > http://channel9.msdn.com/Events/Build/2013/2-306 > > SGL Pretty good news, IMO. In addition to the C++11 and C++14 plans, Herb announced that Microsoft would complete the holes in their C++98 standard support by finally fixing their preprocessor and implementing correct two-phase name lookup (39:18 in the video). Perhaps the last discussion about these things [1] helped to tip the scale. In any case, I'm glad to hear it. Regards, Nate [1] http://boost.2283326.n4.nabble.com/C-announcements-coming-tomorrow-td463790…

1 0

boost::thread dependency on boost::chrono (windows implementation)
by Christian Hägele 28 Jun '13

28 Jun '13

Hello, as boost::thread now depends on boost::chrono I have the following questions: In boost::chrono on windows the the steady_clock is implemented via QueryPerformanceCounter. This may lead to wrong results because on some systems QueryPerformanceCounter gives different results on different processors. In our software we encountered theses problems regularly on some customers machines and thus stopped using QueryPerformanceCounter without additional checking. The problem I'm talking about is described as a TODO in boost/chrono/system_clocks.hpp My questions is if functions like boost::thread::timed_join or boost::mutex::timed_wait may have similar problems on hardware where QueryPerformanceCounter gives wrong result. Is there a way (like a preprocessor macro) to have boost::thread use the old implementation independent from boost::chrono? Regards, Christian

8 10

[1.54.0] Release candidates available
by Marshall Clow 28 Jun '13

28 Jun '13

Release candidate files for 1.54.0 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: efbfbff5a85a9330951f243d0a46e4b9 *boost_1_54_0_rc1.tar.gz 15cb8c0803064faef0c4ddf5bc5ca279 *boost_1_54_0_rc1.tar.bz2 78a35834c45220a6164310e280abe675 *boost_1_54_0_rc1.zip 89e734ffd2afe0982b2d9fc21d033dba *boost_1_54_0_rc1.7z Thanks! -- The release managers

6 9

Re: [boost] Could the custom allocator for flyweight hashed_factory be the boost::interprocess::allocator?
by JOAQUIN M. LOPEZ MUÑOZ 28 Jun '13

28 Jun '13

H Jin, ________________________________________ De: Boost [boost-bounces(a)lists.boost.org] en nombre de Jin Chen [chenjin92(a)gmail.com] Enviado el: lunes, 24 de junio de 2013 19:56 Para: Boost(a)lists.boost.org Asunto: [boost] Could the custom allocator for flyweight hashed_factory be the boost::interprocess::allocator? > I want to use boost::flyweight to do the dedupilcation of > boost::interprocess::basic_string object. I wrote a small test program for > that. In my program: > The flyweight works fine with the interprocess::basic_string which uses the > interprocess::allocator only with the default hashed_factory. The default > hashed_factory is ideal except that it uses std::allocator instead of > interprocess::allocator. I followed the > http://www.boost.org/doc/libs/1_53_0/libs/flyweight/doc/tutorial/configurat… > specifier > of a custom hash_factory which can change its allocator to the interprocess > one, but then got insanely long compiler error that is super hard to > decode... This is a very interesting exercise! There are several problems with your solution: * First of all, hashed_factory, as Jonathan points out, assumes the allocator is default constructible. As boost::interprocess::allocator needs a segment manager at construction time, you can overcome this by writing a custom interprocess allocator that takes that info statically, i.e., from a type that returns the segment manager: struct memory_dat_segment_manager { typedef ipc::managed_mapped_file::segment_manager type; static type* get() { static ipc::managed_mapped_file* segment= new ipc::managed_mapped_file(ipc::open_or_create,"memory.dat",409600); return segment->get_segment_manager(); } }; template<typename T,typename SegmentManager> struct segment_allocator: boost::interprocess::allocator<T,typename SegmentManager::type> { typedef boost::interprocess::allocator<T,typename SegmentManager::type> super; segment_allocator():super(SegmentManager::get()){} template<typename T2> segment_allocator(const segment_allocator<T2,SegmentManager>& x):super(x){} super& base(){return *this;} template<typename T2> struct rebind{ typedef segment_allocator<T2,SegmentManager> other; }; friend void swap(segment_allocator& x,segment_allocator& y) { swap(x.base(),y.base()); } }; Note that segment_allocator is default constructible: the segment is created on the first call to memory_dat_segment_manager. * Now, the holder class (www.boost.org/libs/flyweight/doc/tutorial/configuration.html#holders ) needs also to place its content in shared memory. As none of the holders provided by Boost.Flyweight does this, we must define our own: template<typename SegmentManager,typename C> struct segment_holder_class:boost::flyweights::holder_marker { static C& get() { static C* pc=SegmentManager::get()-> find_or_construct<C>(typeid(segment_holder_class).name())(); return *pc; } }; template<typename SegmentManager> struct segment_holder:boost::flyweights::holder_marker { template<typename C> struct apply { typedef segment_holder_class<SegmentManager,C> type; }; }; Again, the holder uses a SegmentManager class to get access to the segment manager * Finally, you need an interprocess locking policy (www.boost.org/libs/flyweight/doc/tutorial/configuration.html#locking ), and again this needs to be custom-defined (note that, in order for labeled_recursive_mutex to be default constructible, we get the info needed at construction time (the name of the mutex) from a Name class much in the same way we did with SegmentManager before for the allocator and holder): template<typename Name> struct labeled_recursive_mutex { typedef boost::interprocess::named_recursive_mutex mutex_type; operator mutex_type&() { static mutex_type mutex( boost::interprocess::open_or_create,Name::get()); return mutex; } }; template<typename Name> struct labeled_locking:boost::flyweights::locking_marker { typedef labeled_recursive_mutex<Name> mutex_type; typedef boost::interprocess::scoped_lock< typename labeled_recursive_mutex<Name>::mutex_type> lock_type; }; There's a technical issue here (if you don't get the following explanation you might as well skip it): As the mutex used by Boost.Flyweight is created by the holder class and we are using a shared-memory custom holder, it turns out labeled_recursive_mutex is thus created in shared memory. But boost::interprocess::named_recursive_mutex cannot be created in shared memory: we solve the problem with operator mutex_type&(), which actually creates the real mutex as a static variable in regular memory. And we're done. Find attached a small complete program showing how to put all the pieces together. Best, Joaquín M López Muñoz Telefónica Digital ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx

2 1

[Spirit] Retrieve informations out of tokens
by ... ... 27 Jun '13

27 Jun '13

Hi, I want to create a c++ syntax analysor (for creating auto-completion tools), and to help me, I want to use the boost.spirit library. In order to learn the basics of spirit, I executed this exercise. It is now working but I want to display the tokens' characters instead of counting tokens. The problem is I don't know the properties of the argument passed to my functor (the variable "t" in the code below). What is the type of this variable and what are the public method/attributes we can use on ? This is the code of my functor : struct counter{ counter() : j(0) {j = new int();} counter(const counter &model) : j(model.j) {} ~counter() {delete int;} template <typename Token> bool operator()(Token const& t){//I want to know the type of this variable t ++i; ++(*j); std::ostringstream oss; oss << "global : " << i << " membre : " << *j;//typeid(t).name(); printf("%s\n", oss.str().c_str()); return true; } int* j;}; The variable t will be relay to my functor by the following tokenize function : counter* foncteur = new counter();lex::tokenize(first, last, word_count_functor, *foncteur); I still have other questions : I read a consistent part of the documentation but I have not been able to define the type of regex used by boost.spirit. Which type is it ? What is the more appropriate function to use to analyse c++ synthax : tokenize or tokenize _and_parse ? You seems to describe tokenize_and_parse as a more powerful tool, but is it possible to define all the syntax of c++ using a parser ? Could I find an example of c++ syntax analysor using boost.spirit ? Any help would be appreciate,Cordialy,Guillaume Bersac237bis rue de Pessac33000 Bordeaux06.65.30.89.43

6 11

Re: [boost] [thread] synchronized_value: value and move semantics
by Ben Pope 27 Jun '13

27 Jun '13

On 21/02/13 02:02, Vicente J. Botet Escriba wrote: > > Hi, > > boost::synchronized_value (not released yet [1][2][3]) is based on [4]. > See below part of this paper adapted to the Boost.Thread interface. > > Currently boost::synchronized_value is in addition Copyable and > Swappable. I was wondering if it is worth adding value and move > semantics to synchronized_value. Making it EqualityComparable, > LessThanComparable and Movable if the underlying type satisfy these > requirements will allow to store them on a Boost.Container/C++11 container. > > Do you see something completely wrong with this addition? > Has some of you had a need for this? Could you share the context? Sorry, I'm a bit late to the party and not really answering the question. I can see the usefulness of synchronized_value for C++03, but not in C++11. It's just too easy to forget to call the synchronise() member: boost::synchronized_value<std::queue<int>> synch_queue; if(!synch_queue->empty()) synch_queue->pop(); when was was meant was (excuse use of auto, I've become lazy): boost::synchronized_value<std::queue<int>> synch_queue; { auto lock = synch_queue.synchronize(); if(!synch_queue->empty()) synch_queue->pop(); } This is neither safe or efficient (2 lock/unlocks). I think this should just not exist in C++11 and instead be replaced by something like monitor<T> described by Herb Sutter [1]: monitor<std::queue<int>> synch_queue; queue([](std::queue& q) { if(!q.empty()) q.pop(); } Now we're safe and efficient (one lock/unlock per block). Since movability is a C++11 thing, can we have something harder to use incorrectly than synchronized_value for C++11? I guess my point is rather than C++11ifying synchronized_value, can we have monitor instead? Thoughts? Ben [1] http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Herb-Sutter-Con… From 0:40:00

4 4

Interest in an 'either' library?
by David Sankel 26 Jun '13

26 Jun '13

**semantics**: template< typename left_type, typename right_type> struct either { // postcondition, is_left() either( left_type ); // postcondition, is_right() either( right_type ); bool is_left() const; bool is_right() const; // postcondition, is_left() either & operator=( left_type ); // postcondition, is_right() either & operator=( right_type ); // precondition, is_left() left_type left(); // precondition, is_right() right_type right(); private: }; **uses**: **Use 1**: Can be used as an alternative to exceptions or the (error codes+set reference idiom): either<error_code, file_id> load_file(...); vs. error_code load_file( file_id &, ... ); or // throws std::exception file_id load_file(...); **Use 2**: A lightweight alternative to boost::variant when only 2 components are required (either relates to variant in a similar way that pair relates to tuple ). variant<A,B> eitherAOrB; if( A * aPtr = boost::get<A>( &eitherAOrB ) ) std::cout << "A: " << *aPtr; else std::cout << "B: " << boost::get( eitherAOrB ); vs. either<A,B> eitherAOrB; if( eitherAOrB.is_left() ) std::cout << "A: " << eitherAOrB.left(); else std::cout << "B: " << eitherAOrB.right(); --David Sankel

12 41

[1.54.0] Release notes
by Daniel James 26 Jun '13

26 Jun '13

Hello everyone, It's time to send me your release notes, or if you're feeling enthusiastic, you can add them yourself at: http://svn.boost.org/svn/boost/website/public_html/live/feed/history/ You see the notes so far at: http://www.boost.org/users/history/version_1_54_0.html And while I'm at it, I've also added the new libraries to: http://www.boost.org/doc/libs/1_54_0/ thank you, Daniel

11 16

[1.54.0][range] add release note
by Akira Takahashi 26 Jun '13

26 Jun '13

Hi, I think missing Boost.Range release note for 1.54.0. https://svn.boost.org/svn/boost/website/public_html/live/feed/history/boost… Please see changeset: https://svn.boost.org/trac/boost/changeset/84823 Changeset 84823 Timestamp:06/17/13 22:22:07 Author:nathanridge Message:[range] Merge Boost.Range bug fixes to release branch (fixes #6944; fixes #7407; fixes #7408; fixes #7731; fixes #7827; fixes #8338; fixes #8453). Thanks, Akira

2 1

[Boost][asio]How add a timeout to asio connection?
by Renato Forti 25 Jun '13

25 Jun '13

Hi All, I have one problem, I have this class to connect to my server app: class session { public: static void init( const std::string& host, const std::string& port, hades::archive::archive& iarch, hades::archive::archive& oarch) { boost::asio::io_service io_service; client client(io_service, host, port, iarch, oarch); io_service.run(); } }; The problem is : if my server is down, my client (session) will block on io_service.run(); the client nerves end. Then I try to add a time out: class client { public: /// Constructor starts the asynchronous connect operation. client(boost::asio::io_service& io_service, const std::string& host, const std::string& port, // service hades::archive::archive& iarch, hades::archive::archive& oarch) : connection_(io_service) , deadline_(io_service) , iarch_(&iarch) , oarch_(&oarch) { deadline_.async_wait(boost::bind(&client::check_deadline, this)); deadline_.expires_from_now(boost::posix_time::seconds(30)); // Resolve the host name into an IP address. boost::asio::ip::tcp::resolver resolver(io_service); boost::asio::ip::tcp::resolver::query query(host, port); boost::asio::ip::tcp::resolver::iterator endpoint_iterator = resolver.resolve(query); // Start an asynchronous connect operation. boost::asio::async_connect(connection_.socket(), endpoint_iterator, boost::bind(&client::handle_connect, this, boost::asio::placeholders::error)); } /// Handle completion of a connect operation. void handle_connect(const boost::system::error_code& e) { if (!e) { // Successfully established connection. Start operation to read the list // of stocks. The connection::async_read() function will automatically // decode the data that is read from the underlying socket. connection_.async_read(*oarch_, boost::bind(&client::handle_read, this, boost::asio::placeholders::error)); connection_.async_write(*iarch_, boost::bind(&client::handle_write, this, boost::asio::placeholders::error)) ; } else { // An error occurred. throw sync_client_exception(e.message()); } } // Handle completion of a write operation. void handle_write(const boost::system::error_code& e) { } // Handle completion of a read operation. void handle_read(const boost::system::error_code& e) { } void check_deadline() { // Check whether the deadline has passed. We compare the deadline against // the current time since a new asynchronous operation may have moved the // deadline before this actor had a chance to run. if (deadline_.expires_at() <= deadline_timer::traits_type::now()) { // The deadline has passed. The socket is closed so that any outstanding // asynchronous operations are cancelled. connection_.socket().close(); // There is no longer an active deadline. The expiry is set to positive // infinity so that the actor takes no action until a new deadline is set. deadline_.expires_at(boost::posix_time::pos_infin); throw sync_client_exception("Time out : deadline on client!"); } // Put the actor back to sleep. deadline_.async_wait(boost::bind(&client::check_deadline, this)); } private: // The connection to the server. dsafe::sync::connection connection_; // The data received from the server. hades::archive::archive *iarch_; hades::archive::archive *oarch_; deadline_timer deadline_; }; The problem is that now the timeout expires even if the connection to the server occurs. What is wrong? My timeout should be disabled when the connection is successful! How do I get it? Only when the connection fails it should be called! Thanks for clarification

3 2

Could the custom allocator for flyweight hashed_factory be the boost::interprocess::allocator?
by Jin Chen 25 Jun '13

25 Jun '13

I want to use boost::flyweight to do the dedupilcation of boost::interprocess::basic_string object. I wrote a small test program for that. In my program: The flyweight works fine with the interprocess::basic_string which uses the interprocess::allocator only with the default hashed_factory. The default hashed_factory is ideal except that it uses std::allocator instead of interprocess::allocator. I followed the http://www.boost.org/doc/libs/1_53_0/libs/flyweight/doc/tutorial/configurat… specifier of a custom hash_factory which can change its allocator to the interprocess one, but then got insanely long compiler error that is super hard to decode... Right now, I don't know if only use interprocess::allocator in interprocess::basic_string alone will make the flyweight object be shared by multiple process, guess probably not... Then wonder whether that I didn't use the right syntax for custom hashed_factory or flyweight is compatible with boost::interprocess at all... If it is compatible, what's the right syntax for that? How shall I change my code? Below is a test program attached. The code could compile now with flyweight's default hashed_factory. The goal is to make it compile with ShmStringHashedFactory which use the interprocess allocator.

2 1

Proposal for a thread "collision" detector
by Gaetano Mendola 24 Jun '13

24 Jun '13

I would like to know if Boost community could be interested in adopting a check mechanism that is able to detect if a not supposed thread safe class is used by multiple threads in unsafe way. This tecnique has saved us a lot of headache especially when code refactoring on old code is performed. Better to explain it, without enter in the detail of the implementation, with some examples: Example: Queue implementation non thread-safe but still usable if clients are synchronized somehow. class NonThreadSafeQueue { public: ... void push(int) { DFAKE_SCOPED_LOCK(push_pop_); ... } int pop() { DFAKE_SCOPED_LOCK(push_pop_); ... } ... private: DFAKE_MUTEX(push_pop_); }; Example: Queue implementation not usable even if clients are synchronized, so only one thread in the class life cycle can use the two members push/pop. In this case the macro DFAKE_SCOPED_LOCK_THREAD_LOCKED pins the specified critical section the first time a thread enters push or pop, from that time on only that thread is allowed to execute push or pop. class NonThreadSafeQueue { public: ... void push(int) { DFAKE_SCOPED_LOCK_THREAD_LOCKED(push_pop_); ... } int pop() { DFAKE_SCOPED_LOCK_THREAD_LOCKED(push_pop_); ... } ... private: DFAKE_MUTEX(push_pop_); }; Example: Class that has to be contructed/destroyed on same thread, it has a "shareable" method (with external syncronization) and a not shareable method (even with external synchronization). In this case 3 Critical sections have to be defined class ExoticClass { public: ExoticClass() { DFAKE_SCOPED_LOCK_THREAD_LOCKED(ctor_dtor_); ... } ~ExoticClass() { DFAKE_SCOPED_LOCK_THREAD_LOCKED(ctor_dtor_); ... } void Shareable() { DFAKE_SCOPED_LOCK(shareable_section_); ... } void NotShareable() { DFAKE_SCOPED_LOCK_THREAD_LOCKED(ctor_dtor_); ... } ... private: DFAKE_MUTEX(ctor_dtor_) DFAKE_MUTEX(shareable_section_) }; DFAKE_SCOPED_LOCK will "throw an exception" or will call an "abort" in case of check failed. This tecnique doesn't involve real lock/unlock but uses atomic operations, also the various macros DFAKE_XXXXXXXXX are defined void when NDEBUG is defined. Any comment is appreciated. Regards Gaetano Mendola

3 3

The release branch is CLOSED - except by specific permission
by Marshall Clow 24 Jun '13

24 Jun '13

We're counting down to release next Monday. -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

1 0

Heads up - Release branch closed as of tomorrow
by Marshall Clow 24 Jun '13

24 Jun '13

Starting tomorrow (Monday, June 27), the release branch will be closed, except by permission from the release managers. -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

3 5

[smart_ptr] enable_shared_from_this and shared_ptr to a base class
by Adam Romanek 24 Jun '13

24 Jun '13

Hi, I have a question related to using shared_from_this() and a shared_ptr to a base class. Here's a modified version of the enable_shared_from_this usage example from its documentation web page: #include <boost/enable_shared_from_this.hpp> #include <boost/shared_ptr.hpp> #include <cassert> class X { public: virtual void foo() = 0; }; class Y: public X, public boost::enable_shared_from_this<Y> { virtual void foo() { shared_from_this(); } }; int main() { X* x_ptr = new Y; boost::shared_ptr<X> sp(x_ptr); sp->foo(); } First, class Y is now derived from class X. Secondly, shared_ptr's template argument is now X and the parameter to the shared_ptr's constructor is now a pointer to X. Now, calling shared_from_this() in X and/or Y throws boost::bad_weak_ptr. Is this correct behavior? Is it documented somewhere? I know that the example is a bit unrealistic since most of the time shared_ptr is constructed directly from the pointer returned by 'new Y' or created by make_shared() but still, this is something that bothers me. WBR, Adam Romanek

3 9

Boost.Spirit how to use token in functor
by ... ... 24 Jun '13

24 Jun '13

Hi, I have a functor which is working, but its argument, which I don't know its type, I don't know what to do with it. I want to extract data out of it, I want to know is beginning and its end, I want to display the the content of the string character in my consol... but I can't retrieve this information. How could I archieve it ? What is the type of the argument relay to my function ? Is there a dOxygen like documentation (the one on the Boost site is great but a formal documentaton is also interesting). Where is the description and code source of this type ? Here is the code of my functor : struct counter{ counter() : j(0) {j = new int();} counter(const counter &model) : j(model.j) {} template <typename Token> bool operator()(Token const& t){// t is the argument I want to use ++i; ++(*j); std::ostringstream oss; oss << "global : " << i << " membre : " << *j;//typeid(t).name(); printf("%s\n", oss.str().c_str()); return true; } int* j;}; Thanks every one, cordialy,Guillaume Bersac237bis rue de Pessac33000 Bordeaux06.65.30.89.43

2 1

Re: [boost] De Bruijn Bind (alternate bind syntax) Interest?
by Larry Evans 24 Jun '13

24 Jun '13

On 09/02/10 16:08, David Sankel wrote:> 2010/9/2 David Sankel <camior(a)gmail.com> > >> 2010/9/2 Dave Abrahams <dave(a)boostpro.com> >> >> On Thu, Sep 2, 2010 at 11:57 AM, David Sankel <camior(a)gmail.com> wrote: >>> >>>> Hello all, >>>> >>>> I've been working on an alternate bind syntax based on De Bruijn >>>> indices[1]. >>>> The syntax is very simple, yet the terms are very powerful. >>>> >>>> Here is an example of a function const that takes in an argument c and >>>> returns another function that, for all input, returns c: >>>> >>>> //λx.λy.x = λλ1 with De Bruijn indices. >>>> >>> >>> Not according to the page you linked below. What am I missing? >>> >>> [1] http://en.wikipedia.org/wiki/De_Bruijn_index >>> >> >> Sorry about that. The wikipedia page uses 1-indexed indices where I'm using >> 0-indexed indices. So, increment 1 on all my examples to get the wikipedia >> syntax. >> > > I'm beginning to think it is better to use 1-indexing instead of 0-indexing > all around. It will be both compatible with the Wikipedia page and familiar > to boost bind/lambda users. > > Funny thing is, I started with 1-indexing but changed it to 0-indexing for > the fallacious reasoning of the arrrrgh function that Dave A mentioned. > Hi David, I looked at the web page mentioned in your first post to this thread and could not understand the flip example: For flip, I'm introducing subscripts on abstractions (λ) to indicate the number of arguments. For the variables (1,2,etc.) I use a subscript to indicate which argument of the abstraction it refers to. flip = λx.λ(y,z).x(z,y) = λ₁λ₂1(1₁, 2₀) which seems to have a 0 for the subscript of 2. and 1 for the subscript of 1. That's consistent with the argument indices starting at 0 (1₁ corresponds z {the 2nd argument in the argument list, (z,y)}, and 2₀ corresponds to y {the 1st argument in the argument list, (z,y)}); however, subscrited numbers should be the same since both y and z are bound by the same lamba, the nearest one corresponding to number 1. Hence, shouldn't the above be: flip = λx.λ(y,z).x(z,y) = λ₁λ₂2₀(1₁, 1₀) ? Also, since the abstraction indices seem to start at 1, shouldn't the argument indices also start at 1? I think that would make the notation more consistent, and would result in: flip = λx.λ(y,z).x(z,y) = λ₁λ₂2_1(1_2, 1_1) (where a subscript of I have been replaced with _I).

2 1

Error while linking boost. spirit
by ... ... 23 Jun '13

23 Jun '13

Hi, I just downloaded, compiled and install boost.It seems like the installation process worked fine and I successfully compiled a program using boost (boost.log for instance). But when I try to compile an example writed by the developpers of boost.spirit, it fail ! It doesn't seem like it's an inclusion resolution problems, I don't know what to do. Please help me. Here is my code (I paste it from this page) : #include <stdio.h>#include <stdlib.h> #include <boost/spirit/include/lex_lexertl.hpp>#include <boost/spirit/include/phoenix_operator.hpp>#include <boost/spirit/include/phoenix_statement.hpp>#include <boost/spirit/include/phoenix_algorithm.hpp>#include <boost/spirit/include/phoenix_core.hpp>#define BOOST_ALL_DYN_LINK//without it boost.log glitch#include <boost/log/trivial.hpp> int main(){ BOOST_LOG_TRIVIAL(trace) << "boost.log is working !"; typedef lex::lexertl::token<char const*, lex::omit, boost::mpl::false_> token_type; typedef lex::lexertl::actor_lexer<token_type> lexer_type; word_count_tokens<lexer_type> word_count_lexer; std::string str (read_from_file("mainwindow.cpp.txt")); char const* first = str.c_str(); char const* last = &first[str.size()]; lexer_type::iterator_type iter = word_count_lexer.begin(first, last); lexer_type::iterator_type end = word_count_lexer.end(); while (iter != end && token_is_valid(*iter)) ++iter; if (iter == end) { std::cout << "lines: " << word_count_lexer.l << ", words: " << word_count_lexer.w << ", characters: " << word_count_lexer.c << "\n"; } else { std::string rest(first, last); std::cout << "Lexical analysis failed\n" << "stopped at: \"" << rest << "\"\n"; } return 0; }} And here is my error log : 11:32:39 **** Incremental Build of configuration Default for project synthax_analyser ****make all g++ -O2 -g -Wall -fmessage-length=0 -c -o synthax_analyser.o synthax_analyser.cppsynthax_analyser.cpp: In function ‘int main()’:synthax_analyser.cpp:24:4: error: ‘lex’ does not name a typesynthax_analyser.cpp:27:10: error: ‘lex’ does not name a typesynthax_analyser.cpp:29:2: error: ‘word_count_tokens’ was not declared in this scopesynthax_analyser.cpp:29:20: error: ‘lexer_type’ was not declared in this scopesynthax_analyser.cpp:29:20: note: suggested alternative:In file included from /usr/local/include/boost/spirit/home/lex/meta_compiler.hpp:16:0, from /usr/local/include/boost/spirit/home/lex/reference.hpp:14, from /usr/local/include/boost/spirit/home/lex/lexer/token_def.hpp:21, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:14, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/spirit/home/lex/lexer_type.hpp:20:12: note: ‘boost::spirit::lex::lexer_type’synthax_analyser.cpp:29:32: error: ‘word_count_lexer’ was not declared in this scopesynthax_analyser.cpp:31:54: error: ‘read_from_file’ was not declared in this scopesynthax_analyser.cpp:35:2: error: ‘lexer_type’ is not a class or namespacesynthax_analyser.cpp:35:28: error: expected ‘;’ before ‘iter’synthax_analyser.cpp:36:3: error: ‘lexer_type’ is not a class or namespacesynthax_analyser.cpp:36:29: error: expected ‘;’ before ‘end’synthax_analyser.cpp:38:9: error: ‘iter’ was not declared in this scopesynthax_analyser.cpp:38:17: error: ‘end’ was not declared in this scopesynthax_analyser.cpp:38:17: note: suggested alternatives:In file included from /usr/local/include/boost/range/empty.hpp:20:0, from /usr/local/include/boost/proto/functional/range/empty.hpp:12, from /usr/local/include/boost/proto/functional/range.hpp:13, from /usr/local/include/boost/proto/functional.hpp:14, from /usr/local/include/boost/proto/proto.hpp:16, from /usr/local/include/boost/spirit/home/support/terminal.hpp:18, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/range/end.hpp:106:61: note: ‘boost::range_adl_barrier::end’In file included from /usr/local/include/boost/fusion/container/list/cons.hpp:14:0, from /usr/local/include/boost/fusion/iterator/segmented_iterator.hpp:13, from /usr/local/include/boost/fusion/sequence/intrinsic/detail/segmented_begin.hpp:11, from /usr/local/include/boost/fusion/sequence/intrinsic/begin.hpp:17, from /usr/local/include/boost/fusion/container/vector/vector10.hpp:15, from /usr/local/include/boost/fusion/container/vector.hpp:12, from /usr/local/include/boost/fusion/include/vector.hpp:10, from /usr/local/include/boost/spirit/home/phoenix/core/limits.hpp:73, from /usr/local/include/boost/spirit/home/phoenix/core.hpp:11, from /usr/local/include/boost/spirit/include/phoenix_core.hpp:14, from /usr/local/include/boost/spirit/home/support/terminal.hpp:16, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/fusion/sequence/intrinsic/end.hpp:89:5: note: ‘boost::fusion::end’In file included from /usr/local/include/boost/fusion/sequence/intrinsic/begin.hpp:13:0, from /usr/local/include/boost/fusion/container/vector/vector10.hpp:15, from /usr/local/include/boost/fusion/container/vector.hpp:12, from /usr/local/include/boost/fusion/include/vector.hpp:10, from /usr/local/include/boost/spirit/home/phoenix/core/limits.hpp:73, from /usr/local/include/boost/spirit/home/phoenix/core.hpp:11, from /usr/local/include/boost/spirit/include/phoenix_core.hpp:14, from /usr/local/include/boost/spirit/home/support/terminal.hpp:16, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/fusion/sequence/intrinsic_fwd.hpp:67:16: note: ‘boost::fusion::result_of::end’In file included from /usr/local/include/boost/fusion/support/sequence_base.hpp:11:0, from /usr/local/include/boost/fusion/container/vector/vector10.hpp:11, from /usr/local/include/boost/fusion/container/vector.hpp:12, from /usr/local/include/boost/fusion/include/vector.hpp:10, from /usr/local/include/boost/spirit/home/phoenix/core/limits.hpp:73, from /usr/local/include/boost/spirit/home/phoenix/core.hpp:11, from /usr/local/include/boost/spirit/include/phoenix_core.hpp:14, from /usr/local/include/boost/spirit/home/support/terminal.hpp:16, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/mpl/begin_end_fwd.hpp:23:38: note: ‘boost::mpl::end’In file included from /usr/local/include/boost/proto/functional/range.hpp:14:0, from /usr/local/include/boost/proto/functional.hpp:14, from /usr/local/include/boost/proto/proto.hpp:16, from /usr/local/include/boost/spirit/home/support/terminal.hpp:18, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/proto/functional/range/end.hpp:19:12: note: ‘boost::proto::functional::end’In file included from /usr/local/include/boost/range/empty.hpp:20:0, from /usr/local/include/boost/proto/functional/range/empty.hpp:12, from /usr/local/include/boost/proto/functional/range.hpp:13, from /usr/local/include/boost/proto/functional.hpp:14, from /usr/local/include/boost/proto/proto.hpp:16, from /usr/local/include/boost/spirit/home/support/terminal.hpp:18, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/range/end.hpp:106:61: note: ‘boost::range_adl_barrier::end’In file included from /usr/local/include/boost/spirit/home/support/string_traits.hpp:16:0, from /usr/local/include/boost/spirit/home/support/nonterminal/expand_arg.hpp:20, from /usr/local/include/boost/spirit/home/support/context.hpp:18, from /usr/local/include/boost/spirit/home/qi/domain.hpp:18, from /usr/local/include/boost/spirit/home/qi/parser.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/token_def.hpp:17, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:14, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/spirit/home/support/container.hpp:445:5: note: ‘boost::spirit::traits::end’In file included from /usr/local/include/boost/spirit/home/support/handles_container.hpp:14:0, from /usr/local/include/boost/spirit/home/lex/lexer/token_def.hpp:16, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:14, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/spirit/home/support/attributes_fwd.hpp:43:12: note: ‘boost::spirit::result_of::end’In file included from /usr/local/include/boost/spirit/home/support/info.hpp:17:0, from /usr/local/include/boost/spirit/home/lex/lexer/token_def.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:14, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/foreach.hpp:730:1: note: ‘boost::foreach_detail_::end’synthax_analyser.cpp:38:44: error: ‘token_is_valid’ was not declared in this scopesynthax_analyser.cpp:38:44: note: suggested alternatives:In file included from /usr/local/include/boost/spirit/home/lex/lexer/lexertl/lexer.hpp:20:0, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:16, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/spirit/home/lex/lexer/lexertl/token.hpp:415:5: note: ‘boost::spirit::lex::lexertl::token_is_valid’In file included from /usr/local/include/boost/spirit/home/lex/lexer/lexertl/iterator.hpp:18:0, from /usr/local/include/boost/spirit/home/lex/lexer/lexertl/lexer.hpp:23, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:16, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/spirit/home/support/iterators/detail/split_functor_input_policy.hpp:19:21: note: ‘boost::spirit::iterator_policies::split_functor_input_is_valid_test_::token_is_valid’synthax_analyser.cpp:41:7: error: ‘iter’ was not declared in this scopesynthax_analyser.cpp:41:15: error: ‘end’ was not declared in this scopesynthax_analyser.cpp:41:15: note: suggested alternatives:In file included from /usr/local/include/boost/range/empty.hpp:20:0, from /usr/local/include/boost/proto/functional/range/empty.hpp:12, from /usr/local/include/boost/proto/functional/range.hpp:13, from /usr/local/include/boost/proto/functional.hpp:14, from /usr/local/include/boost/proto/proto.hpp:16, from /usr/local/include/boost/spirit/home/support/terminal.hpp:18, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/range/end.hpp:106:61: note: ‘boost::range_adl_barrier::end’In file included from /usr/local/include/boost/fusion/container/list/cons.hpp:14:0, from /usr/local/include/boost/fusion/iterator/segmented_iterator.hpp:13, from /usr/local/include/boost/fusion/sequence/intrinsic/detail/segmented_begin.hpp:11, from /usr/local/include/boost/fusion/sequence/intrinsic/begin.hpp:17, from /usr/local/include/boost/fusion/container/vector/vector10.hpp:15, from /usr/local/include/boost/fusion/container/vector.hpp:12, from /usr/local/include/boost/fusion/include/vector.hpp:10, from /usr/local/include/boost/spirit/home/phoenix/core/limits.hpp:73, from /usr/local/include/boost/spirit/home/phoenix/core.hpp:11, from /usr/local/include/boost/spirit/include/phoenix_core.hpp:14, from /usr/local/include/boost/spirit/home/support/terminal.hpp:16, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/fusion/sequence/intrinsic/end.hpp:89:5: note: ‘boost::fusion::end’In file included from /usr/local/include/boost/fusion/sequence/intrinsic/begin.hpp:13:0, from /usr/local/include/boost/fusion/container/vector/vector10.hpp:15, from /usr/local/include/boost/fusion/container/vector.hpp:12, from /usr/local/include/boost/fusion/include/vector.hpp:10, from /usr/local/include/boost/spirit/home/phoenix/core/limits.hpp:73, from /usr/local/include/boost/spirit/home/phoenix/core.hpp:11, from /usr/local/include/boost/spirit/include/phoenix_core.hpp:14, from /usr/local/include/boost/spirit/home/support/terminal.hpp:16, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/fusion/sequence/intrinsic_fwd.hpp:67:16: note: ‘boost::fusion::result_of::end’In file included from /usr/local/include/boost/fusion/support/sequence_base.hpp:11:0, from /usr/local/include/boost/fusion/container/vector/vector10.hpp:11, from /usr/local/include/boost/fusion/container/vector.hpp:12, from /usr/local/include/boost/fusion/include/vector.hpp:10, from /usr/local/include/boost/spirit/home/phoenix/core/limits.hpp:73, from /usr/local/include/boost/spirit/home/phoenix/core.hpp:11, from /usr/local/include/boost/spirit/include/phoenix_core.hpp:14, from /usr/local/include/boost/spirit/home/support/terminal.hpp:16, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/mpl/begin_end_fwd.hpp:23:38: note: ‘boost::mpl::end’In file included from /usr/local/include/boost/proto/functional/range.hpp:14:0, from /usr/local/include/boost/proto/functional.hpp:14, from /usr/local/include/boost/proto/proto.hpp:16, from /usr/local/include/boost/spirit/home/support/terminal.hpp:18, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/proto/functional/range/end.hpp:19:12: note: ‘boost::proto::functional::end’In file included from /usr/local/include/boost/range/empty.hpp:20:0, from /usr/local/include/boost/proto/functional/range/empty.hpp:12, from /usr/local/include/boost/proto/functional/range.hpp:13, from /usr/local/include/boost/proto/functional.hpp:14, from /usr/local/include/boost/proto/proto.hpp:16, from /usr/local/include/boost/spirit/home/support/terminal.hpp:18, from /usr/local/include/boost/spirit/home/support/common_terminals.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/terminals.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:13, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/range/end.hpp:106:61: note: ‘boost::range_adl_barrier::end’In file included from /usr/local/include/boost/spirit/home/support/string_traits.hpp:16:0, from /usr/local/include/boost/spirit/home/support/nonterminal/expand_arg.hpp:20, from /usr/local/include/boost/spirit/home/support/context.hpp:18, from /usr/local/include/boost/spirit/home/qi/domain.hpp:18, from /usr/local/include/boost/spirit/home/qi/parser.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer/token_def.hpp:17, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:14, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/spirit/home/support/container.hpp:445:5: note: ‘boost::spirit::traits::end’In file included from /usr/local/include/boost/spirit/home/support/handles_container.hpp:14:0, from /usr/local/include/boost/spirit/home/lex/lexer/token_def.hpp:16, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:14, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/spirit/home/support/attributes_fwd.hpp:43:12: note: ‘boost::spirit::result_of::end’In file included from /usr/local/include/boost/spirit/home/support/info.hpp:17:0, from /usr/local/include/boost/spirit/home/lex/lexer/token_def.hpp:15, from /usr/local/include/boost/spirit/home/lex/lexer.hpp:14, from /usr/local/include/boost/spirit/home/lex.hpp:13, from /usr/local/include/boost/spirit/home/lex/lexer_lexertl.hpp:15, from /usr/local/include/boost/spirit/include/lex_lexertl.hpp:16, from synthax_analyser.cpp:12:/usr/local/include/boost/foreach.hpp:730:1: note: ‘boost::foreach_detail_::end’synthax_analyser.cpp: At global scope:synthax_analyser.cpp:54:1: error: expected declaration before ‘}’ tokenmake: *** [synthax_analyser.o] Error 1 Cordialy,Guillaume Bersac237bis rue de Pessac33000 Bordeaux06.65.30.89.43

5 5

concurrent garbage collector
by Taylor Holliday 23 Jun '13

23 Jun '13

Hey Boost, After struggling with breaking shared_ptr cycles in my app, I wrote a little concurrent garbage collector which uses boost::lockfree::queue. Its actually fairly general purpose, and I've released the code here: https://gist.github.com/wtholliday/5793270 Inspired by my question on stack overflow: http://stackoverflow.com/questions/17116189/concurrent-garbage-collection-f… I'm also working on releasing my unit test... its just quite dependent on other code. For the interface: the basic idea is you have a RootPtr<T> used to manage the collector's root set (please forgive my propensity for CamelCase). You have to explicitly manage references between collectable objects (via AddEdge and RemoveEdge functions), but I think that could be made safe using another smart pointer type which knows the collectable object which owns it. At this point I'm not too concerned about performance, as my object graphs aren't that big. I bet a GC guru could implement this without using a queue of events. Anyway, this is the kind of thing I'd love to see in boost someday, so it would be great to read your opinions of it :-) cheers - Taylor W. Taylor Holliday, Owner/Founder Subatomic Software, San Francisco

3 4

Re: [boost] [Multiprecision] Does MP use references internally?
by Daryle Walker 21 Jun '13

21 Jun '13

Nearly all operators, besides assigning and dereferencing ones, are supposed to return by value. Changing that, even with the “innocuous” (unary)+, is surprising. Daryle W. Sent from Windows Mail From: John Maddock Sent: ‎Thursday‎, ‎June‎ ‎20‎, ‎2013 ‎4‎:‎13‎ ‎AM To: boost(a)lists.boost.org > Is Boost.MP giving users references-to-types instead of class types when > requesting a numeric type? Pointers may be objects in and of themselves, > but references aren't; they're just aliases; trying to intentionally use > them as first-class objects is arguably broken. I don't see why this is a problem, but the first error is coming from: auto const aa = +a, bb = +b; Now, in Boost.Multiprecision the unary operator+ is a noop that returns a reference to self, could that be a cause of the issue?

4 3

ptr_map_adapter::insert non const key argument
by Gaetano Mendola 21 Jun '13

21 Jun '13

Hi, it seems that the method: std::pair<iterator,bool> ptr_map_adapter::insert( key_type& key, mapped_type x ) has the key argument non const? Is there a valid reason for it or it's just a mistake? Regards Gaetano Mendola

3 4

How do I specify no padding bytes within a struct/class?
by Daryle Walker 20 Jun '13

20 Jun '13

I've never done this before, so I'm asking first: how do I specify that a struct/class should have no padding at all, at the start, end, or middle? My classes have internal arrays, and specifying no padding lets users use an array of classX<T> as an array of T (just like C++11 std::complex). Complier-specific answers are OK, as long as I can use preprocessor flags to isolate them. I have a preprocessor flag that's currently set to 0 to indicate that there's no packing. I'll change it to 1 whenever I get a compiler's packing support. Daryle W.

5 7

[Multiprecision] Does MP use references internally?
by Daryle Walker 20 Jun '13

20 Jun '13

This may be an artifact of the compiler's error reporting mechanism, but the errors' expansion of the MultiPrecision type I'm using has reference types in it. Types from Boost.MP seem to be a shell class template that wraps an engine and several options. Some of the errors that pop up when using Boost.MP when using Boost.Test with my custom complex-number class: - Boost.MPL calls within Boost.Test complain that it's trying to get a pointer to a reference. - My own code uses arrays everywhere, and I get errors about making arrays to references. I'm not doing anything (too) advanced. Is Boost.MP giving users references-to-types instead of class types when requesting a numeric type? Pointers may be objects in and of themselves, but references aren't; they're just aliases; trying to intentionally use them as first-class objects is arguably broken. Daryle W.

2 2

Re: [boost] [c++11]
by Niall Douglas 19 Jun '13

19 Jun '13

> I wasn't suggesting making the library strictly C++03-compatible. My main > point was that the library has to be compatible with _todays_ and even better > - _yesterdays_ compilers to be actually useful. My choice of "reasonable" time > frame is 3-5 years, as I mentioned. That includes VS 2008 and VS 2010, which > already had some C++11 features, including rvalue references. Making VS 2013 > absolute minimum is a no-go, IMHO. I don't think anyone is making VS2013 an absolute minimum - rather they're making variadic templates an absolute minimum. Something which any other compiler than VS has had for years, and something which unlike many, if not most other C++11 language features is something which lets you write a ton of stuff you simply can't write without them. Now, nothing in proposed Boost.AFIO uses variadic templates in a way not replaceable with preprocessor programming. However it very /nearly/ did: I had this neato bit of evil variadic instantiation which let you convert an unknown set of trailing args into a std::tuple<> for storage, then /unpack/ said std::tuple<> back into an unknown set of trailing args, all with perfect forwarding. Effectively it was a compile-time std::function<> implementation. As proposed Boost.AFIO is also a closure execution engine where that closure can take arbitrary args and return arbitrary returns, that evil variadic template machinery was really useful because it lets you skip using std::function<> with its implied virtual function call. As proposed Boost.AFIO currently nests, in the worst case scenario, a fully bound std::function<> calling a partially bound std::function<> calling a partially bound std::function<>, that's three nested virtual indirect function calls. Recent Intel CPUs can prefetch and branch predict two nesting levels, but they can't cope with three, so performance takes a real nose dive and hence one of the reasons we currently see a peak 80k IOPS. That evil variadic template machinery gets rid of that problem. And its only replacement is std::function<> - you *cannot* implement that functionality (pure compile time std::function<>) without variadic templates because you can't properly unpack them without. None of this matters for proposed Boost.AFIO. But it certainly matters for the forthcoming C++11 only libraries coming soon to Boost, because they make /very/ heavy usage of functionality only possible with variadic templates. That means that they will require, as an absolute minimum for VS, VS2013 or Nov 2012 CTP. Other C++11 features one can make do without without too much cost, but losing variadic templates means a ton of extra source code complexity, much longer compile times and chopping out a lot of what C++11 enables which simply can't be done in C++03. I suspect that those libraries are probably going to force a new "variadic template support is mandatory" category of Boost libraries, probably sooner rather than later. I agree it's going to be frustrating for those stuck with older compilers: I pity those whose employers force MSVC6 on them to this very day. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

6 15

Can't compile code with BOOST_LOG_TRIVIAL
by ... ... 19 Jun '13

19 Jun '13

Hi, I am trying to compile this code : #include <boost/log/trivial.hpp> int main(void){ BOOST_LOG_TRIVIAL(trace) << "boost log is working"; return EXIT_SUCCESS;} And I get the following error message : g++ -o test Capture.o ffmpegTools.o FluxVideoModifie.o test.o vizILogger.o -lavformat -lavcodec -lavutil -lswscale -lopencv_core -lopencv_highgui -lboost_filesystem -lboost_log_setup -lboost_log -lz -lpthread -ldl -lm test.o: In function `main':/home/exploit/git/VIZIRD-CAPTURE/proj/capture//test.cpp:39: undefined reference to `boost::log::v2s_mt_posix::trivial::logger::get()'/home/exploit/git/VIZIRD-CAPTURE/proj/capture//test.cpp:39: undefined reference to `boost::log::v2s_mt_posix::trivial::logger::get()'test.o: In function `boost::log::v2s_mt_posix::record::reset()':/usr/local/include/boost/log/core/record.hpp:153: undefined reference to `boost::log::v2s_mt_posix::record_view::public_data::destroy(boost::log::v2s_mt_posix::record_view::public_data const*)'test.o: In function `boost::log::v2s_mt_posix::record boost::log::v2s_mt_posix::sources::basic_composite_logger<char, boost::log::v2s_mt_posix::sources::severity_logger_mt<boost::log::v2s_mt_posix::trivial::severity_level>, boost::log::v2s_mt_posix::sources::multi_thread_model<boost::log::v2s_mt_posix::aux::light_rw_mutex>, boost::log::v2s_mt_posix::sources::features<boost::log::v2s_mt_posix::sources::severity<boost::log::v2s_mt_posix::trivial::severity_level>, void, void, void, void, void, void, void, void, void> >::open_record<boost::parameter::aux::tagged_argument<boost::log::v2s_mt_posix::keywords::tag::severity, boost::log::v2s_mt_posix::trivial::severity_level const> >(boost::parameter::aux::tagged_argument<boost::log::v2s_mt_posix::keywords::tag::severity, boost::log::v2s_mt_posix::trivial::severity_level const> const&)':/usr/local/include/boost/log/sources/basic_logger.hpp:457: undefined reference to `boost::log::v2s_mt_posix::core::get_logging_enabled() const'test.o: In function `~record_pump':/usr/local/include/boost/log/sources/record_ostream.hpp:278: undefined reference to `boost::log::v2s_mt_posix::aux::unhandled_exception_count()'test.o: In function `record_pump':/usr/local/include/boost/log/sources/record_ostream.hpp:259: undefined reference to `boost::log::v2s_mt_posix::aux::stream_provider<char>::allocate_compound(boost::log::v2s_mt_posix::record&)'/usr/local/include/boost/log/sources/record_ostream.hpp:259: undefined reference to `boost::log::v2s_mt_posix::aux::unhandled_exception_count()'test.o: In function `~auto_release':/usr/local/include/boost/log/sources/record_ostream.hpp:243: undefined reference to `boost::log::v2s_mt_posix::aux::stream_provider<char>::release_compound(boost::log::v2s_mt_posix::aux::stream_provider<char>::stream_compound*)'test.o: In function `boost::log::v2s_mt_posix::sources::aux::severity_level<boost::log::v2s_mt_posix::trivial::severity_level>::set_value(boost::log::v2s_mt_posix::trivial::severity_level)':/usr/local/include/boost/log/sources/severity_feature.hpp:135: undefined reference to `boost::log::v2s_mt_posix::sources::aux::get_severity_level()'test.o: In function `boost::log::v2s_mt_posix::record boost::log::v2s_mt_posix::sources::basic_logger<char, boost::log::v2s_mt_posix::sources::severity_logger_mt<boost::log::v2s_mt_posix::trivial::severity_level>, boost::log::v2s_mt_posix::sources::multi_thread_model<boost::log::v2s_mt_posix::aux::light_rw_mutex> >::open_record_unlocked<boost::parameter::aux::tagged_argument<boost::log::v2s_mt_posix::keywords::tag::severity, boost::log::v2s_mt_posix::trivial::severity_level const> >(boost::parameter::aux::tagged_argument<boost::log::v2s_mt_posix::keywords::tag::severity, boost::log::v2s_mt_posix::trivial::severity_level const> const&)':/usr/local/include/boost/log/sources/basic_logger.hpp:260: undefined reference to `boost::log::v2s_mt_posix::core::open_record(boost::log::v2s_mt_posix::attribute_set const&)'test.o: In function `boost::log::v2s_mt_posix::core::push_record(boost::rv<boost::log::v2s_mt_posix::record>&)':/usr/local/include/boost/log/core/core.hpp:308: undefined reference to `boost::log::v2s_mt_posix::core::push_record_move(boost::log::v2s_mt_posix::record&)'collect2: ld returned 1 exit statusmake: *** [test] Error 1 In my makefile I added the links :LIBS_boost = -lboost_filesystem -lboost_log_setup -lboost_log And i have my libraries correctly installed because the command : $ sudo ldconfig -p | grep boost_l display :libboost_log_setup.so.1.53.0 (libc6,x86-64) => /usr/local/lib/libboost_log_setup.so.1.53.0libboost_log_setup.so (libc6,x86-64) => /usr/local/lib/libboost_log_setup.solibboost_log.so.1.53.0 (libc6,x86-64) => /usr/local/lib/libboost_log.so.1.53.0libboost_log.so (libc6,x86-64) => /usr/local/lib/libboost_log.solibboost_locale.so.1.53.0 (libc6,x86-64) => /usr/local/lib/libboost_locale.so.1.53.0libboost_locale.so (libc6,x86-64) => /usr/local/lib/libboost_loc Can you help me please ? Thanks,Guillaume Bersac237bis rue de Pessac33000 Bordeaux06.65.30.89.43

2 1

Weirdness in SVN
by Marshall Clow 19 Jun '13

19 Jun '13

Ok, this is quite worrisome to me. This morning, bug #6136 was reopened: https://svn.boost.org/trac/boost/ticket/6136 This is an "unused variable warning" in Boost.DateTime. I fixed this bug in the trunk: https://svn.boost.org/trac/boost/changeset/80699 I merged this bug fix (and several others) to the release branch: https://svn.boost.org/trac/boost/changeset/80797 But the files (both trunk and release) appear not to contain the change. If I do a "svn diff", the changes appear in the diff, but the file doesn't contain the change. I checked the other files referenced in change set 80797, and they appear to be fine - just this one. Any idea what could be happening here? My only explanation at the moment is that "Subversion is lying to me", and that's both (a) a huge potential problem, and (b) doesn't suggest a course of action. $ svn diff trunk/boost/date_time/format_date_parser.hpp -r 80698 Index: trunk/boost/date_time/format_date_parser.hpp =================================================================== --- trunk/boost/date_time/format_date_parser.hpp (revision 80698) +++ trunk/boost/date_time/format_date_parser.hpp (working copy) @@ -256,7 +256,6 @@ // skip leading whitespace while(std::isspace(*sitr) && sitr != stream_end) { ++sitr; } - charT current_char = *sitr; short year(0), month(0), day(0), day_of_year(0);// wkday(0); /* Initialized the following to their minimum values. These intermediate @@ -290,7 +289,6 @@ } wkday = mr.current_match; if (mr.has_remaining()) { - current_char = mr.last_char(); use_current_char = true; } break; @@ -310,7 +308,6 @@ } wkday = mr.current_match; if (mr.has_remaining()) { - current_char = mr.last_char(); use_current_char = true; } break; @@ -326,7 +323,6 @@ } t_month = month_type(mr.current_match); if (mr.has_remaining()) { - current_char = mr.last_char(); use_current_char = true; } break; @@ -342,7 +338,6 @@ } t_month = month_type(mr.current_match); if (mr.has_remaining()) { - current_char = mr.last_char(); use_current_char = true; } break; @@ -438,7 +433,6 @@ itr++; if (use_current_char) { use_current_char = false; - current_char = *sitr; } else { sitr++; $ svn diff trunk/boost/date_time/format_date_parser.hpp -r 80699 $ -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

2 3

[range] Best way to count the elements in a filtered range?
by Gonzalo Brito Gadeschi 19 Jun '13

19 Jun '13

I wonder what is the recommended way to count the elements in a filtered range. Let range be a random access range, and filter the result of filtered(predicate), auto filtered_range = range | filter; count_if( filtered_range, [](const&){ return true; }); // (& omitted in lambda) counts the elements in a filtered range. _If_ this is the best way to count the elements in a filtered range, what about defining Range boost::count(Range&& r); to count all element in the range? It could call size() if available and count_if otherwise. Bests, Gonzalo BG

4 7

[mailing list] Duplicated thread - Best way to proceed
by Gonzalo Brito Gadeschi 19 Jun '13

19 Jun '13

The thread: [boost] [range] Best way to count the elements in a filtered range? I sent an email with an unregistered email adress to the list. As expected, I did not receive a confirmation about the mail being accepted. I resent the mail with my registered email adress. As expected, the new mail was accepted. However, the unaccepted mail started getting replies. - What is the best way to proceed? - Why did the email sent with the unregistered email address get replies? - Shouldn't it have been rejected right away? Bests, Gonzalo BG

1 0

[range] Best way to count the elements in a filtered range?
by Gonzalo BG 19 Jun '13

19 Jun '13

I wonder what is the recommended way to count the elements in a filtered range. Let range be a random access range, and filter the result of filtered(predicate), auto filtered_range = range | filter; count_if( filtered_range, [](const&){ return true; }); // (& omitted in lambda) counts the elements in a filtered range. _If_ this is the best way to count the elements in a filtered range, what about defining Range boost::count(Range&& r); to count all element in the range? It could call size() if available and count_if otherwise. Bests, Gonzalo BG

3 2

Is anybody working on the Boost Windows installer?
by Antony Maria Sakkariaz 18 Jun '13

18 Jun '13

Hi, Good morning. I am new to Boost and this mailing list. When I visited BoostPro computing in order to download the Windows installer, I did not see any installer beyond version 1.51. Since BoostPro donated the installer source code to the community, I am checking to see if anybody is updating the installer for the newer Boost versions. In case nobody is working on this, then I thought I would try to do it. :-) Thanks, Antony

2 1

Re: [boost] [c++11]
by Niall Douglas 18 Jun '13

18 Jun '13

> > I should quickly explain why rvalue ref support is so important to proposed > > Boost.AFIO: it's a 100% batch API and therefore takes in batches of things > > to do and returns out batches of results. That implies lots of passing > > sequences of things around in STL containers, which without rvalue refs are > > not cheap to copy. Therefore while we could get the library working on > > Maybe BOOST_ASIO_MOVE_ARG (in boost/asio/detail/config.hpp) will work > for you. I don't understand how that makes std::vector<> or any other STL container suddenly magically start not copy constructing its contents on C++03 compilers. struct async_io_op has both rvalue and const lvalue copy and assignment constructors. It's left up to the compiler and STL container implementation to decide when and where to use them. I agree we should be using more std::move() to help the compiler where it needs it, but all performance tuning is being left till after the Boost import. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

2 1

Re: [boost] [c++11]
by Niall Douglas 18 Jun '13

18 Jun '13

> 2013/6/14 Sid Sacek <ssacek(a)securewatch24.com>: > <...> > > Sounds like it's not really worth the effort and simply just stick to the old style. > > Stick to the old style. Add #ifndef'ed C++11 specific features if they add > functionality or improve performance much. Boost libraries are tested using > C++11 and C++03 on different compilers and works good in all situations. Speaking of which, I was going to ask this list about the minimum compiler requirements for proposed GSoC Boost.AFIO, so now is as good a time as any. The existing code base being prepared for entry into Boost is pure C++11, or at least as much C++11 as is provided by the Nov 2012 CTP experimental MSVC compiler and therefore easily supported by GCC 4.6 and clang 3.x. The variadic templates used probably can be swapped out easily enough with Boost Preprocessor generators. The very extensive use of C++11 only library features could probably be replaced with Boost equivalents in most cases, though we really do need a fully C++11 functional std::exception_ptr rather than Boost's limited boost::exception_ptr. The thing we probably can't replace without major surgery is rvalue reference usage. It's used very extensively. Moreover, performance without rvalues would truly suck. So here's the question: is C++03 compiler and C++03 TR1 standard library support still an absolute, unnegotiable requirement for a library to become an official part of Boost? Or can we at least require rvalue reference support as a minimum? Or do we add a new category to Boost: some bits of C++11 requiring libraries? We're going to have to do this eventually anyway. Niall

12 20

[multiprecision] Are these types suitable as numeric types for unit tests?
by Daryle Walker 18 Jun '13

18 Jun '13

I'm writing new numeric types, and my unit tests use MPL lists of numeric types. I usually use stuff like int, unsigned, and double, but now I'm adding cpp_int and cpp_dec_float_50. Those types were OK when I was just doing type equalities and sizeof checks. Now I'm doing tests that use objects of those types and I'm getting problems. //==== typedef boost::mpl::list<int, unsigned, cpp_int> test_integer_types; typedef boost::mpl::list<double, cpp_dec_float_50> test_floating_types; //... BOOST_AUTO_TEST_CASE_TEMPLATE( test_complex_component_access1, T, test_integer_types ) { typedef complex_it<T, 0> real_type; typedef complex_it<T, 1> complex_type; real_type a; real_type const & aa = a; complex_type b; complex_type const & bb = b; a[ 0 ] = 6; BOOST_CHECK_EQUAL( a[0], T(6) ); BOOST_CHECK_EQUAL( T(6), aa[0] ); b[ 0 ] = 5; b[ 1 ] = 7; BOOST_CHECK_EQUAL( b[0], T(5) ); BOOST_CHECK_EQUAL( T(5), bb[0] ); BOOST_CHECK_EQUAL( b[1], T(7) ); BOOST_CHECK_EQUAL( T(7), bb[1] ); } //==== I'm getting warnings about integer overflow. The problem is at Line 59 of boost/test/tools/detail/print_helper.hpp. It sets an output stream's precision based on the digits given by std::numeric_limits. //==== BOOST_AUTO_TEST_CASE_TEMPLATE( test_complex_component_access2, T, test_floating_types ) { typedef complex_it<T, 0> real_type; typedef complex_it<T, 1> complex_type; real_type a; real_type const & aa = a; complex_type b; complex_type const & bb = b; a[ 0 ] = 6.0; BOOST_CHECK_CLOSE( a[0], T(6.0), 0.1 ); BOOST_CHECK_CLOSE( T(6.0), aa[0], 0.1 ); b[ 0 ] = 5.5; b[ 1 ] = -7.0; BOOST_CHECK_CLOSE( b[0], T(5.5), 0.1 ); BOOST_CHECK_CLOSE( T(5.5), bb[0], 0.1 ); BOOST_CHECK_CLOSE( b[1], T(-7.0), 0.1 ); BOOST_CHECK_CLOSE( T(-7.0), bb[1], 0.1 ); } //==== This time it's an error, at Line 59 of boost/test/tools/floating_point_comparison.hpp. There no (close enough) matching function for "fpt_abs" from some "boost::multiprecision::detail::expression<..." type. (It was truncated by the display. I don't know how to get a clean print-out of errors from Code::Blocks.) I'm guessing the expression template setup is screwing things up. Daryle W.

6 25

Re: [boost] [c++11]
by Niall Douglas 17 Jun '13

17 Jun '13

> > We can work around the lack of variadic templates, and therefore > > support vanilla VS2012 if peer review demands it. Of course VS2012 > > won't make binaries which can run on Windows XP :( so maybe VS2010 > > support will also be demanded by peer review. If it is, we'll do what is required > to meet VS2010. > JFYI: the VS2012 Update 1 can build binaries which can run on WinXP. You just > need to specify the v110_xp toolset in the project options. Apologies, I had skim read the VS2012 update announcement when it happened where it used the phrase "This new platform toolset points to a repackaged version of the Windows 7 SDK shipped in Visual Studio 2010 instead of the Windows 8 SDK" but I had missed the phrase "but uses the same Visual Studio 2012 compiler". As a result, I thought they had basically packed up the VS2010 build environment for VS2012 and that they therefore were equivalent. Mea culpa. BTW, and purely for information, I found that if you build your VS2012 Nov 2012 CTP app as a DLL, and then write a tiny shim program in VS2010 which loads in that DLL, all appeared to work okay on Windows XP. I didn't test that hugely at the time, but it did work for me to get variadic template capable MSVC binaries running on XP. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

1 0

[New][Multiprecision] Getting errors while writing hypercomplex classes.
by Daryle Walker 17 Jun '13

17 Jun '13

I've banged out (yet another) complex number class at <https://github.com/CTMacUser/Complex>. The current commit has an SHA of "b866cda91ccdb4aa87c199c6d9e7c776fee61bcc." Right now, I'm writing this code on a 32-bit Windows 8 system using Code::Blocks with a packaged MinGW GCC 4.7 by TDM. In many of the incremental changes, I ran into internal compiler errors. I don't know if my code is too unusual or it's the compiler. I'm asking if you guys can check out the code with other compilers (GCC 4.7 besides MinGW/TDM, GCC 4.8, Clang 3.x, non-Windows, etc.) so we can figure out what bug goes where. There are two class templates: - boost::math::complex_it<Number, Rank> - boost::math::complex_rt<Number, Rank> "Number" is a Regular type that supports math operations plus Boolean conversions. "Rank" is the Cayley-Dickson hypercomplex level. Use 0 as a shell for real numbers, 1 for regular complex numbers, 2 for quaternions, 3 for octonions, etc. The "complex_it" class template stores all the components directly in an array with length 1ULL << Rank ("i" is for "iterative"). The "complex_rt" class template stores an array of 2 objects of the previous level ("r" is for "recursive"), except for the partial-specialized base case which stores one component. The two templates support nearly the same interface. - Static interface * using value_type = Number * rank = Rank * static_size = 1ULL << Rank * using barrage_type = complex_?t<Number, Rank - 1> (or self when Rank == 0) - Construction * Complex_type a; // random garbage bits * Complex_type b{}; // zero-fill * Complex_type c{ r }; // real conversion * Complex_type d{ r, i, ... }; // real list * Complex_type e{ Complex_type<ConvertibleNumber, SameOrLowerRank>, ... }; * Complex_type f{ Complex_type<ConvertibleNumber, GreaterRank> }; // explicit * Complex_type g{ Other_complex_type<AnyNumber, AnyRank> }; // explicit * Complex_type h{ Complex_type<AnyNumber, AnyRank> }; // explicit * For [d], the total number components can't exceed static_size. * For [e], the combined number of components from the objects can't exceed static_size. * "ConvertibleNumber" uses implicit conversion, "AnyNumber" static_cast. * Conversions in [g] are both in complex_rt, a constructor and conversion-operator. * For [h], it excludes types in "AnyNumber" that would be covered by [e] and [f]. - Member functions * Boolean conversion operator (explicit) * "real" and "imag," inspector and mutator versions, just like std::complex (Don't use "imag" mutator when Rank == 0!) * "unreal" inspector, like boost::quaternion and octonion; plus a mutator version * Lower- and upper-halves of component list (called barrages) - complex_it uses inspector and mutator, like real/imag/unreal - complex_rt uses by-reference returns, const and mutable * operator [] for direct (by-reference) access to components - External operators * == * != * + (unary) * - (unary) * ~ (new, conjugation) * << (output) - Tuple interface (get, tuple_element, tuple_size) - Object support * begin (non-member, complex_it only) * end (non-member, complex_it only) * swap - Math * conj These spots cause internal-compiler errors: * https://github.com/CTMacUser/Complex/blob/master/include/boost/math/complex_ it.hpp#L753 * https://github.com/CTMacUser/Complex/blob/master/include/boost/math/complex_ rt.hpp#L593 * https://github.com/CTMacUser/Complex/blob/master/include/boost/math/complex_ rt.hpp#L599 use the comments to switch the code back and see if it works on your system. There were also problems using Boost.Multiprecision in the unit tests. I don't know if the problems are in Multiprecison, Test, MPL, or some interaction between them. The spots in "complex_it_test.cpp" and "complex_rt_test.cpp" that use the "test_builtin_types" alias were supposed to use "test_types," but the sample types from Multiprecision had MPL errors. Switch the types and see if they work on your system. Daryle W.

3 3

Re: [boost] [c++11]
by Niall Douglas 17 Jun '13

17 Jun '13

> > Actually it targets three compilers (+clang). I might add that > > Boost.ASIO only officially supports Windows, Linux, Solaris and OS X, > > and only the compilers MSVC7.1 or later and g++ 3.3 or later. Some > > would say that is a fairly narrow set in itself. > > That's not quite what I read here: > > http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/overview/implem > entation.html See for yourself at http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/using.html. I agree that perhaps that list, given the list you linked to, is now out of date. > And the compilers you mentioned as officially supported by ASIO actually cover > pretty much every compiler out there nowdays. > > Comparing that with your requirement of the compiler that has not even been > released, it doesn't look like AFIO portability level will be even remotely close to > that of ASIO. We can work around the lack of variadic templates, and therefore support vanilla VS2012 if peer review demands it. Of course VS2012 won't make binaries which can run on Windows XP :( so maybe VS2010 support will also be demanded by peer review. If it is, we'll do what is required to meet VS2010. > > Given that we knew that VS2012 would get variadic templates later this > > year (which it will in the form of VS2013), we decided to just go > > ahead with what > > C++11 features will be available to > 90% of C++ users by the end of 2013. > > That surely should satisfy the portability requirement, if not, then > > we'll work backwards until we reach > 95% of C++ users or > 99% if > > Boost peer review really, really wants it. > > I think your estimate of "> 90% of C++ users by the end of 2013" is much too > optimistic. People in corporate sector are very reluctant to update their > toolsets, so expect people trying to use your new library with 3-5 year old > compilers. I used the qualifier "available to" with purpose: I agree that a compiler may be available to > 90% of C++ users but for whatever reason those users do not avail of that compiler. FYI for my other open source I still get regular bug submissions for MSVC6 breakage due to my use of C++98 features, so I'm well aware what corporate is like. That said, this is a new greenfield library, and therefore no legacy compiler technology is inconvenienced by its compiler requirements. I might add that as C++ Now 2013 showed, there are quite a few new Boost libraries on their way which are C++11 only and will only ever be C++11 only: I saw presentations on new C++11 only versions of Boost.Proto and Boost.Spirit for example. > I know, C++11 has many fancy features and all, and I'm all for its adoption too. > But Boost also serves practical purpose, and if people can't use your library then > that just limits its usefulness. So unless you trying to make some academic work > here, the library should be more portable. If a corporate end user really, really wants the library working on their compiler toolset, they are always free to sponsor a port to that toolset. It's all open source. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

4 5

Re: [boost] [c++11]
by Niall Douglas 17 Jun '13

17 Jun '13

> > The existing code base being prepared for entry into Boost is pure > > C++11, or at least as much C++11 as is provided by the Nov 2012 CTP > > experimental MSVC compiler and therefore easily supported by GCC 4.6 and > clang 3.x. > > I hope that you do realize that the Nov12 CTP does not come with a go-live > license, nor is recommended for any human consumption. Meh. First preview of VS2013 is only a month away. Nov 2012 CTP is usefully broken in ways easy to work around (parser bugs) rather than broken in unhelpful ways (unreliable code generation). It fills a useful slot until VS2013 arrives later this year. > It seems quite odd to me to spend significant GSoC resources on making a library > that targets only two compilers, and assumedly a rather narrow set of OSes. Actually it targets three compilers (+clang). I might add that Boost.ASIO only officially supports Windows, Linux, Solaris and OS X, and only the compilers MSVC7.1 or later and g++ 3.3 or later. Some would say that is a fairly narrow set in itself. We'll be matching Boost.ASIO's official platform support, but adding official support for FreeBSD 10 with clang and libcxx. In truth though it ought to work on any OS providing a POSIX file i/o API with preadv() and pwritev() which is the majority (including Windows via its MSVCRT incidentally). You may find https://github.com/BoostGSoC/boost.afio/wiki/Status-of-proposed-Boost.AFIO of interest. There it tells you how to get started with the proposed library right now. > Was this C++11-only requirement part of the original project plan, and why > didn't anyone object to it then? Yes, it was an original plan requirement. Having full fat C++11 (esp. the C++11 standard library) to hand made the code and design *very* considerably simpler and *much* easier to read (and therefore maintain) - in fact, there is only 670 lines of active code. Judging from the presentations at C++ Now 2013, this simplification experience of pure C++11 is hardly unique: many presenters commented on just how much their pure C++11 new versions of Boost libraries were cleaner, simpler, faster to compile and faster performance, and hugely more maintainable. Given that we knew that VS2012 would get variadic templates later this year (which it will in the form of VS2013), we decided to just go ahead with what C++11 features will be available to > 90% of C++ users by the end of 2013. That surely should satisfy the portability requirement, if not, then we'll work backwards until we reach > 95% of C++ users or > 99% if Boost peer review really, really wants it. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

8 11

Re: [boost] [c++11]
by Niall Douglas 17 Jun '13

17 Jun '13

> > On 14 June 2013 17:21, Niall Douglas <ndouglas(a)blackberry.com> wrote: > >> So here's the question: is C++03 compiler and C++03 TR1 standard > >> library support still an absolute, unnegotiable requirement for a > >> library to become an official part of Boost? > > > > No. > > > > http://www.boost.org/development/requirements.html#Portability > > I suspect this may come down to the review ultimately: I can imagine that any > library that was C++11 only would have a hard time getting through review "as > is", *unless* there's a really compelling reason for it to be that way (and for > some libraries that may well be the case). However, I can also imagine a library > being developed as a C++11 only lib and only ported back to C++03 and/or less > capable compilers once it's stable (or vice versa). Thanks John: you're the only one who actually answered my question. I should quickly explain why rvalue ref support is so important to proposed Boost.AFIO: it's a 100% batch API and therefore takes in batches of things to do and returns out batches of results. That implies lots of passing sequences of things around in STL containers, which without rvalue refs are not cheap to copy. Therefore while we could get the library working on C++03, I'd imagine max IOPS would be awful as all those container copy constructors fire several times per API invocation. Right now max IOPS is about 80,000 which is awful, and that's *with* C++11. I'd expect that to be an order of magnitude slower without move construction. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

2 1

Re: [boost] [c++11]
by Niall Douglas 17 Jun '13

17 Jun '13

> I'll be blunt here: taking off my corporate job hat and putting back on my old > consulting hat, I'd say it simply: you'll get ~ 90% of the C++ user base support > from my open source code for free. If you want more for your niche technology > Y, my rates start at $200/hour. I misphrased myself here: nothing in this statement should be taken as meaning that I am available for consulting work at any hourly rate since I began employment at BlackBerry, and my consulting firm is indeed closed for new business with no prospect of reopening in the immediate future. I meant my original statement in the sense that wanting compatibility with some technology Y is something which can't be expected for free in open source. That includes legacy compilers. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

1 0