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

Re: [Boost-users] [boost] [variant] Warning: variadic templates in boost::variant
by Igor R 09 Dec '13

09 Dec '13

> Development version of Boost.Variant library now uses C++11 variadic > templates when possible. > This leads to more compact binaries, more readable compiler error messages > and faster compilation times. Will it support MSVC12 (i.e. VS2013)? In particular, won't it be affected by the following bug: http://tinyurl.com/o2psdj5 ?

2 1

[boost] [variant] Warning: variadic templates in boost::variant
by Antony Polukhin 09 Dec '13

09 Dec '13

Development version of Boost.Variant library now uses C++11 variadic templates when possible. This leads to more compact binaries, more readable compiler error messages and faster compilation times. However this: * breaks ABI (now variant is declared as `template <typename T0, typename... TN> class variant`) * breaks user code that was explicitly using BOOST_VARIANT_LIMIT_TYPES Code that was using BOOST_VARIANT_ENUM_PARAMS and BOOST_VARIANT_ENUM_SHIFTED_PARAMS macro *must* work correctly without any modifications. To disable variadic templates usage in variant define BOOST_VARIANT_DO_NOT_USE_VARIADIC_TEMPLATES. When all the tests will pass successfully changes will be merged to master branch, so there is a high chance that variadic templates will be supported by Boost 1.56. In case of appearance of hard to fix variadic templates errors in Boost libraries dependent on Boost.Variant - report them in this letter and I'll help in resolving issues. -- Best regards, Antony Polukhin

1 0

C++Now 2014: Call for Submissions, Updated deadlines
by Hartmut Kaiser 09 Dec '13

09 Dec '13

Updated submission dates! Please see below! ============================================== C++ Now Conference 2014 Aspen CO, USA, May 12-17, 2014, www.cppnow.org ============================================== For the full announcement online, please see here: http://cppnow.org/2013/10/21/2014-call-for-submissions/ Call for Submissions -------------------- We invite you to submit session proposals to the 3rd annual C++Now Conference (Aspen CO, USA, May 12-17, 2014). Building upon the resounding success of C++Now 2013 and five years of BoostCon, C++Now 2014 will present leading speakers from the whole C++ community. The C++Now Conference is dedicated to discussion and education about C++, an open and free language and standard. Our Conference will focus on discussion and education about open source software usage and developments in the C++ developer and user community. To reflect the breadth of the C++ and Boost communities, the conference includes sessions aimed at three constituencies: C++ and Boost end-users, hard-core Boost library and tool developers, and researchers pushing the boundaries of computation. The program fosters interaction and engagement within and across those groups, with an emphasis on hands-on, participatory sessions. As a multi-paradigm language, C++ is a melting pot where the most compelling ideas from other programming communities are blended in powerful ways. Historically, some of the most popular sessions at C++Now have highlighted these concepts, from DSLs to functional programming to transactional memory and more. Bring your C#, Python, Ruby or Haskell influences to bear in an environment that will broaden their exposure. At C++Now 2014 we would like to focus on the now established C++11 standard and the new, upcoming C++14 and how those standards are and will shape C++'s future. However, by no means is this intended to restrict the topics of proposals we hope to see. Any other topic related to C++ as outlined below is perfectly fine for submission. Important dates --------------- New proposal submissions due: December 22th, 2013. Proposals decisions sent (tentative program available): February 15th, 2014. Fully scheduled program available: February 28th, 2014. Best Presentation Awards ------------------------ We know how much effort it takes to prepare talks for our conference. For this reason we will award the best The awards will be given based on the audience's voting. Each award will include the author's name listed on the cover of the C++Now website for that year and a plaque containing all the C++Now conference information. Session topics -------------- Topics of interest include, but are not restricted to, the following: * C++11/14 and how it changes life for users and library writers * General tutorial sessions on C++11/14, the C++11/14 Standards library, and one or more Boost libraries * Parallelism in the new C++11/14 standard * Parallel, distributed and GPGPU topics relating to C++ * In-depth sessions on using specific Boost libraries * Case studies on using Boost * Experts panels * Advanced sessions on implementation techniques used within Boost libraries * Development workshops to extend or enhance existing Boost libraries * Workshops on design process * Infrastructure workshops such as Build tools, Website, Testing * Concepts and Generic Programming * Hardware and infrastructure presentations focused on how libraries can make better use of the technology * Software development tools and their application to C++ and or Boost * Other topics likely to be of great interest to C++ users and developers Interactive and collaborative sessions are encouraged, as this is the style of learning and participation that has proven most successful at such events. Sessions can be tutorial based, with an emphasis on interaction and participant involvement, or workshop based, whether hands-on programming or paper-based, discussion-driven collaborative work. Session formats --------------- Presentations Presentations focus on a practitioner's ideas and experience with anything relevant to C++11 or C++14, Boost and users. Panels Panels feature three or four people presenting their ideas and experiences relating to C++11 or C++14 and Boost's relevant, controversial, emerging, or unresolved issues. Panels may be conducted in several ways, such as comparative, analytic, or historic. Tutorials Tutorials are sessions at which instructors teach conference participants specific skills relevant to C++11 or C++14 and Boost. Workshops Workshops provide an active arena for advancements in Boost-relevant topics. Workshops provide the opportunity for experienced practitioners to develop new ideas about a topic of common interest and experience. Author's Corner Presentations These were introduced at BoostCon 2008, and were a great success. They are short (30 minute) sessions, focusing on tips on usage and design. In addition, we're looking to uncover the hidden design gems in Boost libraries. Tool Vendors Presentations We actively encourage tool vendors and ISP's to submit proposals for a special Tool Vendors Session Track aimed at products related to Boost and C++ (compilers, libraries, tools, etc.). Other formats may also be of interest. Don't hold back a proposal just because it doesn't fit into a pigeonhole. Submitting a proposal --------------------- Standard sessions are 90 minutes. You may submit a proposal for fractions or multiples of 90-minutes. Fractional proposals will be grouped into 90 minute sessions covering related topics. Longer sessions, such as tutorials and classes, will be assigned three hour (i.e. half day), or six hour (i.e. full day) time slots. Please include: * The working title. * Type of session: presentation, panel, tutorial, workshop, authors corner, vendor track, other. * A paragraph or two describing the topic covered, suitable for the conference web site. * Proposed length: 10-20 minute short talks, 45 minutes, 90 minutes, half day, full day. * Alternate lengths, if you are willing to make adjustments: 10-20 minute short-talks, 45 minutes, 90 minutes, half-day, full day. * Audience: users, developers, both. * Level: basic, intermediate, advanced. * A biography, suitable for the conference web site. * A photo of about 150 x 150 * Your public contact information (twitter handle, blog, website, google plus, etc.) * Your contact information (will not be made public). Submission details ------------------ All submissions should be made through the EasyChair conference management system: http://www.easychair.org/conferences/?conf=cppnow2014. If you have not already registered at EasyChair, you will need to do so in order to submit your proposal. All submissions will go through a peer review process. Authors are invited (but are not required) to submit PDF versions of full papers of up to 10 pages in ACM conference proceedings format (see http://www.acm.org/sigs/publications/proceedings-templates) The full papers are not required unless you want them published in the proceedings. All accepted proposals will be made available in the Association for Computing Machinery (ACM) Digital Library (approval pending). Best papers, after further reviews, will be considered to be book chapters or journal articles in a renowned journal. The session materials go on the C++ Now website and will be available to attendees. For general information on the C++ Now 2014 paper submission or the scope of technical papers solicited; please refer to the conference website at www.cppnow.org. For any other questions about the submission process or paper format, please contact the Program Committee at cppnow2014(a)easychair.com. If you have any technical problems with EasyChair, please contact EasyChair for help. Note: Presenters must agree to grant a non-exclusive perpetual license to publish submitted materials, either electronically or in print, in any media related to C++ Now. Hartmut Kaiser, email: hartmut.kaiser(a)gmail.com (Program Committee Chair) Joel Falcou, email: joel.falcou(a)lri.fr (Program Committee Co-Chair) Jon Kalb, , email: jon(a)kalbweb.com (Conference Chair) Dave Abrahams, dave(a)boostpro.com (Conference Chair) On behalf of the conference organizers

1 0

Thread synchronization
by Gonzalo Garramuno 08 Dec '13

08 Dec '13

I have an application (a video player), that uses three threads to play videos (one thread handles decoding, another video display, and another audio). These threads have a thread barrier to wait until all 3 threads finish. This works fine. Now, my video player supports playing back two movies at the same time (to have one as a background and one as a foreground). Currently this is done with the same code for both. My problem is that there's no sync between the two movies and I am puzzled on how to achieve synchronism. I am unsure whether a thread barrier can be waited twice by two threads or whether I should have a single barrier that waits on the 6 threads ( 2 decode, 2 video, 2 audio ). If someone has any insight, it would be appreciated.

2 3

boost::iostreams::copy - sink - ENOSPC (No space left on device) error handling
by Dino Korah 07 Dec '13

07 Dec '13

Platform: GCC on Linux; boost 1.55. In the code fragment below, is there a way to handle ENOSPC? #include <fstream> #include <iostream> #include <boost/iostreams/filtering_streambuf.hpp> #include <boost/iostreams/copy.hpp> #include <boost/iostreams/filter/bzip2.hpp> // open input file stream of the bzip2 file std::ifstream ifs("file.bz2"); // open output stream to the "full" device // full device is a "utility-device" to check how applications handle ENOSPC // more details in "man full" std::ofstream ofs("/dev/full"); // Setup the iostreams filter boost::iostreams::filtering_streambuf<boost::iostreams::output> filters; filters.push(boost::iostreams::bzip2_decompressor()); filters.push(ofs); // "run" the filter boost::iostreams::copy(ifs, filters); If I do strace of the compiled binary, the code seem to infinitely call writev() with the same data and returns ENOSPC error. writev(4, [{NULL, 0}, {"DATA DATA "..., 4096}], 2) = -1 ENOSPC (No space left on device) How can this error be handled or made thrown as an error from boost::iostreams::copy() Is it possible to set appropriate exceptions() on the ofstream object? I tried ofs.exceptions(std::ios::badbit | std::ios::failbit) but it didn't make any difference.

2 1

one memory leak
by XIN LI 06 Dec '13

06 Dec '13

Hi there, I use boost version 1.49.0. I meet a memory leak for below sentences: boost::filesystem::path tmp = input.stem(); string strDir = tmp.normalize().string(); Valgrind report memory leak as below: ==18299== 56 bytes in 1 blocks are still reachable in loss record 26 of 61 ==18299== at 0x16DF68B8: malloc (vg_replace_malloc.c:270) ==18299== by 0x3F64FEC: operator new(unsigned long) (in /home/lixin/work/prj/hotfix/13q2_ehf1/src/prosim/dist/Debug_64/GNU-Linux-x86/nanospice) ==18299== by 0x3F5B8F1: stlp_std::priv::__acquire_category(char const*&, char*, _Locale_name_hint*, char const* (*)(char const*, char*, _Locale_name_hint*, int*), void* (*)(char const*, _Locale_name_hint*, int*), char const* (*)(char*), stlp_std::hash_map<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> >, stlp_std::pair<void*, unsigned long>, stlp_std::hash<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > >, stlp_std::equal_to<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > >, stlp_std::allocator<stlp_std::pair<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > const, stlp_std::pair<void*, unsigned long> > > >**, int*) (in /home/lixin/work/prj/hotfix/13q2_ehf1/src/prosim/dist/Debug_64/GNU-Linux-x86/nanospice) ==18299== by 0x3F5BD04: stlp_std::priv::__acquire_ctype(char const*&, char*, _Locale_name_hint*, int*) (in /home/lixin/work/prj/hotfix/13q2_ehf1/src/prosim/dist/Debug_64/GNU-Linux-x86/nanospice) ==18299== by 0x3F3F502: stlp_std::_Locale_impl::insert_ctype_facets(char const*&, char*, _Locale_name_hint*) (in /home/lixin/work/prj/hotfix/13q2_ehf1/src/prosim/dist/Debug_64/GNU-Linux-x86/nanospice) ==18299== by 0x3F3DC3C: stlp_std::locale::locale(char const*) (in /home/lixin/work/prj/hotfix/13q2_ehf1/src/prosim/dist/Debug_64/GNU-Linux-x86/nanospice) ==18299== by 0x458FFFE: boost::filesystem3::path::wchar_t_codecvt_facet() (in /home/lixin/work/prj/hotfix/13q2_ehf1/src/prosim/dist/Debug_64/GNU-Linux-x86/nanospice) ==18299== by 0x4591806: boost::filesystem3::path::begin() const (in /home/lixin/work/prj/hotfix/13q2_ehf1/src/prosim/dist/Debug_64/GNU-Linux-x86/nanospice) ==18299== by 0x4592844: boost::filesystem3::path::m_normalize() (in /home/lixin/work/prj/hotfix/13q2_ehf1/src/prosim/dist/Debug_64/GNU-Linux-x86/nanospice) ==18299== by 0x21019EB: boost::filesystem3::path::normalize() (path.hpp:430) Because my program need run thousands of time and very sensitive for the memory leak. Could anyone help to suggest one way to avoid such memory leak? Thanks a lot! Best wishes, Andy Li

2 1

[log] Sink format is ignored
by Igor R 06 Dec '13

06 Dec '13

Hello, I'm setting up a sink like this: boost::shared_ptr<sinks::text_file_backend> backend = boost::make_shared<sinks::text_file_backend> ( keywords::file_name = fileName, keywords::rotation_size = maxSize, keywords::format = "[%TimeStamp%][%LineID%]: %Message%", keywords::auto_flush = true ); typedef sinks::synchronous_sink<sinks::text_file_backend> file_sink; boost::shared_ptr<file_sink> sink = boost::make_shared<file_sink>(backend); sink->set_filter(!expr::has_attr(serv_attr)); logging::core::get()->add_sink(sink); logging::add_common_attributes(); However, it seems that keywords::format parameter is just ignored. What am I doing wrong?

3 3

Re: [Boost-users] [graph] Compilation problem using depth_first_visit with a listS as a VertexListS
by Simon Bozonnet 06 Dec '13

06 Dec '13

Thanks Alex, I finally understood that using std::vec and std::list is different in the way that we need to specify an index for the edges/nodes while using such a routine like depth_first_visit. Thanks for your help! Simon > From that I isolated the following code which compiles without any problem: > > typedef adjacency_list < vecS, vecS, bidirectionalS, GraphvizVertexProperty,GraphvizEdgeProperty, GraphvizGraphProperty > Graph; > ... > depth_first_visit(_graph2, loop_head, default_dfs_visitor(), make_iterator_property_map(reachable_from_head.begin(),get(vertex_index, _graph2), c)); > So this works fine! > Then, I would like to change the type of graph, so more precisely, to use a std::list (or listS) instead of a std..vector (vecS) for the VertexListS > So the first line declaration becomes: > typedef adjacency_list < vecS, listS, bidirectionalS,GraphvizVertexProperty,GraphvizEdgeProperty, GraphvizGraphProperty > Graph; > //only the 2nd argument changes > But then when I compile the code, I get 1 error during the compilation as described hereafter. "If the VertexList of the graph is vecS, then the graph has a builtin vertex indices accessed via the property map for the vertex_index_t property." (http://www.boost.org/doc/libs/1_55_0/libs/graph/doc/adjacency_list.html <http://www.boost.org/doc/libs/1_55_0/libs/graph/doc/adjacency_list.html>) So when you use listS instead you have to supply your own vertex index map.

1 0

Fwd: support for bjam projects in IDE
by Witold E Wolski 06 Dec '13

06 Dec '13

Hi, I will have to work on bjam based project (rather big). I normally use QT Creator for programming and work with cmake based project. I could't find any hint how to set up an bjam project to work with QT neither information about any IDE which supports bjam. Do boost developer use vim and debug using gdb only? Actually the other guys on the project wrote some python scripts which parse bjam output to generated vcproj files :-@ I would be happy to hear from someone who are happy using bjam with qtcreator or any other IDE for larger projects and how to set this up. All my searches so far regarding bjam return almost exclusively FUD (http://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt) but looking at the Jamroot.jam file of the project (more than 1000 lines) I am inclinded to believe it. ;-( -- Witold Eryk Wolski -- Witold Eryk Wolski

2 2

Await the result of several futures to chain another task
by Kaspar Fischer 06 Dec '13

06 Dec '13

Hi, If I have two futures f1 and f2, can I compose them to a future that completes with the result of f1 and f2 when both f1 and f2 have finished? I'd like to have a future so that I can use the then()<http://www.boost.org/doc/libs/1_55_0/doc/html/thread/synchronization.html#t…>method to run another transformation. I see method wait_for_all()<http://www.boost.org/doc/libs/1_55_0/doc/html/thread/synchronization.html#t…>but this method blocks. Best, Kaspar

2 2

[serialization] How to deserialize only a part of an XML archive?
by luca 05 Dec '13

05 Dec '13

This is my scenario: I've got a shared library in which these classes are defined: class base { ... serialize() ... } class parent: public base { ... serialize(...) {...serialize base. and itselft too!} ... } the shared lib is used by a computational application that re-implements class parent in an extended version - this because the app is a Qt application that does visualization etc...: class grandParent: public parent { //it also defines some specific serialization capabilities: serialize (...) {serialize parent and also itself} } Now if I serialize into an XML archive an instance of grandParent I am clarly able to deserialize it in a grandParent object, but what about to deserialize it as a parent object? if I serialize from grandParent I would get something like: <grandParent> <parent> <base> </base> </parent> </grandParent> I would need to deserialize only the parent part: <parent> <base> </base> </parent> In practice I would like to be able to deserialize an XML archive to a base class instead that to the derived. But in this case the derived class is not accessible by boost (that thus complains about it) In this way I would get the better inter-operability between my application and the underlaying lib, that must be able to run without the app itself... Many thanks! Luca

1 0

Re: [Boost-users] [graph] Compilation problem using depth_first_visit with a listS as a VertexListS
by alex 05 Dec '13

05 Dec '13

> From that I isolated the following code which compiles without any problem: > > typedef adjacency_list < vecS, vecS, bidirectionalS,GraphvizVertexProperty,GraphvizEdgeProperty, GraphvizGraphProperty > Graph; > ... > depth_first_visit(_graph2, loop_head, default_dfs_visitor(), make_iterator_property_map(reachable_from_head.begin(),get(vertex_index, _graph2), c)); > So this works fine! > Then, I would like to change the type of graph, so more precisely, to use a std::list (or listS) instead of a std..vector (vecS) for the VertexListS > So the first line declaration becomes: > typedef adjacency_list < vecS, listS, bidirectionalS,GraphvizVertexProperty,GraphvizEdgeProperty, GraphvizGraphProperty > Graph; > //only the 2nd argument changes > But then when I compile the code, I get 1 error during the compilation as described hereafter. "If the VertexList of the graph is vecS, then the graph has a builtin vertex indices accessed via the property map for the vertex_index_t property." (http://www.boost.org/doc/libs/1_55_0/libs/graph/doc/adjacency_list.html) So when you use listS instead you have to supply your own vertex index map.

1 0

[log] ThreadID attribute is empty
by Igor R 05 Dec '13

05 Dec '13

Hello, I'm formatting a sink like this: sink->set_formatter ( expr::stream << expr::attr<boost::posix_time::ptime>("TimeStamp") << " T:" << expr::attr<boost::thread::id>("ThreadID") << ":" << expr::smessage ); logging::add_common_attributes(); For some reason ThreadID is empty. I tried to register the attribute explicitly: logging::core::get()->add_global_attribute("ThreadID", logging::attributes::current_thread_id()); but it doesn't help. The program is mutithreaded and linked with mt static libs. Thanks.

1 0

Having trouble compiling interval_map
by Daniel Rubi 05 Dec '13

05 Dec '13

Hi, I'm trying to implement an interval map where the keys are close_interval<long> an the values are set<string>. I modified the party example according to my needs, and came up with this short code: #include <boost/icl/interval.hpp> #include <boost/icl/interval_map.hpp> #include <boost/compressed_pair.hpp> using namespace std; using namespace boost::icl; typedef std::set<string> ids; int main(int argc, char* argv[]) { ids ids1; ids1.insert("T1"); ids ids2; ids2.insert("T2"); interval_map<closed_interval<long>, ids> mymap; closed_interval<long> i1 = closed_interval<long>(2, 7); closed_interval<long> i2 = closed_interval<long>(3, 8); mymap.insert(std::pair<closed_interval<long>, ids>(i1,ids1)); mymap.insert(std::pair<closed_interval<long>, ids>(i2,ids2)); return 0; } However, I get this compilation error: call of overloaded ‘insert(std::pair<boost::icl::closed_interval<long int>, std::set<std::basic_string<char> > >)’ is ambiguous mymap.insert(std::pair<closed_interval<long>, ids>(i2,ids2)); This is after getting compiation errors trying ti use: mymap += make_pair(i1,ids1); Any idea what's wrong?

1 0

[Any] inconsistent return types of any_cast overloads
by Arne Vogel 04 Dec '13

04 Dec '13

Hello Boost Users, Code like the following used to work with Boost 1.53 on x86-64 Linux using GCC 4.7 and -std=c++11: boost::any makeVec() { return std::vector<int>{ 1, 2, 3 }; } void foo() { const auto& vec = boost::any_cast<std::vector<int>>(makeVec()); for ( auto value : vec ) { // ... } } The same code is likely to cause a segmentation violation using Boost 1.55. According to the online documentation *1, any_cast has two overloads accepting reference arguments: template<typename ValueType> ValueType any_cast(any&); template<typename ValueType> ValueType any_cast(const any&); If these were indeed the only overloads accepting reference arguments, there is no reason why the example code shouldn't work. ValueType any_cast(const any&) should be the preferred overload and it returns a vector<int> temporary whose lifetime is then extended to the end of the block by being bound to a local const reference, as required by the C++ standard. However, in any.hpp, I discovered the following overload, which is only declared if the macro BOOST_NO_CXX11_RVALUE_REFERENCES is not set. I suppose this overload was added since 1.53, or that, previously, it was by default omitted. template<typename ValueType> ValueType&& any_cast(any&&); This has higher precedence binding to the temporary returned from makeVec, and returns an rvalue reference to the vector<int> contained in said temporary, which is then implicitly converted to a const lvalue reference as by the usual language rules. Since the lifetime of the temporary returned by makeVec is NOT extended - this only works for temporaries directly bound to a local const reference, whereas the result of makeVec is "hidden" inside the call to any_cast - the temporary is destroyed before the start of the for loop, which renders vec invalid and the code a denizen of undefined behavior land. So much for the analysis, now for my actual question. :-) Why does the new overload return by reference when the old ones return by value? The rationale for the old overloads was, I believe, "you should have to ask for a reference if you want one", which makes sense given precisely that using references tends to be more error prone if temporaries are involved. So this would be the very reason why Any does not declare: template<typename ValueType> const ValueType& any_cast(const any&); even though it could be implemented as easily as the actual overload. If I really wanted to get an const reference out of any_cast, I could write something like boost::any_cast<const ValueType&>(var); I can't think of a reason to be inconsistent in this regard and return a reference if a temporary is passed to any_cast, instead of requiring a user who really wants any_cast to return an rvalue reference to write any_cast<ValueType&&>(...). That the overload breaks existing code and (due to being undocumented and not checked at compile time *2), silently so, whereas using ValueType any_cast(any&&) would at least fail to do any harm, is, in my opinion, another reason to be sceptical of the current solution. Furthermore, there is a usability reason for preferring ValueType(any &&): If ValueType &&(any &&) is declared and I do NOT want a reference, I need to write more verbose and inelegant code than in the opposite case: // Name the temporary const auto &vecAny = makeVec(); // Now, ValueType&& any_cast(any&&) is eliminated from candidate set (no conversion from an lvalue to an rvalue reference) const auto& vec = boost::any_cast<std::vector<int>>(vecAny); Note that the const is accidental here, using a mutable lvalue would work as well. Looking forward to your opinions, Arne Vogel *1) http://www.boost.org/doc/libs/1_55_0/doc/html/boost/any_cast_idp25247624.ht… *2) A compiler may issue a warning. However, I found that GCC 4.8.1 does not warn, even with -Wall and the definition of any_cast being known at the point of use.

5 6

boost::regex Character set including braces
by Tobias 04 Dec '13

04 Dec '13

Dear boost-users, in the post http://stackoverflow.com/questions/20351369/regular-expression-cant-find-seq uence-of-numbers I discovered that if one uses an closing bracket as the first character of a character class the character class includes this bracket. This works with the standard setting of boost::regex (i.e., perl-regular expressions) but it is not documented in the manual page http://www.boost.org/doc/libs/1_55_0/libs/regex/doc/html/boost_regex/syntax/ perl_syntax.html#boost_regex.syntax.perl_syntax.character_sets Is this an undocumented feature, a bug or did I misinterpret something in the manual? The version information in version.hpp is: #define BOOST_LIB_VERSION "1_53" Info: I tried this specification of the bracket in the character set because I am used to it from emacs regular expressions. In the remainder there follows a program for reproduction of the phenomenon: #include <string> #include <boost/regex.hpp> #include <iostream> using namespace std; int main() { std::cout << "main()\n"; string s = "98[2]00"; string exp = "^[][0-9]*$"; const boost::regex e(exp); bool isSequence = boost::regex_match(s,e); //isSequence is boolean and should be equal to 1 cout << isSequence << endl; return 0; } /** Local Variables: compile-command: "g++ -g test.cc -o test.exe -lboost_regex-mt; ./test.exe" End: */ Best regards / Mit freundlichen Grüßen Tobias Zawada Engineering / Software Development ______________________________ ITI Events We say Thank you! for an outstanding ITI Symposium 2013! Make sure you save the date for next year: November 3-5, 2014 www.itisim.com ITI GmbH Schweriner Straße 1 01067 Dresden Germany T +49 (351) 26050 147 F +49 (351) 260 50 155 mailto:Zawada@itisim.com Managing Director/Geschäftsführer Jens O. Schindler · Dr. Andreas Uhlig Commercial Register/Handelsregister Amtsgericht Dresden · HRB 2331 USt.-IdNr.: DE140297717 Diese E-Mail ist streng vertraulich und nur für den Empfänger bestimmt. Sie kann Informationen enthalten, die rechtliche, geschäftliche oder andere Vergünstigungen bedeuten. Sollten Sie nicht der ausdrückliche Empfänger sein, dürfen Sie diese Informationen nicht benutzen, veröffentlichen oder vervielfältigen. The information in this e-mail is strictly confidential, is intended solely for the addressee, and may be privileged. If you are not the intended addressee you must not disclose, print or take action based upon this transmission and should delete it from your system.

2 1

[Filesystem] [Locale] Unicode filenames doc example error
by Egor Tensin 04 Dec '13

04 Dec '13

Why doesn't this simple code from the Boost.Locale docs work? #include <boost/filesystem.hpp> #include <boost/filesystem/fstream.hpp> #include <boost/locale.hpp> #include <exception> #include <iostream> int main() { try { std::locale::global(boost::locale::generator().generate("")); boost::filesystem::path::imbue(std::locale()); boost::filesystem::ofstream hello("привет.txt"); } catch (const std::exception& e) { std::cerr << e.what() << std::endl; } return 0; } Compiled with >cl /EHsc /D _UNICODE /D UNICODE b.cpp /I%BOOST_ROOT% /MD /link /LIBPATH:%BOOST_ROOT%\stage\lib it gives me >b.exe boost::filesystem::path codecvt to wstring: error Could someone please explain what's the problem there and how do I handle Unicode file names on Windows using Boost.Filesystem & Boost.Locale? I'm using Boost 1.55.0 & compiling with MS Visual C++ 2010 compiler v.16.00.30319.01.

1 0

[log] connecting a logger to a specific sink
by Igor R 04 Dec '13

04 Dec '13

Hello, I'm integrating Boost.Log to my project, and have a couple of questions. First of all, I'd like each instance of some class to write its log to a separate rotating file. I understand how to setup such a sink, but can't find a way to connect a particular source (logger) to the sink. Is it possible? Besides, when setting up the file, I configure it with: keywords::format = "[%TimeStamp%]: %Message%" but %TimeStamp% doesn't seem to get recognized, so I get empty [ ] in the file. Do I miss some header file? Thanks.

2 4

Print boost graph with custom vertex label
by Saha, Shambwaditya 04 Dec '13

04 Dec '13

Hi All, I want to print a Boost Graph having custom(string) vertex labels instead of the default vertex numbering label 0,1,2... I have initialized the graph as : typedef adjacency_list <vecS, vecS, directedS, property<vertex_name_t,string>> Graph; Graph g; set<string> names; map<string,Graph::vertex_descriptor> vertex ; for(auto it = names.begin() ; it != names.end(); ++it ) vertex[*it] = add_vertex(*it,g) ; Now how should I print this graph such that I get edges of the form abc -> xyz; instead of 1->2; Thanks and Regards, Shambwaditya

1 0

[phoenix][spirit] catch_all issues in V3
by Igor R 03 Dec '13

03 Dec '13

Hello, The following code doesn't compile (MSVC10, Boost 1.55). If I modify "catch_all" line like this: query = id[phx::try_[qi::_val = phx::bind(&string2test, qi::_1)].catch_all [ qi::_pass = false ], qi::_val = qi::_val ]; ...it compiles, but doesn't seem to invoke the semantic action in runtime. It there a workaround that would both compile and work? Thanks! #define BOOST_SPIRIT_USE_PHOENIX_V3 #include <string> #include <boost/spirit/include/qi.hpp> #include <boost/spirit/include/phoenix_core.hpp> #include <boost/spirit/include/phoenix_operator.hpp> #include <boost/phoenix/bind/bind_function.hpp> #include <boost/phoenix/statement/try_catch.hpp> namespace qi = boost::spirit::qi; namespace phx = boost::phoenix; struct test { }; test string2test(const std::string &str) { if (str == "throw") throw "exception!"; return test(); } template <typename Iterator = std::string::const_iterator> struct test_parser : qi::grammar<Iterator, test(), qi::blank_type> { test_parser() : test_parser::base_type(query) { query = id[phx::try_[qi::_val = phx::bind(&string2test, qi::_1)].catch_all [ qi::_pass = false ] ]; id = qi::lexeme[*qi::char_("a-zA-Z_0-9")]; } qi::rule<Iterator, test(), qi::blank_type> query; qi::rule<Iterator, std::string(), qi::blank_type> id; }; int main() { const std::string input = "qwerty"; test_parser<> p; test output; bool ok = phrase_parse(input.begin(), input.end(), p, qi::blank, output); } // 1> boost\boost\proto\traits.hpp(297): error C2338: 0 == Expr::proto_arity_c 1> boost\boost\mpl\eval_if.hpp(63) : see reference to class template instantiation 'boost::proto::result_of::value<Expr>' being compiled 1> with 1> [ 1> Expr=boost::phoenix::try_catch_actor<boost::proto::exprns_::basic_expr<boost::phoenix::tag::try_catch,boost::proto::argsns_::list2<boost::phoenix::try_catch_actor<boost::proto::exprns_::basic_expr<boost::phoenix::tag::try_catch,boost::proto::argsns_::list1<boost::phoenix::actor<boost::proto::exprns_::expr<boost::proto::tagns_::tag::assign,boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::spirit::attribute<0>>,0>,boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval,boost::proto::argsns_::list2<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::phoenix::detail::function_ptr<1,test,test (__cdecl *)(const std::string &)>>,0>,boost::phoenix::actor<boost::spirit::argument<0>>>,2>>>,2>>>,1>>,boost::proto::exprns_::basic_expr<boost::phoenix::tag::catch_all,boost::proto::argsns_::list1<boost::phoenix::actor<boost::proto::exprns_::expr<boost::proto::tagns_::tag::assign,boost::proto::argsns_::list2<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<boost::phoenix::argument<3>>,0>,boost::phoenix::actor<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal,boost::proto::argsns_::term<bool>,0>>>,2>>>,1>>,2>> 1> ]

2 3

[graph] Compilation problem using depth_first_visit with a listS as a VertexListS
by Simon Bozonnet 03 Dec '13

03 Dec '13

Hi There, I am struggling with BOOST while trying to link them with my code. Actually I start while using "loops_dfs.cpp" as an example. >From that I isolated the following code which compiles without any problem: typedef adjacency_list < vecS, vecS, bidirectionalS,GraphvizVertexProperty,GraphvizEdgeProperty, GraphvizGraphProperty > Graph; Graph _graph2; typedef color_traits < default_color_type > Color; typedef graph_traits < Graph >::vertex_descriptor VertexType; typedef graph_traits < Graph >::edge_descriptor EdgeType; EdgeType back_edge;//ok I know it is empty but it just to try the compilation!! VertexType loop_head, loop_tail; loop_tail = source(back_edge, _graph2); loop_head = target(back_edge, _graph2); std::vector < default_color_type > reachable_from_head(num_vertices(_graph2), Color::white()); default_color_type c; depth_first_visit(_graph2, loop_head, default_dfs_visitor(), make_iterator_property_map(reachable_from_head.begin(),get(vertex_index, _graph2), c)); So this works fine! Then, I would like to change the type of graph, so more precisely, to use a std::list (or listS) instead of a std..vector (vecS) for the VertexListS So the first line declaration becomes: typedef adjacency_list < vecS, listS, bidirectionalS,GraphvizVertexProperty,GraphvizEdgeProperty, GraphvizGraphProperty > Graph; //only the 2nd argument changes But then when I compile the code, I get 1 error during the compilation as described hereafter. Since I am fighting for more than one day now on this problem, I would **really** appreciate if someone can give me more explanations and/or advice to solve my problem... Thanks in advance, Simon 1>boost/property_map.hpp(351) : error C2679: binary '+' : no operator found which takes a right-hand operand of type 'boost::detail::error_property_not_found' 1>(or there is no acceptable conversion) 1> C:\Program Files (x86)\Microsoft Visual Studio 8\VC\include\vector(366): could be 'std::_Vector_iterator<_Ty,_Alloc> std::_Vector_iterator<_Ty,_Alloc>::operator +(__w64 int) const' 1> with 1> [ 1> _Ty=boost::default_color_type, 1> _Alloc=std::allocator<boost::default_color_type> 1> ] 1> while trying to match the argument list '(const std::_Vector_iterator<_Ty,_Alloc>, boost::detail::error_property_not_found)' 1> with 1> [ 1> _Ty=boost::default_color_type, 1> _Alloc=std::allocator<boost::default_color_type> 1> ] 1> \inc\boost/property_map.hpp(351) : while compiling class template member function 'boost::default_color_type boost::iterator_property_map<RandomAccessIterator,IndexMap,T,R>::operator [](void *) const' 1> with 1> [ 1> RandomAccessIterator=std::_Vector_iterator<boost::default_color_type,std::allocator<boost::default_color_type>>, 1> IndexMap=boost::adj_list_vertex_property_map<boost::adjacency_list<boost::listS,boost::listS,boost::bidirectionalS,LatticeNode,LatticeArc>,boost::detail::error_property_not_found,boost::detail::error_property_not_found &,boost::vertex_index_t>, 1> T=boost::default_color_type, 1> R=boost::default_color_type & 1> ] 1> ..\test.cpp(18) : see reference to class template instantiation 'boost::iterator_property_map<RandomAccessIterator,IndexMap,T,R>' being compiled 1> with 1> [ 1> RandomAccessIterator=std::_Vector_iterator<boost::default_color_type,std::allocator<boost::default_color_type>>, 1> 1> IndexMap=boost::adj_list_vertex_property_map<boost::adjacency_list<boost::listS,boost::listS,boost::bidirectionalS,LatticeNode,LatticeArc>,boost::detail::error_property_not_found,boost::detail::error_property_not_found &,boost::vertex_index_t>, 1> T=boost::default_color_type, 1> R=boost::default_color_type & 1> ]

1 0

[ANN] C++Now 2014: 5 Days to Submissions Deadline
by Boris Kolpackov 03 Dec '13

03 Dec '13

Hi, Only 5 days left before the submissions deadline for C++Now 2014! C++Now is a general C++ conference for C++ experts and enthusiasts. It is not specific to any library/framework or compiler vendor and has three tracks with presentations ranging from hands-on, practical tutorials to advanced C++ design and development techniques. For more information about C++Now, see the conference's website: http://cppnow.org/about/ Have you learned something interesting about C++ (e.g., a new technique possible in C++11)? Or maybe you have implemented something cool related to C++ (e.g., a C++ library)? If so, consider sharing it with other C++ enthusiasts by giving a talk at C++Now 2014. For more information on possible topics, formats, etc., see the call for submissions: http://cppnow.org/2013/10/21/2014-call-for-submissions/ Boris

1 0

Re: [Boost-users] [Thread] Using thread accross libraries
by Sébastien Gallou 02 Dec '13

02 Dec '13

> > You are linking to the static Boost.Thread library. This means that > you've got two distinct Boost.Thread libraries loaded into your process, > one into the executable and one in the DLL. Thanks Lars, you solve my problem. Effectively, I was linking with the static lib. When I was looking how to build shared libs, I found in the boost documentation that shared build should be the default. http://www.boost.org/boost-build2/doc/html/bbv2/tutorial/linkage.html I'm under Windows, and without add link=shared to the b2 command line, the build is static. Next was the problem to link my app with boost. It was necessary to define BOOST_ALL_DYN_LINK in boost\config\user.hpp, while the comment just above says that it should not be needed for boost_thread : "Forces all libraries [...] to be linked as dll's rather than static libraries on Microsoft Windows. [...] Note that there may be some libraries that can only [...] be dynamically linked (Boost.Threads for example), in these cases this macro has no effect." Is something I didn't well understand ? Anyway, it now works, Thank you again Lars, Sebastien Gallou

1 0

Re: [Boost-users] Boost-users Digest, Vol 3643, Issue 1
by Damien Kick 02 Dec '13

02 Dec '13

On Dec 1, 2013, at 11:00 AM, boost-users-request(a)lists.boost.org wrote: > Date: Sun, 1 Dec 2013 20:38:32 +0530 > From: Rahul Mathur <srivmuk(a)gmail.com> > Subject: [Boost-users] ZeroMQ integration with Boost-v1.54 > Message-ID: > <CALtf4sBn6Dh0WVOgAfaXvSj4obMiMw335w88xDj5vguPOoHMaw(a)mail.gmail.com> […] > BTW, How do I proceed to have ZeroMQ integrated with Boost-v1.54 with > GCC on Linux platform? Here is some code that I've been using to integrate Boost.Asio and 0MQ. The OP question asked for GNU/Linux only but this code has been working for me on both Windows and POSIX. Most of this comes from comments on various Internet forums but integrates together a few things which I personally found less than obvious on my first few attempts. For example, most of the code snippets I found only mentioned POSIX and I had to beat my head against a few walls to get something that worked on both, though YMMV. ==> config.hpp.in <== #ifndef INCLUDE_SHOR_DM_CONFIG_HPP #define INCLUDE_SHOR_DM_CONFIG_HPP // Boost C++ headers #include <boost/filesystem.hpp> // C++ headers #include <string> #ifndef _WIN32_WINNT # define _WIN32_WINNT 0x0601 #endif #ifdef _MSC_VER # define SHOR_DM_CONSTEXPR # define SHOR_DM_DEFAULT_CTOR(expr) expr { } # define SHOR_DM_DEFAULT_COPY(expr) # define SHOR_DM_DEFAULT_DTOR(expr) expr { } # define SHOR_DM_DEFAULT_ASSIGN(expr) # define SHOR_DM_DELETE(expr) expr # define SHOR_DM_NOEXCEPT throw() #else # define SHOR_DM_CONSTEXPR constexpr # define SHOR_DM_DEFAULT_CTOR(expr) expr = default # define SHOR_DM_DEFAULT_COPY(expr) expr = default # define SHOR_DM_DEFAULT_DTOR(expr) expr = default # define SHOR_DM_DEFAULT_ASSIGN(expr) expr = default # define SHOR_DM_DELETE(expr) expr = delete # define SHOR_DM_NOEXCEPT noexcept #endif #endif ==> zee/basic_zmq_fd.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_BASIC_ZMQ_FD_HPP #define INCLUDE_SHOR_DM_ZEE_BASIC_ZMQ_FD_HPP // 0MQ headers #include <zmq.hpp> namespace shor { namespace dm { namespace zee { template<typename Native_handle> struct Basic_zmq_fd { typedef Native_handle native_handle_type; typedef native_handle_type value_type; private: zmq::socket_t& zmq_socket_; Native_handle zmq_fd_; public: explicit Basic_zmq_fd(zmq::socket_t& zmq_socket) : zmq_socket_(zmq_socket), zmq_fd_() { std::size_t zmq_fd_size = sizeof(zmq_fd_); zmq_socket_.getsockopt(ZMQ_FD, &zmq_fd_, &zmq_fd_size); } value_type operator () () const { return zmq_fd_; } }; } // namespace zee } // namespace dm } // namespace shor #endif ==> zee/handler.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_HANDLER_HPP #define INCLUDE_SHOR_DM_ZEE_HANDLER_HPP // DM headers #include "dm/zee/msg.hpp" // Boost C++ headers #include <boost/system/error_code.hpp> #include <boost/function.hpp> // C++ headers #include <functional> namespace shor { namespace dm { namespace zee { typedef std::function< void (const boost::system::error_code& err, shor::dm::zee::Msg& msg) > Async_recv_handler; } // namespace zee } // namespace dm } // namespace shor #endif ==> zee/lossy_service.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_LOSSY_SERVICE_HPP #define INCLUDE_SHOR_DM_ZEE_LOSSY_SERVICE_HPP // Boost C++ headers #include <boost/asio.hpp> namespace shor { namespace dm { namespace zee { template<typename Service> struct Lossy_service : public Service { explicit Lossy_service(boost::asio::io_service& ios) : Service(ios) { } void destory(typename Service::implementation_type& impl) { } }; } // namespace zee } // namespace dm } // namespace shor #endif ==> zee/msg.cpp <== #include "dm/zee/msg.hpp" shor::dm::zee::detail::Msg::Frame::Frame( Frame&& that) : that_(std::move(that.that_)) { } shor::dm::zee::detail::Msg::Frame::Frame( zmq::message_t&& that) : that_(std::move(that)) { } shor::dm::zee::detail::Msg::Frame::Frame( const std::string& the_other) : that_(the_other.size()) { std::copy(the_other.begin(), the_other.end(), static_cast<char*>(that_.data())); } shor::dm::zee::detail::Msg::Frame& shor::dm::zee::detail::Msg::Frame::operator = ( Frame&& that) { that_ = std::move(that.that_); return *this; } shor::dm::zee::detail::Msg::Frame& shor::dm::zee::detail::Msg::Frame::operator = ( const std::string& the_other) { that_.rebuild(the_other.size()); std::copy(the_other.begin(), the_other.end(), static_cast<char*>(that_.data())); return *this; } shor::dm::zee::detail::Msg::Msg( Msg&& that) : frames_(std::move(that.frames_)) { } shor::dm::zee::detail::Msg& shor::dm::zee::detail::Msg::operator = ( Msg&& that) { frames_ = std::move(that.frames_); return *this; } ==> zee/msg.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_MSG_HPP #define INCLUDE_SHOR_DM_ZEE_MSG_HPP // My header #include "dm/zee/msg_fwd.hpp" // DM headers #include "dm/config.hpp" // 0MQ headers #include <zmq.hpp> // C++ headers #include <deque> namespace shor { namespace dm { namespace zee { namespace detail { struct Msg { class Frame { zmq::message_t that_; public: SHOR_DM_DEFAULT_CTOR(Frame()); Frame(Frame&& that); Frame(zmq::message_t&& that); Frame(const std::string& the_other); SHOR_DM_DEFAULT_DTOR(~Frame()); Frame& operator = (Frame&& that); Frame& operator = (const std::string& the_other); operator zmq::message_t& (); operator const zmq::message_t& () const; zmq::message_t& get(); const zmq::message_t& cget() const; const zmq::message_t& get() const; private: SHOR_DM_DELETE(Frame(const Frame& that)); SHOR_DM_DELETE(Frame& operator = (const Frame& that)); }; typedef std::deque<Frame> Frames; private: Frames frames_; public: SHOR_DM_DEFAULT_CTOR(Msg()); Msg(Msg&& that); SHOR_DM_DEFAULT_DTOR(~Msg()); Msg& operator = (Msg&& that); Frames& frames(); const Frames& frames() const; private: SHOR_DM_DELETE(Msg(const Msg& that)); SHOR_DM_DELETE(Msg& operator = (const Msg& that)); }; } // namespace detail typedef detail::Msg Msg; } // namespace zee } // namespace dm } // namespace shor #include "dm/zee/msg.ipp" #endif ==> zee/msg.ipp <== #ifndef INCLUDE_SHOR_DM_ZEE_MSG_IPP #define INCLUDE_SHOR_DM_ZEE_MSG_IPP // My header #include "dm/zee/msg.hpp" inline shor::dm::zee::detail::Msg::Frame::operator zmq::message_t& () { return that_; } inline shor::dm::zee::detail::Msg::Frame::operator const zmq::message_t& () const { return that_; } inline zmq::message_t& shor::dm::zee::detail::Msg::Frame::get() { return that_; } inline const zmq::message_t& shor::dm::zee::detail::Msg::Frame::cget() const { return that_; } inline const zmq::message_t& shor::dm::zee::detail::Msg::Frame::get() const { return that_; } inline shor::dm::zee::detail::Msg::Frames& shor::dm::zee::detail::Msg::frames() { return frames_; } inline const shor::dm::zee::detail::Msg::Frames& shor::dm::zee::detail::Msg::frames() const { return frames_; } #endif ==> zee/msg_fwd.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_MSG_FWD_HPP #define INCLUDE_SHOR_DM_ZEE_MSG_FWD_HPP namespace shor { namespace dm { namespace zee { namespace detail { struct Msg; } // namespace detail typedef detail::Msg Msg; } // namespace zee } // namespace dm } // namespace shor #endif ==> zee/posix_zmq_socket.cpp <== // My header #include "dm/zee/posix_zmq_socket.hpp" // DM headers #include "dm/zee/handler.hpp" // Boost C++ headers #include <boost/bind.hpp> struct shor::dm::zee::detail::Posix_zmq_socket::Read_handler { typedef Posix_zmq_socket::implementation_type Io_type; typedef Posix_zmq_socket::Base_read_handler Base_read_handler; private: Io_type& io_; Base_read_handler read_handler_; Async_recv_handler recv_handler_; public: Read_handler( Io_type& io, Base_read_handler read_handler, Async_recv_handler recv_handler) : io_(io), read_handler_(read_handler), recv_handler_(recv_handler) { } void operator () ( const boost::system::error_code& err, std::size_t /*bytes_transferred*/) { read_handler_(*this, err, recv_handler_); } void operator () () { io_.async_read_some(boost::asio::null_buffers(), *this); } }; shor::dm::zee::detail::Posix_zmq_socket::Posix_zmq_socket( boost::asio::io_service& ios, zmq::context_t& zenv, const int zmq_socket_type) : Zmq_socket_base(ios, zenv, zmq_socket_type), zmq_fd_(Zmq_socket_base::zmq_socket()), io_(ios, zmq_fd_()), io_release_(&io_, Release()) { } void shor::dm::zee::detail::Posix_zmq_socket::async_recv( Async_recv_handler recv_handler) { const auto base_read_handler_fn = boost::bind( &Posix_zmq_socket::read_handler, this, _1, _2, _3); Read_handler read_handler( std::ref(io_), base_read_handler_fn, recv_handler); read_handler(); } void shor::dm::zee::detail::Posix_zmq_socket::close_ext() { this->cancel(); // TODO: reset zmq_fd_ io_.release(); } ==> zee/posix_zmq_socket.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_POSIX_ZMQ_SOCKET_HPP #define INCLUDE_SHOR_DM_ZEE_POSIX_ZMQ_SOCKET_HPP // Base class header #include "dm/zee/zmq_socket_base.hpp" // DM headers #include "dm/zee/handler.hpp" #include "dm/zee/lossy_service.hpp" #include "dm/zee/basic_zmq_fd.hpp" // Boost C++ headers #include <boost/asio/posix/basic_stream_descriptor.hpp> #include <boost/asio/posix/stream_descriptor_service.hpp> #include <boost/asio.hpp> namespace shor { namespace dm { namespace zee { namespace detail { class Posix_zmq_socket : public Zmq_socket_base { using Stream_descriptor_service = boost::asio::posix::stream_descriptor_service; template<typename Service> using Basic_stream_descriptor = boost::asio::posix::basic_stream_descriptor<Service>; // Borrowed from <http://preview.tinyurl.com/n6jh2ne> but it // doesn't seem to work; i.e. I was still finding that the file // descriptor was being closed, causing a crash at shutdown. // Because of this, I (re)introduced Release (see below). typedef Lossy_service<Stream_descriptor_service> service_type; typedef Basic_stream_descriptor<service_type> implementation_type; struct Read_handler; struct Release { void operator () (implementation_type* ptr) { if (ptr->is_open()) { ptr->release(); } } }; Basic_zmq_fd<int> zmq_fd_; implementation_type io_; std::unique_ptr<implementation_type, Release> io_release_; public: Posix_zmq_socket( boost::asio::io_service& ios, zmq::context_t& zenv, int zmq_socket_type); SHOR_DM_DEFAULT_DTOR(~Posix_zmq_socket()); void async_recv(Async_recv_handler handler); void cancel(); private: SHOR_DM_DELETE(Posix_zmq_socket(const Posix_zmq_socket& that)); SHOR_DM_DELETE( Posix_zmq_socket& operator = (const Posix_zmq_socket& that)); virtual void close_ext() override; }; } // namespace detail typedef detail::Posix_zmq_socket Posix_zmq_socket; } // namespace zee } // namespace dm } // namespace shor #include "dm/zee/posix_zmq_socket.ipp" #endif ==> zee/posix_zmq_socket.ipp <== #ifndef INCLUDE_SHOR_DM_ZEE_POSIX_ZMQ_SOCKET_IPP #define INCLUDE_SHOR_DM_ZEE_POSIX_ZMQ_SOCKET_IPP // My header #include "dm/zee/posix_zmq_socket.hpp" inline void shor::dm::zee::detail::Posix_zmq_socket::cancel() { io_.cancel(); } #endif ==> zee/windows_zmq_socket.cpp <== // My header #include "dm/zee/windows_zmq_socket.hpp" // DM headers #include "dm/zee/handler.hpp" // Boost C++ headers #include <boost/system/error_code.hpp> #include <boost/system/system_error.hpp> #include <boost/asio/error.hpp> #include <boost/bind.hpp> struct shor::dm::zee::detail::Windows_zmq_socket::Read_handler { typedef Windows_zmq_socket::implementation_type Io_type; typedef Windows_zmq_socket::Base_read_handler Base_read_handler; private: Io_type& io_; Base_read_handler read_handler_; Async_recv_handler recv_handler_; public: Read_handler( Io_type& io, Base_read_handler read_handler, Async_recv_handler recv_handler) : io_(io), read_handler_(read_handler), recv_handler_(recv_handler) { } void operator () (const boost::system::error_code& err) { read_handler_(*this, err, recv_handler_); } void operator () () { io_.async_wait(*this); } }; shor::dm::zee::detail::Windows_zmq_socket::Windows_zmq_socket( boost::asio::io_service& ios, zmq::context_t& zenv, const int zmq_socket_type) : Zmq_socket_base(ios, zenv, zmq_socket_type), zmq_fd_(Zmq_socket_base::zmq_socket()), io_(ios) { auto zfd_event = CreateEvent( nullptr, // default security settings false, // auto reset false, // initial state: unsignalled nullptr); // anonymous object if (!zfd_event) { const boost::system::error_code an_error_code( GetLastError(), boost::asio::error::get_system_category()); throw boost::system::system_error(an_error_code, "CreateEvent"); } io_.assign(zfd_event); if (WSAEventSelect(zmq_fd_(), zfd_event, FD_READ) == SOCKET_ERROR) { const boost::system::error_code an_error_code( WSAGetLastError(), boost::asio::error::get_system_category()); throw boost::system::system_error( an_error_code, "WSAEventSelect"); } } void shor::dm::zee::detail::Windows_zmq_socket::async_recv( Async_recv_handler recv_handler) { const auto base_read_handler_fn = boost::bind( &Windows_zmq_socket::read_handler, this, _1, _2, _3); Read_handler read_handler( std::ref(io_), base_read_handler_fn, recv_handler); read_handler(); } void shor::dm::zee::detail::Windows_zmq_socket::close_ext() { this->cancel(); // TODO: reset zmq_fd_ io_.close(); } ==> zee/windows_zmq_socket.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_WINDOWS_ZMQ_SOCKET_HPP #define INCLUDE_SHOR_DM_ZEE_WINDOWS_ZMQ_SOCKET_HPP // Base class header #include "dm/zee/zmq_socket_base.hpp" // DM headers #include "dm/zee/basic_zmq_fd.hpp" #include "dm/zee/handler.hpp" // Boost C++ headers #include <boost/asio/windows/object_handle.hpp> #include <boost/asio.hpp> namespace shor { namespace dm { namespace zee { namespace detail { class Windows_zmq_socket : public Zmq_socket_base { typedef boost::asio::windows::object_handle implementation_type; struct Read_handler; Basic_zmq_fd<SOCKET> zmq_fd_; implementation_type io_; public: Windows_zmq_socket( boost::asio::io_service& ios, zmq::context_t& zenv, int zmq_socket_type); SHOR_DM_DEFAULT_DTOR(~Windows_zmq_socket()); void async_recv(Async_recv_handler handler); void cancel(); private: SHOR_DM_DELETE(Windows_zmq_socket(const Windows_zmq_socket& that)); SHOR_DM_DELETE( Windows_zmq_socket& operator = (const Windows_zmq_socket& that)); virtual void close_ext() override; }; } // namespace detail typedef detail::Windows_zmq_socket Windows_zmq_socket; } // namespace zee } // namespace dm } // namespace shor #include "dm/zee/windows_zmq_socket.ipp" #endif ==> zee/windows_zmq_socket.ipp <== #ifndef INCLUDE_SHOR_DM_ZEE_WINDOWS_ZMQ_SOCKET_IPP #define INCLUDE_SHOR_DM_ZEE_WINDOWS_ZMQ_SOCKET_IPP // My header #include "dm/zee/windows_zmq_socket.hpp" inline void shor::dm::zee::detail::Windows_zmq_socket::cancel() { io_.cancel(); } #endif ==> zee/zmq_socket.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_ZMQ_SOCKET_HPP #define INCLUDE_SHOR_DM_ZEE_ZMQ_SOCKET_HPP // My header #include "dm/zee/zmq_socket_fwd.hpp" // Conditional headers #ifndef _MSC_VER # include "dm/zee/posix_zmq_socket.hpp" #else # include "dm/zee/windows_zmq_socket.hpp" #endif // Boost C++ headers #include <boost/asio.hpp> namespace shor { namespace dm { namespace zee { #ifndef _MSC_VER typedef Posix_zmq_socket Zmq_socket; #else typedef Windows_zmq_socket Zmq_socket; #endif } // namespace zee } // namespace dm } // namespace shor #endif ==> zee/zmq_socket_base.cpp <== // My headers #include "dm/zee/zmq_socket_base.hpp" // C++ headers #include <cassert> shor::dm::zee::detail::Zmq_socket_base::Opts::Opts( zmq::socket_t& zmq_socket) : zmq_socket_(zmq_socket) { } shor::dm::zee::detail::Zmq_socket_base::Zmq_socket_base( boost::asio::io_service& ios, zmq::context_t& zenv, const int zmq_socket_type) : ios_(ios), zenv_(zenv), zmq_socket_(zenv, zmq_socket_type), opts_(zmq_socket_) { opts_.linger(0); } bool shor::dm::zee::detail::Zmq_socket_base::send( Msg msg) { if (msg.frames().empty()) { auto frame = Msg::Frame(); const auto send_p = zmq_socket_.send(frame); static_cast<void>(opts_.events()); return send_p; } const auto first = msg.frames().begin(); const auto last = std::prev(msg.frames().end()); for (auto pos = first; pos != last; ++pos) { const auto send_p = zmq_socket_.send(*pos, ZMQ_SNDMORE); static_cast<void>(opts_.events()); if (!send_p) { return false; } } const auto send_p = zmq_socket_.send(msg.frames().back(), 0); static_cast<void>(opts_.events()); return send_p; } shor::dm::zee::Msg shor::dm::zee::detail::Zmq_socket_base::recv() { Msg my_value; int more_p = 0; do { zmq::message_t frame; const int flags = 0; zmq_socket_.recv(&frame, flags); static_cast<void>(opts_.events()); my_value.frames().push_back(std::move(frame)); more_p = opts_.rcvmore(); } while (more_p); return my_value; } void shor::dm::zee::detail::Zmq_socket_base::read_handler( std::function<void ()> io_fn, const boost::system::error_code& err, const Async_recv_handler recv_handler) { if (err == boost::asio::error::operation_aborted) { auto msg = Msg(); recv_handler(err, msg); } else if (opts_.events() & ZMQ_POLLIN) { do { auto msg = this->recv(); recv_handler(err, msg); } while (opts_.events() & ZMQ_POLLIN); } else { io_fn(); } } ==> zee/zmq_socket_base.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_ZMQ_SOCKET_BASE_HPP #define INCLUDE_SHOR_DM_ZEE_ZMQ_SOCKET_BASE_HPP // DM headers #include "dm/zee/handler.hpp" #include "dm/zee/msg.hpp" // 0MQ headers #include <zmq.hpp> // Boost C++ headers #include <boost/asio.hpp> // C++ headers #include <string> namespace shor { namespace dm { namespace zee { namespace detail { struct Zmq_socket_base { class Opts { zmq::socket_t& zmq_socket_; public: explicit Opts(zmq::socket_t& zmq_socket); SHOR_DM_DEFAULT_DTOR(~Opts()); void linger(int value); void subscribe(const std::string& value); int events() const; int linger() const; int rcvmore() const; private: template<typename Opt_value> Opt_value getsockopt(int opt_name) const; void setsockopt(int opt_name, const std::string& opt_value); template<typename Opt_value> void setsockopt(int opt_name, const Opt_value& opt_value); SHOR_DM_DELETE(Opts(const Opts& that)); SHOR_DM_DELETE(Opts& operator = (const Opts& that)); }; private: boost::asio::io_service& ios_; zmq::context_t& zenv_; zmq::socket_t zmq_socket_; Opts opts_; public: void bind(const char* addr); void bind(const std::string& addr); void close(); void connect(const char* addr); void connect(const std::string& addr); boost::asio::io_service& get_io_service(); Opts& opts(); bool send(Msg msg); Msg recv(); bool connected() const; const boost::asio::io_service& get_const_io_service() const; const boost::asio::io_service& get_io_service() const; const Opts& opts() const; protected: typedef std::function<void ()> Void_fn; typedef std::function< void (Void_fn, const boost::system::error_code& err, Async_recv_handler recv_handler) > Base_read_handler; Zmq_socket_base( boost::asio::io_service& ios, zmq::context_t& zenv, int zmq_socket_type); SHOR_DM_DEFAULT_DTOR(virtual ~Zmq_socket_base()); void read_handler( std::function<void ()> io_fn, const boost::system::error_code& err, Async_recv_handler handler); zmq::context_t& zenv(); zmq::socket_t& zmq_socket(); const zmq::context_t& const_zenv() const; const zmq::socket_t& const_zmq_socket() const; const zmq::context_t& zenv() const; const zmq::socket_t& zmq_socket() const; private: SHOR_DM_DELETE(Zmq_socket_base(const Zmq_socket_base& that)); SHOR_DM_DELETE( Zmq_socket_base& operator = (const Zmq_socket_base& that)); virtual void close_ext() = 0; }; } // namespace detail typedef detail::Zmq_socket_base Zmq_socket_base; } // namespace zee } // namespace dm } // namespace shor #include "dm/zee/zmq_socket_base.ipp" #endif ==> zee/zmq_socket_base.ipp <== #ifndef INCLUDE_SHOR_DM_ZEE_ZMQ_SOCKET_BASE_IPP #define INCLUDE_SHOR_DM_ZEE_ZMQ_SOCKET_BASE_IPP // My header #include "dm/zee/zmq_socket_base.hpp" inline void shor::dm::zee::detail::Zmq_socket_base::Opts::linger( const int value) { this->setsockopt(ZMQ_LINGER, value); } inline void shor::dm::zee::detail::Zmq_socket_base::Opts::subscribe( const std::string& value) { this->setsockopt(ZMQ_SUBSCRIBE, value); } inline int shor::dm::zee::detail::Zmq_socket_base::Opts::events() const { return this->getsockopt<int>(ZMQ_EVENTS); } inline int shor::dm::zee::detail::Zmq_socket_base::Opts::linger() const { return this->getsockopt<int>(ZMQ_LINGER); } inline int shor::dm::zee::detail::Zmq_socket_base::Opts::rcvmore() const { return this->getsockopt<int>(ZMQ_RCVMORE); } template<typename Opt_value> Opt_value shor::dm::zee::detail::Zmq_socket_base::Opts::getsockopt( const int opt_name) const { Opt_value opt_value; std::size_t opt_size = sizeof(Opt_value); zmq_socket_.getsockopt(opt_name, &opt_value, &opt_size); return opt_value; } inline void shor::dm::zee::detail::Zmq_socket_base::Opts::setsockopt( const int opt_name, const std::string& opt_value) { zmq_socket_.setsockopt(opt_name, opt_value.c_str(), opt_value.size()); } template<typename Opt_value> inline void shor::dm::zee::detail::Zmq_socket_base::Opts::setsockopt( const int opt_name, const Opt_value& opt_value) { const std::size_t opt_size = sizeof(Opt_value); zmq_socket_.setsockopt(opt_name, &opt_value, opt_size); } inline void shor::dm::zee::detail::Zmq_socket_base::bind( const char* addr) { zmq_socket_.bind(addr); } inline void shor::dm::zee::detail::Zmq_socket_base::bind( const std::string& addr) { zmq_socket_.bind(addr.c_str()); } inline void shor::dm::zee::detail::Zmq_socket_base::close() { this->close_ext(); zmq_socket_.close(); } inline void shor::dm::zee::detail::Zmq_socket_base::connect( const char* addr) { zmq_socket_.connect(addr); } inline void shor::dm::zee::detail::Zmq_socket_base::connect( const std::string& addr) { zmq_socket_.connect(addr.c_str()); } inline boost::asio::io_service& shor::dm::zee::detail::Zmq_socket_base::get_io_service() { return ios_; } inline shor::dm::zee::detail::Zmq_socket_base::Opts& shor::dm::zee::detail::Zmq_socket_base::opts() { return opts_; } inline bool shor::dm::zee::detail::Zmq_socket_base::connected() const { // This function should have been const in zmq::socket_t return const_cast<zmq::socket_t&>(zmq_socket_).connected(); } inline const boost::asio::io_service& shor::dm::zee::detail::Zmq_socket_base::get_const_io_service() const { return ios_; } inline const boost::asio::io_service& shor::dm::zee::detail::Zmq_socket_base::get_io_service() const { return ios_; } inline zmq::context_t& shor::dm::zee::detail::Zmq_socket_base::zenv() { return zenv_; } inline zmq::socket_t& shor::dm::zee::detail::Zmq_socket_base::zmq_socket() { return zmq_socket_; } inline const zmq::context_t& shor::dm::zee::detail::Zmq_socket_base::const_zenv() const { return zenv_; } inline const zmq::socket_t& shor::dm::zee::detail::Zmq_socket_base::const_zmq_socket() const { return zmq_socket_; } inline const zmq::context_t& shor::dm::zee::detail::Zmq_socket_base::zenv() const { return zenv_; } inline const zmq::socket_t& shor::dm::zee::detail::Zmq_socket_base::zmq_socket() const { return zmq_socket_; } #endif ==> zee/zmq_socket_fwd.hpp <== #ifndef INCLUDE_SHOR_DM_ZEE_ZMQ_SOCKET_FWD_HPP #define INCLUDE_SHOR_DM_ZEE_ZMQ_SOCKET_FWD_HPP namespace shor { namespace dm { namespace zee { namespace detail { #ifndef _MSC_VER class Posix_zmq_socket; #else class Windows_zmq_socket; #endif } // namespace detail #ifndef _MSC_VER typedef detail::Posix_zmq_socket Posix_zmq_socket; typedef Posix_zmq_socket Zmq_socket; #else typedef detail::Windows_zmq_socket Windows_zmq_socket; typedef Windows_zmq_socket Zmq_socket; #endif } // namespace zee } // namespace dm } // namespace shor #endif ________________________________ This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents.

1 0

ZeroMQ integration with Boost-v1.54
by Rahul Mathur 02 Dec '13

02 Dec '13

All, Looking to have ZeroMQ integration with Boost-v1.54. I am familiar with Boost.ASIO client and Server model. BTW, How do I proceed to have ZeroMQ integrated with Boost-v1.54 with GCC on Linux platform?

3 2

Ask for material about the algorithm of boost::polygon in detail
by rogy liu 02 Dec '13

02 Dec '13

Hi all, I want to optimize the performance of the boolean operation of boost::polygon with CUDA. I want to speedup it at the source code level, and I found it is hard to speedup the hot spot because of dependency & container. Then, I want to evaluate the feasibility from the algorithm. I have found the article "Industrial strength polygon clipping - A novel algorithm with applications in VLSI CAD", but I think it is hard to understand. Do you have more material for study? Thanks, Rogy

1 0

[MSM] Best place to execute an action with return value
by Daniele Barzotti 02 Dec '13

02 Dec '13

Hi, I'm diving into this very useful piece of code which is MSM and I'm modelling a state machine for a gsm modem. When I have to perform a call I need to move from the IDLE state to WAITING_RESPONSE and, in the transaction action I have to call the MakeCall() method on my GSM object. This method has a return value and a non 0 value means it is failed. In this situation the SM don't have to move on to the next state but remains in the IDLE one, so... Since the Actions has no return value, I have to use a Guard instead or I have to add another state called MAKE_CALL? Thanks in advance, Daniele.

2 4

[OT] Boost Programming forum
by Daniele Barzotti 30 Nov '13

30 Nov '13

Hi, I'm sorry for this off-topic but... I received an email which informs me that I was been registered into this forum: http://www.boostprogramming.com/forum/index.php So, since I'm not register myself, I would ask if this site has some relation with boost community. Regards, Daniele.

2 1

[Multi-Index] Skip-Scan "virtual" ordered-non-unique index on top of composite ordered-unique index
by Dominique Devienne 29 Nov '13

29 Nov '13

We have BMIs of entries with complex composite "natural-keys". For example: typedef boost::multi_index_container< FooIdPtr, // FYI: boost::shared_ptr<FooId> bmi::indexed_by< EntityIndex<ByUid>::unique, // FYI: Surrogate/Primary Key EntityIndex<ByNKey>::of<FooId>::unique, // FYI: Natural Key // additional indexes by type, name and parent EntityIndex<ByType>::non_unique, EntityIndex<ByName>::non_unique, EntityIndex<ByParent>::non_unique > > Impl; The EntityIndex template utility simply factors the index definitions used in several BMIs. For example template <> struct EntityIndex<ByNKey> { template <typename T_IDENT> struct of { typedef hashed_unique< // natural key (logical primary key) tag<ByNKey>, identity< shared_ptr<T_IDENT> >, EntityIdHash<T_IDENT>, EntityIdPred<T_IDENT> > unique; }; }; template <> struct EntityIndex<ByParent> { typedef hashed_non_unique< tag<ByParent>, BOOST_MULTI_INDEX_CONST_MEM_FUN( EntityId, const Uid&, parent_uid // FYI: EntityId is the base class of FooId and co. ) > non_unique; }; After recently reading http://www.sqlite.org/draft/optoverview.html#skipscan and its Skip-Scan optimization, I wondered about changing my ByNKey unique index from hashed to ordered, and thought that in theory, I could perhaps avoid the maintenance and memory cost of the additional type+name+parent indexes, since all three are subsets of the ByNKey unique index, and using a similar skip-scan strategy, which might/would still provide reasonable performance, at least better than no index at all (i.e. a full scan). I know BMI does not provide this of course, but do you think Joaquin that it would be possible to one-day add such "virtual" ordered non-unique indexes on top of an existing ordered (possibly unique) composite index? Of course in this case, the composite'ness is hidden inside FooId, and not exposed to BMI (it used to be a true BMI composite index, but modeling the identity as an object made more sense and simplified things), so whether an index is a subset of another would need to be "configurable" in some way, to yield a "compatible key" with the right "prefix" keys to skip to the next "sub-range" to scan (hopefully that makes sense...). I think I would be able to write custom code on top of a ByNKey ordered-non-unique index to implement a subset of the functionality a true BMI ordered non-unique index provides, for my own needs (with some difficulty, but feasible nonetheless), but the kind of template meta-programming BMI uses to implements its indexes is beyond my current skill level, which is why I'm posting to see what the experts (i.e. Joaquin) thinks about this Skip-Scan virtual indexes idea. Thanks, --DD

2 4

Serialization problem with cyclic references (pointers)
by krisdamato 29 Nov '13

29 Nov '13

Try steppin through this code where the deserialization takes place. On every machine I've tried this (and I've tried it with two different Boost builds as well) parent stays null every time. Can anyone point out the reason why? This is giving me a headache :( I suspect it's got something to do with there being cyclic references between parent and child... #include <boost\archive\binary_oarchive.hpp> #include <boost\archive\binary_iarchive.hpp> #include <boost\serialization\vector.hpp> #include <fstream> #include <memory> #include <vector> class A { public: A() { parent = nullptr; someInt = 0; } template <class Archive> void serialize(Archive& archive, const unsigned int version) { archive & someInt; archive & parent; archive & children; } int someInt; A* parent; std::vector<A*> children; }; int main() { A* newA = new A(); A* newPtr = new A(); newPtr->someInt = 5; newPtr->parent = newA; newA->children.push_back(newPtr); // Save. std::ofstream outputFile("test", std::fstream::out | std::fstream::binary); if (outputFile.is_open()) { boost::archive::binary_oarchive outputArchive(outputFile); // Serialize objects. outputArchive << newA; outputArchive << newPtr; outputFile.close(); } delete newA; delete newPtr; newA = nullptr; newPtr = nullptr; // Load.| std::ifstream inputFile("test", std::fstream::binary | std::fstream::in); if (inputFile && inputFile.good() && inputFile.is_open()) { boost::archive::binary_iarchive inputArchive(inputFile); // Load objects. inputArchive >> newA; inputArchive >> newPtr; inputFile.close(); } return 0; } -- View this message in context: http://boost.2283326.n4.nabble.com/Serialization-problem-with-cyclic-refere… Sent from the Boost - Users mailing list archive at Nabble.com.

2 2

[Exception] How do I inherit custom exception hierarchy from std::runtime_error rather than from std::exception?
by Egor Tensin 29 Nov '13

29 Nov '13

Hi, The issue that's confusing me arose from my intention of inheriting my exception classes from std::runtime_error rather than from std::exception. It seemed logical to me, as my exceptions are really runtime errors; getting something meaningful via what() also seemed like a good idea. However, this doesn't compile: #include <iostream> #include <stdexcept> #include <boost/exception/all.hpp> typedef boost::error_info<struct tag_foo_info, unsigned long> foo_info; struct foo_error : virtual boost::exception, virtual std::runtime_error { explicit foo_error(const char *const what) : std::runtime_error(what) { } explicit foo_error(const std::string& what) : std::runtime_error(what) { } }; static void foo() { BOOST_THROW_EXCEPTION(foo_error("foo error") << foo_info(42)); } int main(int argc, char *argv[]) { try { foo(); } catch (const std::exception& e) { std::cerr << boost::diagnostic_information(e); return 1; } return 0; } It says that there's no default constructor available for std::runtime_error. How do I fix this or should I use the idiomatic approach? The interesting thing is that if I erase the "virtual" keyword, the program compiles flawlessly. I wonder what is the reason for that, e.g. why the original code doesn't work and why the new code does, what are the consequences of making boost::exception and std::runtime_error base (non-virtual) classes, etc. I'm confused as the docs clearly recommends I build exception classes hierarchy using virtual inheritance. Could somebody please give me an insight into the inner workings of the library & inheritance mechanisms? Thank you in advance, Egor.

4 7

[Bind & Function] c function pointers
by Matthijs Möhlmann 29 Nov '13

29 Nov '13

Hello all, It was pointed out to me that the subject line was not correct, so I resent this mail with a correct subject line. I'm not sure if this is possible at all, but let me explain: I have the following function signature: typedef int (*sasl_callback_ft)(void); That function in question gets called with unknown amount of parameters (usually 3 or 4) Now I want to assign a member function to it: class admin { public: int callback_fun(void *context, int id, const char **result, unsigned *len); } boost::function<int(void *, int, const char **, unsigned *)> callback = boost::bind(&admin::callback_fun, this, _1, _2, _3, _4); Obviously the compiler doesn't allow to assign callback to a sasl_callback_ft var sasl_callback_ft fun = callback; I get compiler errors like: matthijs@hammer:~/t2$ clang++ -o main -std=c++11 main.cpp main.cpp:22:19: error: no viable conversion from 'boost::function<int (void *, int, const char **, unsigned int *)>' to 'sasl_callback_ft' (aka 'int (*)()') sasl_callback_ft cbfun = cb; ^ ~~ /usr/include/boost/function/function_template.hpp:894:5: note: candidate function operator safe_bool () const ^ 1 error generated. Attached the testcase I made for this. Regards, Matthijs

2 2

Re: [Boost-users] [Thread] Using thread accross libraries
by Sébastien Gallou 29 Nov '13

29 Nov '13

Antony, Thanks a lot for your answer. But I check the configuration of each project, and same runtime-library is used (/MDd) in both cases. So my problem doesn't come from here. If you have another idea... Thanks for your help, Sébastien

2 1

[Multi-Index] performance difference between lower_bound() and upper_bound()
by Dominique Devienne 29 Nov '13

29 Nov '13

I have a multi-index BMI (Boost 1.44), with an ordered_non_unique index on a"name" string field, which is lexicographically ordered. I'm searching for the range of values of the form "$prefix $integer", i.e. "foo 1", "foo 99", etc... to obtain this "range", I initially used (pseudo-code): auto begin = by_name_index().lower_bound(prefix + " 0"); auto end = by_name_index().upper_bound(prefix + " 9"); and within the range I test the suffix for its number'ness and keep the largest number. But I was surprised to see it performed badly for large number of calls. I switched to using instead: auto begin = by_name_index().lower_bound(prefix + " 0"); auto end = by_name_index().lower_bound(prefix + " :"); And this performs much better (20x). The "corpus" of names of this particular test may be skewing the results, since entries are added to the BMI with monotonically increasing number suffixes, and all entries have the prefix I'm looking for, yet I'm very surprised of such a large performance difference between the lower/upper version, and the lower/lower version. Anyone has a clue what could be going on? Thanks, --DD PS: I'm assuming the two versions are equivalent. Let me know if I'm mistaken please. This is not yet thoroughly tested.

3 6

Put the Library Name in the Subject Line (was: boost and c function pointers)
by Mateusz Loskot 29 Nov '13

29 Nov '13

On 29 November 2013 09:29, Matthijs Möhlmann <matthijs(a)cacholong.nl> wrote: > boost::function<int(void *, int, const char **, unsigned *)> callback = > boost::bind(&admin::callback_fun, this, _1, _2, _3, _4); Please, Put the Library Name in the Subject Line [1], it will save people's time. Name Boost refers to a *collection of libraries, hence Boost has nothing to do with C function pointers. [1] http://www.boost.org/community/policy.html#subject-line Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

boost and c function pointers
by Matthijs Möhlmann 29 Nov '13

29 Nov '13

Hello all, I'm not sure if this is possible at all, but let me explain: I have the following function signature: typedef int (*sasl_callback_ft)(void); That function in question gets called with unknown amount of parameters (usually 3 or 4) Now I want to assign a member function to it: class admin { public: int callback_fun(void *context, int id, const char **result, unsigned *len); } boost::function<int(void *, int, const char **, unsigned *)> callback = boost::bind(&admin::callback_fun, this, _1, _2, _3, _4); Obviously the compiler doesn't allow to assign callback to a sasl_callback_ft var sasl_callback_ft fun = callback; I get compiler errors like: matthijs@hammer:~/t2$ clang++ -o main -std=c++11 main.cpp main.cpp:22:19: error: no viable conversion from 'boost::function<int (void *, int, const char **, unsigned int *)>' to 'sasl_callback_ft' (aka 'int (*)()') sasl_callback_ft cbfun = cb; ^ ~~ /usr/include/boost/function/function_template.hpp:894:5: note: candidate function operator safe_bool () const ^ 1 error generated. Attached the testcase I made for this. Regards, Matthijs

1 0

[mpl][fusion] How to transform vector_c into std::vector?
by Mostafa 29 Nov '13

29 Nov '13

How does one transform an mpl:vector_c into a regular std::vector? Sample input: typedef mpl::vector<int, int_<10>, int_<11>, int_<12> > some_vector_c; Thanks, Mostafa

3 5

Where can I get ml64.exe
by niXman 28 Nov '13

28 Nov '13

Hi, I trying to build boost-1.55 using MinGW-W64 for x86_64 arch. boost.context library requires ml64.exe for building, but I can't find it. I have found ml.exe (it's for i686 arch) on MSDN site[1], but I can't find ml64.exe. The question is where can I get it? Thanks. [1] http://www.microsoft.com/en-us/download/details.aspx?id=12654 -- Regards, niXman ___________________________________________________ Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingw-w64/ ___________________________________________________ Another online IDE: http://liveworkspace.org/

3 3

[Thread] Using thread accross libraries
by Sébastien Gallou 28 Nov '13

28 Nov '13

Hi all, first, thanks for this great library. I'm using Boost::thread and experiencing a problem when trying to interrupt thread executed in a dynamic library (DLL, under Windows). I reproduced it in a minimal example, that I join to this post (I don't know if attachment is authorized so I also put it on my GDrive<https://drive.google.com/file/d/0B3dXqBwTbfcAQ1E0MDRfU0hxNVE/edit?usp=shari…>, and copy the code at the end of this mail). In this code, I start a thread in the main, calling a function "doWork" of a plugin, dynamically loaded. The doWork just do some sleep and wait for boost::thread_interrupted exception. The problem is that the exception is never received when the main call interrupt on the thread. If the doWork code is in the main application, all works well. Trying to debug into Boost, I'm seeing that in the interruptible_wait function, the test "if(detail::get_current_thread_data() && detail::get_current_thread_data()->interruption_enabled)" doesn't give the same result if code is in DLL (test result is false) or in the main (true). What is the reason of this behaviour ? Thanks for your help, Sébastien Gallou Here is the code : *TestBoostThread.cpp :* IPlugin* Plugin; void doWork(){ try { Plugin->doWork(); } catch (boost::thread_interrupted&) { // End-of-thread exception was not catch by plugin, // it's a developer's error, we have to report it std::cout << "Plugin didn't catch boost::thread_interrupted."; }} int main(int argc, char* argv[]){ HMODULE libraryHandle = LoadLibrary(L"Dll.dll"); boost::function<IPlugin* ()> construct = (IPlugin* (*)(void))GetProcAddress(libraryHandle, "construct"); Plugin=construct(); boost::shared_ptr<boost::thread> thread = boost::shared_ptr<boost::thread>(new boost::thread(doWork)); Sleep(1500); thread->interrupt(); thread->join(); FreeLibrary(libraryHandle); return 0;} *Dll.cpp :* class MyPlugin : public IPlugin{ virtual ~MyPlugin(){} virtual void doWork() { try { while(1) { std::cout << "MyPlugin is running..."; // Give a chance to exit plugin thread boost::this_thread::sleep(boost::posix_time::milliseconds(1000)); }; } catch (boost::thread_interrupted&) { std::cout << "MyPlugin is stopped..."; } }}; extern "C" __declspec(dllexport) IPlugin* construct(){ return new MyPlugin;}

2 1

Hash collision for pairs of int
by Saurabh T 27 Nov '13

27 Nov '13

Hi, I'm experiencing a lot of collisions using the hash_combine function in functional/hash/hash.hpp for integer-pairs-as-keys when there are few unique ints in each of the pair's positions (put together the keys themselves are unique of course). I've uploaded a simple enough test case here: http://www.speedyshare.com/Wcem6/hash.cc.gz. If there's a more preferred way to upload, let me know and I'll reupload. With 400K pairs, this returns only 86K unique indices and has a max of 18 collisions in size_t. Am I doing something really wrong here? Thank you. saurabh

3 3

[Graph] filters and subgraphs?
by The Maschine 27 Nov '13

27 Nov '13

Hi all, What Im trying to do is the get a filtered or subgraph that holds the properties of the original graph (vertex and edge bundles). Ill use the 'subgraph' in other algorithms but from time to time I'd like to be able to trace the original vertex_descriptor and push data back to the original graph. (that might be able to happen via the original_vertex_d below but lets see..) Below is an attempt to use graph filters to do it but for reasons that can be found in topics by others, I think this is not going to work. (filtered graph are too simple.. etc) Is it possible to use the 'distance map', that I use to produce a filtered graph, for producing a subgraph that all info from the original (minus the filtered vertexes that we dont want of course) data are there and can be also further used in algorithms? Thanks ///////////////////////////// struct VertexProperties { boost::graph_traits<unGraph>::vertex_descriptor original_vertex_d; // might be needed for the question above double m_bc; // for betweenness ..... .... }; struct EdgeProperties { double m_weight1; double m_weight2; }; typedef double Weight; typedef boost::property<boost::edge_weight_t, double> EdgeWeightProperty; typedef boost::adjacency_list<boost::vecS, boost::vecS, boost::undirectedS, VertexProperties, EdgeProperties> unGraph; typedef boost::graph_traits < unGraph >::vertex_descriptor Vertex; typedef boost::property_map < unGraph, boost::vertex_index_t >::type IndexMap; typedef boost::iterator_property_map < Vertex*, IndexMap, Vertex, Vertex& > PredecessorMap; typedef boost::iterator_property_map < Weight*, IndexMap, Weight, Weight& > DistanceMap; struct vertex_distance_filter { vertex_distance_filter() { } vertex_distance_filter(std::vector<Weight> distance_map, double radius) : m_dist_map(distance_map), m_radius(radius) { } bool operator()(const typename boost::graph_traits<unGraph>::vertex_descriptor& v) const { return m_radius > m_dist_map[v]; } double m_radius; std::vector<Weight> m_dist_map; }; ////// int i = 0; // simplified boost::graph_traits<unGraph>::vertex_descriptor s_vertex = boost::vertex(i, m_ugraph); // Filter std::vector<Vertex> predecessors(boost::num_vertices(m_ugraph)); std::vector<Weight> distances(boost::num_vertices(m_ugraph), std::numeric_limits<double>::max() ); IndexMap indexMap = boost::get(boost::vertex_index, m_ugraph); PredecessorMap predecessorMap(&predecessors[0], indexMap); DistanceMap distanceMap(&distances[0], indexMap); boost::dijkstra_shortest_paths(m_ugraph, s_vertex, boost::weight_map(boost::get(&EdgeProperties::m_weight1, m_ugraph)).predecessor_map(predecessorMap).distance_map(distanceMap)); vertex_distance_filter filter(distances, 400.0f); typedef boost::filtered_graph<unGraph, vertex_distance_filter> FilteredGraphType; FilteredGraphType filteredGraph(m_ugraph, filter); // Work on the filtered graph. Subgraph maybe??? std::vector< double > v_centrality_vec(boost::num_vertices(filteredGraph), 0.0); // different weight from above. here m_weight2 boost::brandes_betweenness_centrality(filteredGraph , boost::centrality_map(boost::make_iterator_property_map(v_centrality_vec.begin(),boost::get(boost::vertex_index, filteredGraph),double())).vertex_index_map(get(boost::vertex_index, m_ugraph)).weight_map(boost::get(&EdgeProperties::m_weight2, m_ugraph)) ); // here we start having problems... comments above boost::graph_traits<unGraph>::vertex_iterator vertex_iterator_begin, vertex_iterator_end; for ( boost::tie(vertex_iterator_begin, vertex_iterator_end) = vertices(filteredGraph); vertex_iterator_begin != vertex_iterator_end; ++vertex_iterator_begin) { // this is the original unfiltered graph!!!! m_ugraph[*vertex_iterator_begin].m_bc = v_centrality_vec[*vertex_iterator_begin]; }

1 0

[log] switching from n loggers to 1
by Eric Prud'hommeaux 27 Nov '13

27 Nov '13

I'm updating an old library which sets up eight separate loggers with different channel labels: BOOST_LOG_INLINE_GLOBAL_LOGGER_DEFAULT(DefaultLog, SWObjectsLogger); BOOST_LOG_INLINE_GLOBAL_LOGGER_CTOR_ARGS(RewriteLog, SWObjectsLogger, (channel = "Rewrite")); ... BOOST_LOG_SEV(L::RewriteLog::get(), L::info) << "foo->bar\n"; I'd like to update to 1.54 (or 1.55) and before I `perl -i` the heck out of it, I'm wondering what are the tradeoffs around using a single logger: BOOST_LOG_INLINE_GLOBAL_LOGGER_DEFAULT(TheLogger, boost::log::sources::severity_channel_logger< severity_level >) ... BOOST_LOG_CHANNEL_SEV(L::TheLogger::get(), L:Rewrite, L::info) << "foo->bar"; I can guess that many loggers gives me more (future) versatility to log Rewrite stuff to a different stream and that these eight loggers come with some memory footprint. Is that about right? (Also, why does adding a template parameter for the channel BOOST_LOG_INLINE_GLOBAL_LOGGER_DEFAULT(TheLogger, boost::log::sources::severity_channel_logger< severity_level >) barf with macro errors? expressions_channel_severity_filter.cpp:306:127: error: macro "BOOST_LOG_INLINE_GLOBAL_LOGGER_DEFAULT" passed 3 arguments, but takes just 2 expressions_channel_severity_filter.cpp:306:1: error: ‘BOOST_LOG_INLINE_GLOBAL_LOGGER_DEFAULT’ does not name a type? ) -- -ericP office: +1.617.599.3509 mobile: +33.6.80.80.35.59 (eric(a)w3.org) Feel free to forward this message to any list for any purpose other than email address distribution. There are subtle nuances encoded in font variation and clever layout which can only be seen by printing this message on high-clay paper.

1 0

[multiarray] How to make a generic one from an existing C multi-array.
by Mostafa 27 Nov '13

27 Nov '13

Given the following: template <typename T, std::size_t D1> void foo(T (&arr)[D1]) { typedef boost::multi_array_ref < typename boost::remove_all_extents<T>::type, boost::rank<T[D1]>::value > arr_type; // ? = ExtentList or extents_tuple. arr_type ma(arr, ?); } Are there any existing tools to create an ExtentList or extents_tuple obj from the type of arr? Thanks, Mostafa

1 0

[graph] How to use default ColorMap when using depth_first_visit
by Laila, Akeel 26 Nov '13

26 Nov '13

Hi, I'm looking to use depth_first_visit to traverse a labeled_graph, but the below code fails to compile due to the absence of ColorMap argument: depth_first_visit(dependencyGraph, targetDepVertex, visitor(cycleDetector)); error C2780: 'void boost::depth_first_visit(const IncidenceGraph &,graph_traits<G>::vertex_descriptor,DFSVisitor,ColorMap,TerminatorFunc)' : expects 5 arguments - 3 provided e:\TR\ToolsRelease\git\boost\1.54.0\src\boost/graph/depth_first_search.hpp:320:0 : see declaration of 'boost::depth_first_visit' error C2780: 'void boost::depth_first_visit(const IncidenceGraph &,graph_traits<G>::vertex_descriptor,DFSVisitor,ColorMap)' : expects 4 arguments - 3 provided e:\TR\ToolsRelease\git\boost\1.54.0\src\boost/graph/depth_first_search.hpp:309:0 : see declaration of 'boost::depth_first_visit' On the other hand, depth_first_search compile just fine: depth_first_search(dependencyGraph, visitor(cycleDetector)); I guess what it comes down to is that a default ColorMap is utilized by depth_first_search. Anyone know how I can access this same default ColorMap (which I can then feed to depth_first_visit()) FYI, my labeled_graph type is defined as follows: typedef boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS , DependencyVertex, DependencyEdge> DependencyGraphInternalType; typedef boost::labeled_graph<DependencyGraphInternalType, string> DependencyGraphType; Thanks, Akeel Laila ________________________________ This email is non-binding, is subject to contract, and neither Kulicke & Soffa Industries Inc nor its subsidiaries shall have any obligation to you to consummate the transactions herein or to enter into any agreement, other than in accordance with the terms and conditions of a definitive agreement if and when negotiated, finalized and executed between the parties.

1 0

how to learn Boost
by e.palmero＠googlemail.com 26 Nov '13

26 Nov '13

Dear Boost Developer: I am new to Boost and I would like to know any suggestion for books to get deeply inside the Boost libraries. Best Ernesto

4 3

[multiprecision] FMA without expression templates?
by Francesco Biscani 26 Nov '13

26 Nov '13

Hello, I would like to start using the Boost multiprecision library in my code. For a series of reasons, I would like to disable the expression template support (I need the return type of a + b to be the type of a or b, and not an expression). My understanding after briefly venturing into the library code is that there is the concept of a multiply_add() function (e.g., in boost/multiprecision/detail/default_ops.hpp), but that such support is hidden behind the expression template magic and it is not exposed when ET is disabled. I tried to look into Boost math as well, where there is a fused multiply-add function, but it seems like it is built to support floating-point types and I need support for integral types (for the implementation of algebraic operations on polynomials with integer coefficients). Is my understanding correct or is there a way to use some kind of a multiply_accumulate function in multiprecision without using ET? Many thanks, Francesco.

1 0

[random] infinite loop in uniform_real_distribution
by Jérémy Coulon 26 Nov '13

26 Nov '13

Hello, I'm using Boost 1.54. The following code hangs in infinite loop when generating a single floating point number : #include <boost/random.hpp> #include <iostream> #include <limits> int main() { boost::random::mt19937 rng; boost::random::uniform_real_distribution<float> distrib( -std::numeric_limits<float>::max(), std::numeric_limits<float>::max()); std::cout << distrib(rng) << std::endl; return 0; } I can reproduce the bug with both - Linux GCC 4.8 x86_64 and - Windows VisualStudio 2012 32bits It looks like this uniform distribution doesn't work if the range [min,max] is large. From uniform_real_distribution.hpp:61 T result = numerator / divisor * (max_value - min_value) + min_value; Here the operation (max_value - min_value) produces an overflow. Regards, Jeremy

3 7

[Iostreams] Segmentation fault when stream is flushed or closed
by Steven Maenhout 26 Nov '13

26 Nov '13

Hello, I'm trying to open a boost::iostreams::stream in the constructor of a class and to close the stream in the destructor. This works fine but when I pass a reference to a std::stringstream in that same constructor I get a segmentation fault in the destructor when I flush or close the stream. This happens irrespective if the passed std::stringstream reference takes part in the boost::iostream::stream or not. I'm using gcc 4.6.3 with boost 1.53 on Linux x86_64. Below I provided a small example that exhibits this behaviour. Any ideas anyone? #include "test.h" int main(int argc, char **argv) { std::stringstream logStream; Test test(logStream); return 0; } where test.h contains: #include <fstream> #include <sstream> #include <boost/iostreams/stream.hpp> #include <boost/iostreams/tee.hpp> typedef boost::iostreams::tee_device<std::stringstream, std::ofstream> TeeDevice; typedef boost::iostreams::stream<TeeDevice> TeeStream; class Test { public: Test(const std::stringstream& logStream) { std::ofstream dummyFileHandle("/dev/null", std::ios_base::out | std::ios_base::app); std::stringstream logStream2; TeeDevice myTee (logStream2, dummyFileHandle); m_out.open(myTee); } virtual ~Test() { if(m_out.is_open()) { m_out.flush(); m_out.close(); } }; protected: TeeStream m_out; };

2 4

activating Boost Graph Library finish_edge
by Michael Behrns-Miller 25 Nov '13

25 Nov '13

Hello boost users. I'm using BGL, and was happy to see the addition of the finish_edge() visitor to DFS. I had previously added code to finish_vertex() to emulate this visitor, had to track vertices, not ideal. But when I add the template function to my Visitor class, the code is never hit. Specifically, I'm using Visual Studio 2013 and the compiler is telling me my debug breakpoint will never get hit in the function as the code did not make it into the executable. The visitor class is below, any thoughts on what I'm doing wrong? I took a look at undirected_dfs.hpp and it includes call_finish_edge() in the DFS algorithm in undir_dfv_impl(). Thanks, Michael class BaseVisitor : public boost::dfs_visitor<> { public: template <class E, class G> void examine_edge(E e, const G& g) { // gets hit... } template <class V, class G> void discover_vertex(V v, const G& g) { // gets hit... } template <class V, class G> void finish_vertex(V v, const G& g) { // gets hit... } template <class E, class G> void finish_edge(const E& e, const G& g) { // NOT built or hit... // Tried using [E e] param as well... } };

1 0

Peer Review Report for proposed Boost.TypeIndex v2.1 Nov 12th – 21st 2013
by Niall Douglas 24 Nov '13

24 Nov '13

Please let me know as soon as possible any errata, missing credits etc. Niall Boost Peer Review Report for proposed Boost.TypeIndex v2.1 Nov 12th – 21st 2013 This report is the first edition, dated Sunday 24th November 2013. The review manager was Niall Douglas http://www.nedprod.com/. Source: https://github.com/apolukhin/type_index/zipball/master Documentation: http://apolukhin.github.com/type_index/index.html Peer review discussion detail: http://boost.2283326.n4.nabble.com/TypeIndex-Peer-review-period-for-library… My thanks to the Boost members whose peer review makes up this report: Robert Ramey, Vicente J. Botet Escriba, Gavin Lambert, Andrey Semashev, Steven Watanabe, pfultz2, Mathieu Champlon, Joël Lamotte Klaim, Rob Stewart, Jan Herrmann, Tony Van Eerd. Contents: · Summary of consensus from peer review ......................................................................................................... 1 · My recommendation to the library author and the Review Wizards ................................................................ 3 Summary of consensus from peer review: The consensus feedback was to accept TypeIndex after substantial modifications. There were two recommendations of rejection due to how substantial such modifications would need to be (i.e. a request for a second round of peer review with a new implementation). Note that my personal opinion based on post-review reflection is written in [square bracketed italics]. · Many seemed to feel that a boost::type_info’s member function API, where identically named to that of std::type_info member function API, ought to have identical compile-time effects. This implied that missing member function APIs, or other compile time errors for missing or incomplete functionality, would be okay but if name() returns some const char *, then any const char * so long as it meets the C++ standard is okay. [I think there are three use cases for a type_info like substitute: (i) as a lightest possible weight, non-RTTI requiring minimal type_info which can have any API it likes and ought to not be directly substitutable for std::type_info or std::type_index (ii) as a compile-time substitute for std::type_info in that it will compile without third party code modification, but may not produce reliable code due to not returning exactly the same values as std::type_info (iii) as a runtime substitute for std::type_info in that it will require code to be “ported” to it due to having a breaking API, but thereafter produces reliable code. I’ll be very blunt in saying that (ii) is a bad idea in my opinion, and (iii) is valuable but out of scope enhancement which could be added as a separate class after peer review. In my opinion, (i) is where we ought to focus, and I would recommend that the lightest possible weight type_info replacement be deliberately compile-time incompatible with std::type_info (where output is not identical to std::type_info) to force porting code to it so authors are not lazy.] · A large minority seemed to feel that a boost::type_info’s member function API, where identically named to that of std::type_info member function API, ought to have identical run-time outcomes. Most specifically, this would mean that member functions e.g. name() would return exactly what std::type_info’s name() does, even if for example name() returns a std::string instead of a const char * as would be necessary in pre-C++11 compilers. [This is really use case (iii) in the previous item.] · It was mentioned that it should be possible to optionally specialise std::hash<> for type_info for optional seamless use in hash taking containers. · Some felt that implementation-specific std::type_info quirks ought to be replicated. Others felt they should not, and a portable interface which works identically on all platforms is preferred. [This is really use case (iii) in the previous item.] · boost::type_info is currently initialised via a static cast from a std::type_info when RTTI is available. This is undefined behaviour, and some felt this to be a showstopper. I (Niall Douglas) looked into this more deeply due to its seriousness, and found that because most STL implementations define std::type_info with a virtual function table, the undefined behaviour static cast would cause dynamic_cast on a boost::type_info instance to misoperate. [I believe the RTTI induced misoperation to indeed be a showstopper, and that this use of undefined behaviour to reduce code bloat is an unsafe optimisation. A much lighter weight non-direct-substitute for std::type_info ought to be as code bloat parsimonious as is possible, while its lack of non-explicit interoperation ability with std::type_info ought to allow avoidance of needing any UB tricks.] · Some felt that any use of implied boost::type_info ought to be explicitly written as boost::type_info instead of relying on namespace lookup, as the name similarity to std::type_info may introduce confusion. [I agree] · It was mentioned that some function-local static data members are initialised in a thread unsafe way. [For information I have to hand a very lightweight BOOST_BEGIN_MEMORY_TRANSACTION() implementation ideal for this purpose. We could submit it to Boost.Detail and then everyone could use it?] · Magic macros such as __PRETTY_FUNCTION__ ought to not be referenced outside of a function as they don’t technically exist there. Checks for their existence ought to be within a function. · It was requested that a boost::type_id<> which takes some unknown variable instance as a parameter and therefore allows the compiler to deduce the type of the variable as the boost::type_index<T> type would be valuable. · A mechanism for programming compile-time logic with class inheritance trees such that inheritance can be determined at compile-time with RTTI disabled was requested. My recommendation to the library author and the Review Wizards: · In my opinion Antony ought to make TypeIndex v3 quite literally a very lightweight container of some unknown, but known to be uniquely identifying for some type, static const char * string. I think its class type and its list of member functions ought to be deliberately compile-time incompatible with std::type_info to force authors to upgrade their code. A conversion member function ought to be able to synthesise a corresponding std::type_info using typeid() from some boost::type_index<T>, but that’s about it. I would even, personally speaking, go so far as to only provide a boost::type_index and no corresponding boost::type_info, especially if the boost::type_id<T>() function can return a const boost::type_index<T>& and therefore can be used as a static const lref, or copy constructed from it etc. A suggested name() member function replacement which correctly breaks out the multiple confounding uses of std::type_info::name() into each of their three use cases (and which intentionally causes any use of name() to fail to compile) might be: Text Box: /*! Returns a static const char string of unknown format uniquelyidentifying this type.The only guarantee is that this string will beunique to the type within this process lifetime. */const char *unique_name() const noexcept;/*! Returns a representation of this type suitable for printing.This call may take some time as its storage may not be cached. */std::string pretty_name() const;class enum mangling{Native, //!< Whatever the native mangling used by this toolset isMSVC, //!< The Microsoft C++ mangling formatItanium //!< The Itanium C++ mangling format};/*! Returns the mangled form of the string representation of the type.After the calculation the value is cached statically such that the c_str()function can be used to convert the returned string to a const char *format identical to what may be returned by std::type_info::name() (orraw_name() on MSVC).This function may throw an exception if it does notsupport mangled type string calculation, including when mangling=Native onsome Bear in mind that user code can always subclass boost::type_index and add their own name() implementation based on one or more of the above new member functions. · In other words, here I think “less is more” in every way you look at it. I think a slimmer less heavy TypeIndex would be a superior solution. · I request the Review Wizards to allow Antony some time to make the changes to produce a v3 of the library, and then to allow TypeIndex v3 a Fast Track Review of five days to ensure the Boost community is happy and that its feedback has been incorporated. It was asked during peer review that such a five day period please include a weekend. I would be happy to serve as review manager again if requested. Niall Douglas Waterloo, Canada, November 2013

1 0

[boost-TLS] Thread Local Storage (TLS) Question
by Kyle Ketterer 24 Nov '13

24 Nov '13

Hello, I am using multiple threads for I/O operations. The issue I am having is joining these threads on the main thread. It appears that calling join() on a thread with TLS pointers, it results in a hang. I have multiple thread specific pointers declared outside of the function and in the beginning of the method I call reset ( new std::string ) ....etc etc. I also am acquiring some resource handlers as Im using a boost::thread_specific_ptr < ifstream > infile So, when I create the thread in the main thread and join() it I get a hang. The only thing I can think of is that the handlers are not being released so join() waits indefinitely. I read in the documentation that the pointers should be cleaned up on thread exit - but the thread apparently never exits because then resources are not released? I understand that it may not be "conventional" to use a tls pointer for ifstream but I find it a lot better than locking with mutexes. Also, I'm not sure if there are limits as to how many TLS pointers you can actually use but I am currently using about 10 for one thread method. Another thing to note is that when calling detach() on the thread, all of the threads execute properly and I get expected output. However, I need to call join() every x amount of threads due to OS limitations of how many threads can actually be created. I need to read about 5000 files so obviously I can't create 5000 threads as Windows maxes out at 700 I believe. I am reading files off of a RAID setup so I believe this is a situation that can benefit from multiple threads reading files. Basically, I only want to create 4 threads at a time, then join() the previous 4, ensure that they have all completed successfully and continue to create more. Any suggestions or comments on this issue? Thanks -- Kyle Ketterer <reminisc3(a)gmail.com>

3 3

Boost 1.55 and ICL : Compile error
by Adam Baxter 24 Nov '13

24 Nov '13

Hello all, I'm getting a compile error under Boost 1.55 using ICL's Closed Interval include: In file included from /home/abaxter/Projects/Du/apollo/libapollo/src/theory.cpp:21:0: /home/abaxter/local/include/boost/icl/closed_interval.hpp: In constructor 'boost::icl::closed_interval<DomainT, Compare>::closed_interval()': /home/abaxter/local/include/boost/icl/closed_interval.hpp:35:31: error: 'DefaultConstructibleConcept' was not declared in this scope BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:35:66: error: expected primary-expression before '>' token BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:35:67: error: expected primary-expression before ')' token BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:35:68: error: there are no arguments to 'BOOST_CONCEPT_ASSERT' that depend on a template parameter, so a declaration of 'BOOST_CONCEPT_ASSERT' must be available [-fpermissive] BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:35:68: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated) /home/abaxter/local/include/boost/icl/closed_interval.hpp:36:31: error: 'LessThanComparableConcept' was not declared in this scope BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:36:64: error: expected primary-expression before '>' token BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:36:65: error: expected primary-expression before ')' token BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:36:66: error: there are no arguments to 'BOOST_CONCEPT_ASSERT' that depend on a template parameter, so a declaration of 'BOOST_CONCEPT_ASSERT' must be available [-fpermissive] BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp: In constructor 'boost::icl::closed_interval<DomainT, Compare>::closed_interval(const DomainT&)': /home/abaxter/local/include/boost/icl/closed_interval.hpp:46:31: error: 'DefaultConstructibleConcept' was not declared in this scope BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:46:66: error: expected primary-expression before '>' token BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:46:67: error: expected primary-expression before ')' token BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:46:68: error: there are no arguments to 'BOOST_CONCEPT_ASSERT' that depend on a template parameter, so a declaration of 'BOOST_CONCEPT_ASSERT' must be available [-fpermissive] BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:47:31: error: 'LessThanComparableConcept' was not declared in this scope BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:47:64: error: expected primary-expression before '>' token BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:47:65: error: expected primary-expression before ')' token BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:47:66: error: there are no arguments to 'BOOST_CONCEPT_ASSERT' that depend on a template parameter, so a declaration of 'BOOST_CONCEPT_ASSERT' must be available [-fpermissive] BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp: In constructor 'boost::icl::closed_interval<DomainT, Compare>::closed_interval(const DomainT&, const DomainT&)': /home/abaxter/local/include/boost/icl/closed_interval.hpp:55:31: error: 'DefaultConstructibleConcept' was not declared in this scope BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:55:66: error: expected primary-expression before '>' token BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:55:67: error: expected primary-expression before ')' token BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:55:68: error: there are no arguments to 'BOOST_CONCEPT_ASSERT' that depend on a template parameter, so a declaration of 'BOOST_CONCEPT_ASSERT' must be available [-fpermissive] BOOST_CONCEPT_ASSERT((DefaultConstructibleConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:56:31: error: 'LessThanComparableConcept' was not declared in this scope BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:56:64: error: expected primary-expression before '>' token BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:56:65: error: expected primary-expression before ')' token BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ /home/abaxter/local/include/boost/icl/closed_interval.hpp:56:66: error: there are no arguments to 'BOOST_CONCEPT_ASSERT' that depend on a template parameter, so a declaration of 'BOOST_CONCEPT_ASSERT' must be available [-fpermissive] BOOST_CONCEPT_ASSERT((LessThanComparableConcept<DomainT>)); ^ make[2]: *** [libapollo/src/CMakeFiles/libapollo.dir/theory.cpp.o] Error 1 make[1]: *** [libapollo/src/CMakeFiles/libapollo.dir/all] Error 2 make: *** [all] Error 2 15:18:23: The process "/usr/bin/make" exited with code 2. Any ideas? Adam

1 0

[Thread] TLS / locking ?
by beet 24 Nov '13

24 Nov '13

Hi there, I have a number of threads and, within the context of each thread, a large number of objects may be active. I would now like to provide all objects accessed by a thread with a common random number generator. i.e., there would be as many random number generators as there are threads, and all objects active inside of a given thread would access the same generator, but objects in different threads use different generators. The obvious approach would be to store the generator in thread-local storage. I am concerned, however, about the performance implications. In particular, does access to thread-local storage implicitly involve locking of sorts? If so, the (very) frequent access to the random number generator would effectively serialize my application. Thanks and Best Regards, Beet

3 3

Design query using Boost.
by Rahul Mathur 24 Nov '13

24 Nov '13

All, I have a design sinerio. I have different struct (C structures) having different data's but NO similarities between struct and each struct does different operations. The struct for example are - struct Apple { int A; char B; long C; double d; .. ..}; struct Orange { char A; int B; unsigned int C; long d; .. }; and maybe few more. Above few struct data members have dynamic data and other members have fixed/hardcoded datas. The complete struct is send as a buffer to a remote machine through native send()/read() API calls which has been successfully implemented. Please note this data as tested were hard coded or completely static but didn't had combination of dynamic/real and static data.. Now such operations (viz different or repeated) with ONE/MULTIPLE SET of data could be many as 1000, I wish now to send complete operations to remote machine, get a ACK from it and work on this struct data with modification/cancellation/reject/etc operations. One way could be to work with something similar - struct Apple { ... ..}; vector <Apple> data; data.insert (begin();end()) --- But, I have few questions - 1. I can have "std::map<string, vector>" and send this data as native send(). Latter read/recv() with string. Am I correct as I would have multiple operations? 2. I do wish to maintain synchronisation using Boost::lockfree mechanism latter? 3. Any other techniques? Thanks.

1 0

[log] Why aren't logger operations const ?
by Mauricio Carneiro 24 Nov '13

24 Nov '13

I am trying to use a severity channel logger but I hit the problem with BOOST_LOG_SEV not being a const method -- I'm thinking because of both open_record() and push_record() This will basically force me to make all methods in my classes not const because they want to write out to their loggers. I can't really afford to do that -- so I'm restricted to global loggers at the moment. In my current implementation, each class has a logger with the class name as the channel (initialized in their constructors), and it issues log messages at any point with BOOST_LOG_SEV(this->logger, level) I'd love to hear the reason behind the non-constness and if my design is not the intended for Boost::Log. Thank you for your help. Mauricio Carneiro, Ph.D. http://www.broadinstitute.org/~carneiro/

2 4

Re: [Boost-users] New-style for on an iterator-range of filter_iterator of strings crashes/hangs
by Ami Tavory 24 Nov '13

24 Nov '13

Steven Watanabe: > AMDG > > On 11/23/2013 11:12 AM, Ami Tavory wrote: > > <snip> > > typedef > > filter_iterator<function<bool (const string &)>, > > vector<string>::const_iterator> > > filter_it_t; > > auto r = make_iterator_range(filter_it_t(fn, ss.begin()), > > filter_it_t(fn, ss.end())); > > <snip> > > > > yields an executable that crashes with > > {{{ > > Segmentation fault (core dumped) > > }}} > > > > <snip> > > > > You're not constructing the filter_iterators correctly. > From the documentation: > > filter_iterator(Predicate f, Iterator x, Iterator end = Iterator()); > > Effects: > > Constructs a filter_iterator where m_iter is either > the first position in the range [x,end) such that > f(*m_iter) == true or else``m_iter == end``. The > member m_pred is constructed from f and m_end from end. > > You need to pass the end iterator as well. (Or use > the Boost.Range version) > > In Christ, > Steven Watanabe Many thanks!

1 0

New-style for on an iterator-range of filter_iterator of strings crashes/hangs
by Ami Tavory 23 Nov '13

23 Nov '13

Hello, Using g++ 4.8.1 (g++ (Ubuntu/Linaro 4.8.1-10ubuntu8) 4.8.1) with boost 1.5.3, building the code below with {{{ g++ -o example/filter.out -std=c++0x -Wall -g -rdynamic -I/usr/include/boost example/filter.cpp }}} {{{ #include <vector> #include <string> #include <iostream> #include <functional> #include <boost/iterator/filter_iterator.hpp> #include <boost/range/iterator_range.hpp> using namespace std; using namespace boost; int main() { vector<string> ss{"hello", "world"}; // function<bool (const string &)> fn = [](const string &s){return false;}; function<bool (const string &)> fn = [](const string &s){return s.size() > 3;}; cout << fn("Hello") << endl; // (1) cout << fn("world") << endl; // (2) typedef filter_iterator<function<bool (const string &)>, vector<string>::const_iterator> filter_it_t; auto r = make_iterator_range(filter_it_t(fn, ss.begin()), filter_it_t(fn, ss.end())); for(const string &a: r) cout << a << endl; return 0; } }}} yields an executable that crashes with {{{ Segmentation fault (core dumped) }}} Exchanging the comment in the two lines {{{ // function<bool (const string &)> fn = [](const string &s){return false;}; function<bool (const string &)> fn = [](const string &s){return s.size() > 3;}; }}} (so that the first lambda is used) yields an executable that hangs. In either case, the application first prints the results of the lines marked (1) and (2). Can't figure out what I'm doing wrong, and would appreciate advice. Thanks, Ami

2 1

self_loop=false for Unique R-MAT generator
by Николай Кинаш 23 Nov '13

23 Nov '13

>The R-MAT graph model is different from the BA model; are you sure you >want R-MAT? Hmm.... I`m not sure. How to create BA model in BPGL? Thanks.

2 1

Re: [Boost-users] [boost] Subversion repository closing. Conversion to Git imminent.
by Beman Dawes 22 Nov '13

22 Nov '13

On Fri, Nov 22, 2013 at 6:09 PM, Edward Diener <eldiener(a)tropicsoft.com>wrote: > On 11/22/2013 11:52 AM, Beman Dawes wrote:... > >> >> Please make no svn commits after that time. We will be adding a pre-commit >> hook that prevents commits, but please do not wait for that becomes >> active. >> >> After svn is closed, the conversion will be run one last time, and then >> turned off. Then there is a week set aside for final validity checks, >> testing, and general scurrying around. When that is done, the boostorg >> repo >> on GitHub will open for business. If everything goes smoothly, it may take >> less than a week but if there are glitches it may take longer. >> > > Can the boostorg repo on GitHub be pulled from at any time during that > week or is the idea to wait until everything has been verified first. > The boostorg repos, both super-project and individual libraries, can be cloned and that might be useful for some limited testing. For example, creating a private branch "experiments" and making some trial changes and commits. But there is still a risk that any changes pushed up to the GitHub boostpro public repo will get overwritten. This would happen if we decide to rerun the conversion one last time to fix some showstopper that surfaces during testing. So other than throw-away experiments, best bet is to relax, and don't depend on the GitHub public repos until we post a message saying we are totally live. Useful questions, Thanks! --Beman

1 0

[Geometry] Finding polygon self-intersections efficiently
by Rob Conde 22 Nov '13

22 Nov '13

Given a possibly self-intersecting polygon, I'm trying to find the self-intersecting segments of the polygon. I can do this naively of course using Segment and intersects, but I'd like to know if there's a more efficient suggested approach in Boost.Geometry...I'm having a hard time finding anything from the documentation. Thanks, Rob Conde

1 0

Re: [Boost-users] [Boost-docs] [boost] Improving Documentation
by Paul A. Bristow 22 Nov '13

22 Nov '13

> -----Original Message----- > From: Boost-docs [mailto:boost-docs-bounces@lists.boost.org] On Behalf Of Paul A. Bristow > Sent: Wednesday, November 20, 2013 12:09 PM > To: Discussion of Boost Documentation > Subject: [Boost-docs] FW: [boost] Improving Documentation I've had yet another go at Robert Ramey's challenge to document his to-be-proposed Safe Integers library You can see the results of my most recent efforts (now only for users) at https://dl.dropboxusercontent.com/u/43940943/safe_numerics/libs/safe_numeri… and as a single pdf file https://dl.dropboxusercontent.com/u/43940943/safe_numerics/libs/safe_numeri… Apart from the effort involved in providing Doxygen comments (which I believe is small, especially during writing the code, because there is lots of boiler plating possible), our main differences of view are on how to provide the 'concepts' information. The only true concepts used by this library (at present) are the ubiquitous assignable and copyconstructable. For the more common concepts, I have used a simple link to the concept like http://www.sgi.com/tech/stl/Assignable.html because the library is not using Boost.Concept (yet). (There is also a concept of a Numeric type but this is not enforced by the use of the library, although it can be tested using file https://dl.dropboxusercontent.com/u/43940943/safe_numerics/boost/safe_numer… provided). The information on type Numeric in this file is documented in my Doxygenated version here: https://dl.dropboxusercontent.com/u/43940943/safe_numerics/libs/safe_numeri… Robert has contrasted his presentation of concepts (and other information) thus http://htmlpreview.github.io/?https://raw.github.com/robertramey/safe_numer… doc/html/index.html with mine. I believe that it contains the same information (about Numeric) and can be found by using the automatically produced Index - see https://dl.dropboxusercontent.com/u/43940943/safe_numerics/libs/safe_numeri… l The other information about operators can also be found using the index, for example, operator>= see https://dl.dropboxusercontent.com/u/43940943/safe_numerics/libs/safe_numeri… /safe_compare/greater_than_equal.html The difference is that Robert provides a simple list, whereas I provide an index to individual operators (not all are currently documented - retrofitting is tedious!). IMO the user will find the index method easier (when that is the users' expectation). With a tiny library like this (chosen as a demo because it is small) it may be easy to find the concepts section, but for a typical much larger library making the table and finding it will be less attractive. The size of the documentation is much, much bigger, but it is more likely to be complete, and more likely to be accurate, (and nearly all will be unread so its repetitions unimportant). A typical example of what the user is likely to read is about the key template 'safe': https://dl.dropboxusercontent.com/u/43940943/safe_numerics/libs/safe_numeri… /safe.html You will note how this references concepts DefaultConstructible,... If Concepts get into the C++ language, or Boost.Concept is used, or the method using by Boost.GIL - see http://www.boost.org/doc/libs/1_55_0/libs/gil/doc/html/g_i_l_0286.html I believe we could make this fairly automatic, but I think the library must do this as it is conceived. Views welcome. Paul PS A more typical library with Doxygen comments in the C++ reference section is at https://dl.dropboxusercontent.com/u/43940943/circular_buffer/libs/circular_… l showing the info about circular buffer, for example at https://dl.dropboxusercontent.com/u/43940943/circular_buffer/libs/circular_… cular_buffer.html --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

1 0

Re: [Boost-users] [BGL] visitors.hpp:138: error: no type named 'event_filter' in 'class dijkstra_custom_visitor'
by The Maschine 22 Nov '13

22 Nov '13

Well Jeremiah, My email and the assumptions are completely wrong. Im sorry. just forget about it, next time Ill have my coffee before debuting code :) thanks

1 0

Subversion repository closing. Conversion to Git imminent.
by Beman Dawes 22 Nov '13

22 Nov '13

The Boost Steering Committee has given the final approval for the conversion from Subversion to Git, including the modularization of Boost library repositories. The Subversion repository will be closed for all changes to all branches, including the sandbox, Sunday, November 23 2013, 00:00 hours UTC. That's 8 PM Saturday, US East Coast time, and 5 PM US West Coast time. Please make no svn commits after that time. We will be adding a pre-commit hook that prevents commits, but please do not wait for that becomes active. After svn is closed, the conversion will be run one last time, and then turned off. Then there is a week set aside for final validity checks, testing, and general scurrying around. When that is done, the boostorg repo on GitHub will open for business. If everything goes smoothly, it may take less than a week but if there are glitches it may take longer. --Beman

1 0

self_loop=false for Unique R-MAT generator
by Николай Кинаш 22 Nov '13

22 Nov '13

Hi. I use Parallel Boost Graph Library to create network Barabási–Albert (BA) model int main(int argc, char* argv[]) { boost::mpi::environment env(argc, argv); boost::minstd_rand gen; Graph g(RMATGen(gen, 100, 400, 0.3, 0.1, 0.2, 0.03), RMATGen(), 100); write_graphviz(std::cout, g); } This graph always have self-loops vertex. How i can to forbid self_loop for Unique R-MAT generator ?

2 1

Re: [Boost-users] [BGL] visitors.hpp:138: error: no type named 'event_filter' in 'class dijkstra_custom_visitor'
by The Maschine 22 Nov '13

22 Nov '13

Hi, My code is very simple so I suspect I missing something about the real 'examine_vertex' meaning. One example with the custom visitor and one without that produces the correct results out site the 'search' (I;d like to be able to do it with a visitor though for later steps) Simplified to just the essentials. #### With VISITOR #### IndexMap indexMap = boost::get(boost::vertex_index, m_ugraph); PredecessorMap predecessorMap(&predecessors[0], indexMap); DistanceMap distanceMap(&distances[0], indexMap); glm::dvec3 s_mid = m_ugraph[*vertex_iterator_begin].m_mid_point; double thres = 500.0f; dijkstra_threshold vis(s_mid,thres); try { boost::dijkstra_shortest_paths(m_ugraph, *vertex_iterator_begin, boost::predecessor_map(predecessorMap).distance_map(distanceMap).visitor(vis)); } catch (...) { } int total_node_count2 = 0; double total_depth2 = 0.0; for (boost::tie(vi, vi_end) = boost::vertices(m_ugraph); vi != vi_end; ++vi) { if( (double(distances[*vi])*1.1) >= std::numeric_limits<double>::max() || (std::isnan(distances[*vi])) || !(std::isfinite(distances[*vi])) ) { } else { total_depth2 += double(distances[*vi]); total_node_count2 += 1; } } #### To the total distances and the number of nodes within the radius is not correct… #### Without a visitor outside dijkstra_shortest_paths #### try { boost::dijkstra_shortest_paths(m_ugraph, *vertex_iterator_begin, boost::predecessor_map(predecessorMap).distance_map(distanceMap)); } catch (...) { } int total_node_count2 = 0; double total_depth2 = 0.0; for (boost::tie(vi, vi_end) = boost::vertices(m_ugraph); vi != vi_end; ++vi) { if( (double(distances[*vi])*1.1) >= std::numeric_limits<double>::max() || (std::isnan(distances[*vi])) || !(std::isfinite(distances[*vi])) ) { } else { if( thres > 0.0f && glm::distance(s_mid, m_ugraph[*vi].m_mid_point) < thres ) { total_depth2 += double(distances[*vi]); total_node_count2 += 1; } } ### This give you the correct results but you searched the full graph. Any ideas? Thanks

2 1

Visitor pattern with functor front end
by Daniele Barzotti 22 Nov '13

22 Nov '13

Hi, maybe this will be a trivial question but I'm quite new to MSM. If I would to use the visitor pattern, how can I define it using the functor front-end? Regards, Daniele.

1 1

Boost.log file rotation current file name
by Daniel Krikun 22 Nov '13

22 Nov '13

Hello, I use some log viewer tool to display and filter logs. In log4j there is a feature that allows for the current logfile to have some constant name, e.g 'current.log', and only after it is finalized it is renamed to its name (probably having some timestamp/counter) in it. This feature makes it most convenient with log viewers. Is it possible to achieve this with Boost.Log? If not I would like to suggest it as a feature request. Regards,

1 0

Fwd: Boost.log file collector
by Daniel Krikun 22 Nov '13

22 Nov '13

Hello, When I set up text_file_backend with file rotation and a file collector with the target directory other from the directory where my application resides, then if the application crashes, the current log file will not be collected to the target directory. This is somewhat inconvenient, because, let's say we setup the file collector to collect all the log files under 'logs' subfolder, and then if the application crashes we ask the user to simply e-mail the 'logs' folder to see what possibly went wrong before the crash, but, alas, the most interesting piece is missing. Is there a way to work around the problem? Thanks,

1 0

[multiprecision] Empty intervals and intervals with NaN check
by Александров Петр 21 Nov '13

21 Nov '13

Hello. In MPFI documentation it is said that "MPFI functions operate on valid intervals ..., their behavior with non-valid intervals as input is undefined". Are intervals checked in Boost Multiprecision library whether they are invalid? Can this be easily done using Boost? Kind regards, Petr.

2 3

Problem with variadic BOOST_PP_TUPLE_REM in Clang
by Jeremiah Willcock 21 Nov '13

21 Nov '13

When using Clang version "Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)" in C++11 mode, the code: #include <boost/preprocessor.hpp> BOOST_PP_TUPLE_REM()(foo(bar, baz) const) is not expanded correctly. The second line expands to: BOOST_PP_TUPLE_REM_(foo(bar, baz) const) while on GCC 4.9, it expands to: foo(bar, baz) const Is there a known issue with this macro on Clang? -- Jeremiah Willcock

6 12

Re: [Boost-users] [BGL] visitors.hpp:138: error: no type named 'event_filter' in 'class dijkstra_custom_visitor'
by The Maschine 21 Nov '13

21 Nov '13

Thanks a lot for that. Problem solved, in terms of the function call. What remains is that my custom visitor is not behaving as I thought** it would! What I wanted to implement (which partially is based on an older thread that you replied) is cut-off radius around the source. The problem with my version of visitor is that it dies when it 'examines' the first vertex outside the radius, but this doesnt imply that everything within radium is correctly found (correct distances etc). Any tips about this? Thanks a lot

2 1

[BGL] visitors.hpp:138: error: no type named 'event_filter' in 'class dijkstra_custom_visitor'
by The Maschine 21 Nov '13

21 Nov '13

Hi, Im trying to use a custom visitor but I get this error. My custom visitor is: class dijkstra_custom_visitor : public boost::default_dijkstra_visitor { public: dijkstra_threshold(glm::dvec3 source, double threshold): s(source), threshold(threshold) {} struct hit_threshold {}; void examine_vertex(boost::graph_traits <unGraph>::vertex_descriptor v, const unGraph& g) { glm::dvec3 dest = boost::get(&VertexProperties::m_mid_point, g, v); if( glm::distance(s,dest) > threshold ) throw hit_threshold(); } double threshold; glm::dvec3 s; }; My 'calling' line is: std::vector<Vertex> predecessors(boost::num_vertices(m_ugraph)); std::vector<Weight> distances(boost::num_vertices(m_ugraph), std::numeric_limits<double>::max() ); IndexMap indexMap = boost::get(boost::vertex_index, m_ugraph); PredecessorMap predecessorMap(&predecessors[0], indexMap); DistanceMap distanceMap(&distances[0], indexMap); glm::dvec3 s_mid = m_ugraph[*vertex_iterator_begin].m_mid_point; double thres = 500.0f; boost::dijkstra_shortest_paths(m_ugraph, *vertex_iterator_begin, boost::predecessor_map(predecessorMap).distance_map(distanceMap).visitor(boost::make_dijkstra_visitor(dijkstra_custom_visitor(s_mid,thres)))); What do you think is the problem? thanks

2 1

TypeTraits like library for inheritance access specifiers?
by Mostafa 21 Nov '13

21 Nov '13

Is there a TypeTraits like library for determining inheritance access specificers? Something like a is_private_base_of? Thanks, Mostafa

1 0

linking with boost log 1.54
by Ovanes Markarian 20 Nov '13

20 Nov '13

Hi *, I am stuck with a problem to link on linux (ubuntu 12.04) with a boost log library (clang 3.0 & libstdc++). No matter what I do it fails. The problem is: I have a 3rd party library which is delivered as an .so-module and I need to link with it. My project is organized so that we develop static libraries and link them with test or application runner executables. I currently build boost as static libraries only, after I link my project with log library I get tons of errors like: /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libpthread.a(nptl-init.o): In function `__pthread_initialize_minimal_internal': /build/buildd/eglibc-2.15/nptl/nptl-init.c:296: undefined reference to `__libc_setup_tls' /build/buildd/eglibc-2.15/nptl/nptl-init.c:314: undefined reference to `_dl_cpuclock_offset' /build/buildd/eglibc-2.15/nptl/nptl-init.c:430: undefined reference to `_dl_pagesize' /build/buildd/eglibc-2.15/nptl/nptl-init.c:456: undefined reference to `_dl_init_static_tls' /build/buildd/eglibc-2.15/nptl/nptl-init.c:458: undefined reference to `_dl_wait_lookup_done' /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libpthread.a(nptl-init.o): In function `__pthread_get_minstack': /build/buildd/eglibc-2.15/nptl/nptl-init.c:479: undefined reference to `_dl_pagesize' /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libpthread.a(pthread_create.o): In function `allocate_stack': /build/buildd/eglibc-2.15/nptl/allocatestack.c:457: undefined reference to `_dl_stack_flags' /build/buildd/eglibc-2.15/nptl/allocatestack.c:596: undefined reference to `_dl_stack_flags' /usr/local/lib/libboost_log-mt-s.a(text_file_backend.o): In function `boost::log::v2s_mt_posix::sinks::anonymous::file_collector::file_collector(boost::shared_ptr<boost::log::v2s_mt_posix::sinks::anonymous::file_collector_repository> const&, boost::filesystem::path const&, unsigned long, unsigned long)': libs/log/src/text_file_backend.cpp:(.text+0x60b): undefined reference to `boost::filesystem::detail::current_path(boost::system::error_code*)' libs/log/src/text_file_backend.cpp:(.text+0x65c): undefined reference to `boost::filesystem::absolute(boost::filesystem::path const&, boost::filesystem::path const&)' libs/log/src/text_file_backend.cpp:(.text+0x6b1): undefined reference to `boost::filesystem::detail::create_directories(boost::filesystem::path const&, boost::system::error_code*)' And so on. Do you have any hints or suggestions? Thanks, Ovanes

4 7

[String_Ref] Working with other parts of boost
by Norbert Wenzel 20 Nov '13

20 Nov '13

Hi, I wanted to play around with Boost.String_Ref and found some old code that I thought would be the ideal case for string_refs. It's basically a config file reader that stores the whole line and also a key/value pair that may be found in that line. So a single line looked something like this: std::string line; //original line as is in the file boost::string_ref key; //extracted key subpart boost::string_ref value; //extracted value subpart But when I wanted to trim the string_refs (eg. for lexical_casting them) I got compile errors, because boost::trim uses erase, which of course is not supported by string_ref. But string_ref has the remove_prefix/suffix member functions, which would be exactly what trim needs. So I quickly hacked an additional overload of trim_*_if that calls the remove_*fix instead of the .erase() member function and it seemed to work. The second problem occurred when I tried to extract my key/value pair from a line using the Tokenizer, which seems to be old, but it still works for simple cases. Tokenizer internally uses assign() to fill an internal buffer with the next token, which of course is no member function of string_ref. Since it seems Tokenizer only uses the assign version that takes two iterators it might be possible to add such an assign() function to string_ref. At least I added one as a testcase locally and it worked in my limited testcase. Are there any plans to add either trim() or Tokenizer support for string_ref? I'm not sure about the Tokenizer/assign stuff, since one would have to change string_ref but I really think the trim() support would be helpful. Anyway, these issues kept me from actually using string_ref, since the code did not compile (or required changes to boost headers in order to compile). And I did not want to redo some of the boost string algorithm stuff in order to use string_refs. Norbert

4 9

[Asio] Issues with kqueue_reactor, dynamic libraries and -fvisibility=hidden
by Andrei Bica 19 Nov '13

19 Nov '13

I'm having a problem with a larger project for MacOS which uses multiple dynamic libraries and asio features (deadline_timers and tcp/udp scokets). I've managed to reproduce my problem in the following minimal example: ////////// Timer.hpp ////////// #ifndef TIMER_HPP #define TIMER_HPP #include <boost/asio.hpp> #include <boost/thread.hpp> #define VISIBLE __attribute__ ((visibility ("default"))) class VISIBLE Timer { public: Timer(boost::asio::io_service& service); private: void onTimeout(const boost::system::error_code& code); boost::asio::deadline_timer timer; }; #endif // Timer_HPP ////////// Timer.cpp ////////// #include <Timer.hpp> Timer::Timer(boost::asio::io_service& service) : timer(service) { timer.expires_from_now(boost::posix_time::seconds(1)); timer.async_wait(boost::bind(&Timer::onTimeout, this, _1)); } void Timer::onTimeout(const boost::system::error_code& code) { std::cout << "The callback from the dynamic library was called." << std::endl; } ////////// main.cpp ////////// #include <Timer.hpp> boost::asio::io_service service; void run() { service.run(); } void onTimeout(const boost::system::error_code& code) { std::cout << "The callback from main was called." << std::endl; } int main() { Timer timer(service); boost::asio::deadline_timer deadline_timer(service); deadline_timer.expires_from_now(boost::posix_time::seconds(1)); deadline_timer.async_wait(boost::bind(&onTimeout, _1)); boost::thread t(boost::bind(&run)); t.join(); return 0; } Timer.cpp is compiled into a dynamic library and used by main.cpp which is compiled as an executable. The environment: MacOS 10.8.5, Boost 1.54.0, clang 500.2.79 The parameters which are passed to clang at compilation time are: clang++ -ggdb -c Timer.cpp -I. -I/opt/local/include -fPIC -fvisibility=hidden clang++ -ggdb -o libTimer.dylib -dynamiclib Timer.o -L/opt/local/lib -lboost_thread-mt -lboost_system-mt -fvisibility=hidden clang++ -ggdb main.cpp -o runTest -I. -I/opt/local/include -L. -L/opt/local/lib -lboost_thread-mt -lboost_system-mt -lTimer fvisibility=hidden As you can see the visibility is set to hidden at compilation time in order to expose only desired functions (e.g. the Timer class) from my library. The problem that arise is that the callback of the timer from main.cpp is never called. If I remove the visibility flag at compilation time the example works as it should (both timer callbacks are called). When I did further investigations I've observed that 2 kqueue_reactor instances are create when using hidden visibility and only one kqueue_reactor is created when visibility is set to default. I need an advise on how should I proceed so that I can still use the visibility set to hidden at compilation time but have the example working as expected. When compiling the example on Linux using visibility set to hidden the example works as expected. Regards, Andrei

1 0

Compiling Boost 1.55.0 with Intel 14.0.1 and libstdc++ from GCC 4.8.1
by Maxime Boissonneault 19 Nov '13

19 Nov '13

Hi, I am attempting to build Boost 1.55.0 with Intel compiler 14.0.1, using the Standard C++ Library provided by GCC 4.8.1 I am having a lot of errors with "fenv". Here is a subset of those errors, with one particular object that is being built by the build script. The offending command line is "icpc" -c -xc++ -w1 -inline-level=2 -O3 -ip -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_BUILDING_THE_LIB=1 -DBOOST_LOG_DLL -DBOOST_LOG_NO_THREADS -DBOOST_LOG_USE_AVX2 -DBOOST_LOG_USE_NATIVE_SYSLOG -DBOOST_LOG_USE_SSSE3 -DBOOST_LOG_WITHOUT_EVENT_LOG -DBOOST_SPIRIT_USE_PHOENIX_V3=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_DONT_USE_CHRONO=1 -DDATE_TIME_INLINE -DNDEBUG -I"." -c -o "bin.v2/libs/log/build/intel-linux/release/log-api-unix/named_scope_format_parser.o" "libs/log/src/named_scope_format_parser.cpp" Errors are such as : In file included from ./boost/math/tools/promotion.hpp(26), from ./boost/math/special_functions/detail/round_fwd.hpp(12), from ./boost/math/special_functions/math_fwd.hpp(26), from ./boost/math/special_functions/fpclassify.hpp(19), from ./boost/spirit/home/support/detail/sign.hpp(22), from ./boost/spirit/home/karma/numeric/detail/numeric_utils.hpp(22), from ./boost/spirit/home/karma/numeric/uint.hpp(33), from ./boost/spirit/include/karma_uint.hpp(16), from libs/log/src/named_scope_format_parser.cpp(22): ./boost/math/tools/config.hpp(309): error: identifier "fexcept_t" is undefined fexcept_t m_flags; ^ In file included from ./boost/math/tools/promotion.hpp(26), from ./boost/math/special_functions/detail/round_fwd.hpp(12), from ./boost/math/special_functions/math_fwd.hpp(26), from ./boost/math/special_functions/fpclassify.hpp(19), from ./boost/spirit/home/support/detail/sign.hpp(22), from ./boost/spirit/home/karma/numeric/detail/numeric_utils.hpp(22), from ./boost/spirit/home/karma/numeric/uint.hpp(33), from ./boost/spirit/include/karma_uint.hpp(16), from libs/log/src/named_scope_format_parser.cpp(22): ./boost/math/tools/config.hpp(301): error: identifier "FE_INVALID" is undefined fegetexceptflag(&m_flags, FE_ALL_EXCEPT); I have the following set export CPLUS_INCLUDE_PATH=/software6/compilers/gcc/4.8.1/include/c++/4.8.1/ if I unset CPLUS_INCLUDE_PATH, this specific object compiles fine (with warnings, but no error). Does anyone have an idea of weither this is a bug with Intel compiler or with Boost ? Best regards, -- --------------------------------- Maxime Boissonneault Analyste de calcul - Calcul Québec, Université Laval Ph. D. en physique

3 6

New Windows Build of 1.55.0
by Tom Kent 19 Nov '13

19 Nov '13

The previous build of 1.55.0 did not build with the correct zlib version (and thus the correct sub-library of iostreams did not build). I have created a 1.55.0-build2 directory on the sourceforge page with the updated version. I've also added a note to the 1.55.0/README.md file explaining that it is incomplete, but I did not remove the prior build. http://sourceforge.net/projects/boost/files/boost-binaries/1.55.0-build2/ Tom

1 0

Issue with compilation using XCode 4.6/GCC
by Tim Burgess 18 Nov '13

18 Nov '13

Hi, I have a project for Windows/Mac that builds fine using VS2010, but generates errors when I build using Xcode 4.6 with the GCC compiler (required, as this project also uses wxWidgets). All of my modules compile cleanly, but I get the following "orphaned" error output that doesn't seem to belong to any module: SurfaceReader Group /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp:28: '<anonymous enum>' is/uses anonymous type /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp:28: Trying to instantiate 'template<class T> struct boost::remove_reference' /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp:38: '<anonymous enum>' is/uses anonymous type /users/tim/developer/libraries/boost_1_54_0/boost/type_traits/decay.hpp:38: Trying to instantiate 'template<class T> struct boost::remove_reference' I realise that I haven't provided the command that Xcode is using to build the project - this isn't deliberate, but I can't seem to locate where Xcode provides this on-screen using the VoiceOver accessibility tool (I'm a totally blind developer). Can anybody offer any advice regarding decay.hpp errors (I'm not including it directly in any of my modules), or can direct to me to where I might find a log that would provide more detail as to the compilation options that Xcode is using (i.e. its GCC-equivalent command line)? Many thanks in advance. Best wishes. Tim Burgess

1 1

Can gil library in boost 1.49 load png palette images?
by Guangchao Wang 18 Nov '13

18 Nov '13

I'm tried to load a png which can be found in the attachment, I find the color of this png is PNG_COLOR_TYPE_PALETTE and its depth is 8, I reviewed the code of png_io_private.hpp and found that no such type of PNG is supported. Can you give me some help about how to load such PNG with boost.gil library? Thank you very much. Best, Guangchao

4 6

Did build of Boost succeed - lib vs. stage/lib?
by Lutz Gehlen 17 Nov '13

17 Nov '13

Hello all, I am trying to build the Boost libraries version 1.55.0 with Visual Studio 2010 Express under Windows XP. Following the instructions in the documentation, I have unpacked the source code distribution, opened a Visual Studio command line window, and executed bootstrap .\b2 I haven't noticed any errors, and I was told in the end that I had successfully built the Boost libraries. So far, so good. I then tried to build the example program in section 6 of the Getting started guide. Section 6.1 instructs to add "C:\Program Files\boost\boost_1_55_0\lib" (in my case E:\boost_1_55_0\lib) to the list of Additional Library Directories. However, I do not have a lib directory in E:\boost_1_55_0?! I tried to build the example program and then searched for the library file libboost_regex-vc100-mt-gd-1_55.lib that Visual Studio was failing to find. I found it in E:\boost_1_55_0\stage\lib instead of E:\boost_1_55_0\lib. Adding this directory to the list of Additional Library Directories allowed me to build and execute the example program successfully. However, I am wondering now whether my build worked correctly or not. I am trying to avoid running into subtle and hard to debug problems later. Does anyone know if or what went wrong with my build? What is the stage directory and is it safe to use it? Thank you very much for your help and best wishes Lutz

2 2

the link to the documentation for "explicit bool operator" is broken
by Adam Romanek 17 Nov '13

17 Nov '13

Dear Boosters, I've just discovered that there's a broken link to the documentation of "explicit bool operator" macro on http://www.boost.org/doc/libs/1_55_0/libs/utility/index.html WBR, Adam Romanek

2 1

Can I return std::unique_ptr in a boost::future?
by Aaron_Wright＠selinc.com 15 Nov '13

15 Nov '13

I'm trying to return a std::unique_ptr in a boost::future. I can't get it to compile. Is it possible? The code wraps a packaged_task in a functor to make it copyable enough to pass to a boost::asio::io_service, where the work will be done in another thread. The code works for other return types that are copyable. This is what I have for a small test case: std::unique_ptr< int > get_int_impl(int i) { return std::unique_ptr< int >(new int(i)); } std::unique_ptr< int > get_int(int i) { typedef boost::packaged_task< std::unique_ptr< int > > Task; boost::shared_ptr< Task > task = boost::make_shared< Task >(boost::bind(&get_int_impl, 42)); boost::unique_future< std::unique_ptr< int > > future = task->get_future(); // <--- Error from this line. m_service.post(boost::bind(&Task::operator(), task)); return future.get(); } BOOST_AUTO_TEST_CASE(test_get_int) { BOOST_CHECK_EQUAL(*get_int(42), 42); } The error: boost/thread/future.hpp(239): error C2248: 'std::unique_ptr<_Ty>::unique_ptr' : cannot access private member declared in class 'std::unique_ptr<_Ty>' --- Aaron Wright

4 6

Re: [Boost-users] [Math] BOOST_FPU_EXCEPTION_GUARD on Linux
by David Roberts 15 Nov '13

15 Nov '13

> As I recall this was a hardware issue on early AMD 64-bit CPU's, possibly a > GLIBC issue too. In fact if I recall it was this issue: > http://sourceware.org/bugzilla/show_bug.cgi?id=2445 which didn't get much > help from the glibc guys > > But basically if any of the FPU exception flags are set prior to a call to > pow or exp, you risk getting a garbage answer back. I'll add a link to the > above in the code. > > HTH, John. That Bugzilla link was extremely helpful - thanks! I've done a bit more research and I'm pretty sure this WAS a bug in glibc. It's fixed on recent versions of Linux though. Taking your test program from http://sourceware.org/bugzilla/show_bug.cgi?id=2445 and trying it on some different Linux versions and CPUs resulted in this: SLES 10: kernel 2.6.16.21-0.8-smp glibc 2.4 g++ 4.1.0 CPU Xeon E5-2630 FAILS CentOS 6.2: kernel 2.6.32-220.el6.x86_64 glibc 2.12 g++ 4.4.6 CPU Xeon X3450 FAILS Amazon Linux 2013.03: kernel 3.4.57-48.42.amzn1.x86_64 glibc 2.12 g++ 4.6.3 CPU Xeon E5507 FAILS OpenSuSE 12.1: kernel 3.1.10-1.16-ec2 glibc 2.14.1 g++ 4.6.2 CPU Xeon E5-2650 WORKS OpenSuSE 12.2: kernel 3.4.6-2.10-ec2 glibc 2.15 g++ 4.7.1 CPU Xeon E5-2650 WORKS Fedora 20 beta: kernel 3.11.6-300.fc20.x86_64 glibc 2.18 g++ 4.8.2 CPU Xeon E5645 WORKS This shows that the problem definitely occurs on Intel CPUs as well as AMD, and is much more likely to be caused by glibc than the compiler or the kernel. The most likely change to the glibc code that fixed the problem is this one from May 2011: http://repo.or.cz/w/glibc.git/commitdiff/8db736347c7aca3201f61e3f05b5f672bc… There was a place in powl() where 4500 decimal was used instead of 0x4500 hex. 4500 decimal is 0x1194 hex. This number was then tested against the floating point status word. The exception flags are in the low byte of this word (see http://www.nacad.ufrj.br/online/intel/Documentation/en_US/compiler_f/main_f… for the values) and as a result of the typo the presence of either FE_UNDERFLOW = 0x10 or FE_DIVBYZERO = 0x4 will cause the test to pass unintentionally. More experiments with your test program on CentOS 6.2 (glibc 2.12) seem to confirm this - if only the flags FE_INEXACT, FE_OVERFLOW and/or FE_INVALID are set they DON'T cause the weird result to occur. Given the bug was in the x86_64-specific powl() implementation and it seems to be fixed in glibc version 2.14, I think you could get away with tightening up the criteria on your guard from: #if ((defined(__linux__) && !defined(__UCLIBC__)) || defined(__QNX__) || defined(__IBMCPP__)) && !defined(BOOST_NO_FENV_H) to: #if ((defined(__linux__) && defined(__x86_64__) && !defined(__UCLIBC__) && (!defined(__GLIBC_PREREQ) || !__GLIBC_PREREQ(2,14))) || defined(__QNX__) || defined(__IBMCPP__)) && !defined(BOOST_NO_FENV_H) That still doesn't help people like me who have to work on current 64 bit enterprise Linux releases, but for the benefit of anyone else who stumbles across this having suffered the same performance problem, here's a hack that works OK if neither your code nor any other 3rd party library you're using cares about the floating point flags. In boost/math/tools/config.hpp change: struct fpu_guard { fpu_guard() { fegetexceptflag(&m_flags, FE_ALL_EXCEPT); feclearexcept(FE_ALL_EXCEPT); } ~fpu_guard() { fesetexceptflag(&m_flags, FE_ALL_EXCEPT); } private: fexcept_t m_flags; }; to: struct fpu_guard { fpu_guard() { if (fetestexcept(FE_UNDERFLOW | FE_DIVBYZERO) != 0) { feclearexcept(FE_ALL_EXCEPT); } } }; This is beneficial for performance because the expensive calls are feclearexcept() and fesetexceptflag(). The (more-or-less identical on Linux) fegetexceptflag() and fetestexcept() functions are much quicker. Not bothering to reset the cleared flags saves one expensive call - obviously this relies on nothing downstream caring about them. Only clearing the flags if one of the problematic ones is set often avoids the other expensive call. I've noticed that the FE_INEXACT flag is almost always set if you do any serious floating point calculation, but the other 4 flags are set much less frequently. I'm not suggesting that you put this hack into the official Boost codeline, but just thought it might be useful to anyone in my situation who finds this post via a search engine.

2 1

concept_check() fails for types from unnamed namespace on gcc 4.2.3
by Adam Romanek 15 Nov '13

15 Nov '13

Dear Boosters! I have a problem compiling some source code that uses Boost 1.54 and gcc 4.2.3 (it's a toolchain for a MIPS platform but that's irrelevant). Basically there is a problem with checking concepts on types that come from unnamed namespaces. See the attached code example and compiler error message. Note that the same code compiles without any problems on gcc 4.6.3. I've found a question on boost-dev list [1] and a ticket [2] related to this particular issue. Note that the ticket was closed with "worksforme" resolution, which I don't understand - the problem is still out there. Now since Boost's minimal requirements are gcc 3.3 [3] then should I consider it a bug that I should report or is it a known issue? In case the latter is true then what should I do? [1] http://boost.2283326.n4.nabble.com/concept-check-fails-with-types-declared-… [2] https://svn.boost.org/trac/boost/ticket/2037 [3] http://www.boost.org/users/history/version_1_55_0.html WBR, Adam Romanek

1 0

Can gil library in boost 1.49 load png palette images?
by Guangchao Wang 15 Nov '13

15 Nov '13

I'm tried to load a png which can be fund in the attachment, I find the color of this png is PNG_COLOR_TYPE_PALETTE and its depth is 8, I reviewed the code of png_io_private.hpp and found that no such type of PNG is supported. Can you give me some help about how to load such PNG with boost.gil library? Thank you very much. Best, Guangchao

1 0

boost::serialization warnings for template class
by Michele Vallisneri 15 Nov '13

15 Nov '13

Dear Boost experts, I'm serializing (intrusively) a template class Matrix<T> that includes a double-pointer buffer of data of type T. So my save/load pair looks like template<class Archive> void save(Archive & ar, const unsigned int version) const { ar & row_dim; ar & col_dim; for ( size_t i = 0; i < row_dim; i++ ) for ( size_t j = 0; j < col_dim; j++ ) { ar & value[i][j]; } } template<class Archive> void load(Archive & ar, const unsigned int version) { size_t rowdim, coldim; ar & rowdim; ar & coldim; resize( rowdim, coldim ); for ( size_t i = 0; i < rowdim; i++ ) for ( size_t j = 0; j < coldim; j++ ) ar & value[i][j]; } The type of value is T**. The serialization works OK, but I'm getting some warnings that lead me to suspect that Boost is trying to track the addresses of the value[i][j] elements, which is not needed, and presumably a problem for performance. g++ -c -m64 -O3 -Wall -I../../include -I/usr/depot/redhatel5_64/boost/1.48.0/include -o Linux-x86_64/obj/test_Matrix.o test_Matrix.cpp /usr/depot/redhatel5_64/boost/1.48.0/include/boost/mpl/print.hpp: In instantiation of 'boost::mpl::print<boost::serialization::BOOST_SERIALIZATION_STATIC_WARNING_LINE<98> >': /usr/depot/redhatel5_64/boost/1.48.0/include/boost/serialization/static_warning.hpp:92: instantiated from 'boost::serialization::static_warning_test<false, 98>' /usr/depot/redhatel5_64/boost/1.48.0/include/boost/archive/detail/check.hpp:98: instantiated from 'void boost::archive::detail::check_object_tracking() [with T = gcore::Matrix<int>]' /usr/depot/redhatel5_64/boost/1.48.0/include/boost/archive/detail/oserializer.hpp:313: instantiated from 'static void boost::archive::detail::save_non_pointer_type<Archive>::invoke(Archive&, T&) [with T = gcore::Matrix<int>, Archive = boost::archive::text_oarchive]' /usr/depot/redhatel5_64/boost/1.48.0/include/boost/archive/detail/oserializer.hpp:525: instantiated from 'void boost::archive::save(Archive&, T&) [with Archive = boost::archive::text_oarchive, T = gcore::Matrix<int>]' /usr/depot/redhatel5_64/boost/1.48.0/include/boost/archive/detail/common_oarchive.hpp:69: instantiated from 'void boost::archive::detail::common_oarchive<Archive>::save_override(T&, int) [with T = gcore::Matrix<int>, Archive = boost::archive::text_oarchive]' /usr/depot/redhatel5_64/boost/1.48.0/include/boost/archive/basic_text_oarchive.hpp:80: instantiated from 'void boost::archive::basic_text_oarchive<Archive>::save_override(T&, int) [with T = gcore::Matrix<int>, Archive = boost::archive::text_oarchive]' /usr/depot/redhatel5_64/boost/1.48.0/include/boost/archive/detail/interface_oarchive.hpp:63: instantiated from 'Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = gcore::Matrix<int>, Archive = boost::archive::text_oarchive]' test_Matrix.cpp:43: instantiated from here /usr/depot/redhatel5_64/boost/1.48.0/include/boost/mpl/print.hpp:55: warning: comparison between signed and unsigned integer expressions Is my suspicion correct, and how do I change my code to avoid the warnings (and performance hits, if any)? Thanks! Michele

1 0

Boost 1.55 and warning in Boost.Circular
by gast128 14 Nov '13

14 Nov '13

Hello all, I just dl 1.55 and I got a warning: D:\Develop\SDK and Libraries\boost_1_55_0\boost/circular_buffer/base.hpp(199): warning C4172: returning address of local variable or temporary Code is crytpic due to all the templates. Is this a client error?

1 2

Boost.Log: Set formatter for named_scope attr.
by David Puffer 14 Nov '13

14 Nov '13

Hi, Being new to Boost.Log (and Boost in general) I have spent the last few days trying to implement Boost.Log - which Is working fairly well by now. However - I encountered one problem that I've not been able to solve by now, although it seems to me quite trivial: I have successfully registered the "named_scope" attribute and I am populating its value by a call to BOOST_LOG_FUNCTION. This works well and I can see the function-name in my log-output. However - I also want the line-number and the file-name, and discovered that there's a possibility to set the output-format of the "named_scope" attribute (which already incorporates file-name and line-number info) like so: #include <boost/log/expressions/formatters/named_scope.hpp> sink->set_formatter(expr::stream << expr::format_named_scope("Scopes", "%n")); As documented here: http://www.boost.org/doc/libs/1_54_0/libs/log/doc/html/log/detailed/express… I just don't seem to find any way to get to my sink - which is configured in a settings-file and evaluated by a call to the init_from_stream() function. Is there any way to query for all the sinks - or get a sink by name? How is one supposed to set a sink formatter for a sink which was generated by the library and not the user? Or is there a way to specify the output-format for named attributes via a settings-file as well? As far as I can see it's only possible to format the output of a log record as a whole - but not single attributes. Also: Is it correct, that the above function will only set the format for the "Scopes" attribute - which means I could call this function repeatedly for lets say the "TimeStamp" attribute as well? Best regards, David

2 2

[Log] Error with operator<< in basic_formatting_ostream
by Víctor Yo 14 Nov '13

14 Nov '13

Hi ewveryone, I'm working lately with Boost.Log (I'm a newbie) library and I want to write a logger with some parameters and formatting options. I followed the documentation, I created a backend and a frontend and I tried to format the output in the frontend with the set_formatter() function. I tried with the Lambda style and with the Boost.Format style but I'm getting an error that I can not locate. Iwas working on it for the last two whole days but I couldn't find a solution. It is related with the basic_formatting_ostream, but I don't understand what that means. I defined the backend and attached to it two streams (to a file and to cout) typedef boost::log::sinks::text_ostream_backend our_backend; typedef boost::log::sinks::synchronous_sink<our_backend> our_frontend; //............................................................................................................................................ boost::shared_ptr<our_backend> backend = boost::make_shared<our_backend>(); //Stream definitions boost::shared_ptr<std::ostream> stream_out(&std::cout, boost::log::empty_deleter()); boost::shared_ptr<std::ostream> stream_file(new std::ofstream("file_logger.log")); backend -> add_stream(stream_out); backend -> add_stream(stream_file); Created the frontend (and wrapping the backend to it) //Wrap the backend into the frontend and register in the core. //The frontend provides synchronization for the backend. boost::shared_ptr<our_frontend> frontend(new our_frontend(backend)); And now come the offending code which is supposed to format the output (note that the first commented block was my first try). None of them works and the error is the same in both cases: */*frontend -> set_formatter* * (* * boost::log::expressions::format("[%1%] %2%, File: %3%, Line: %4% <%5%>: %6% ")* * % boost::log::attributes::counter< unsigned int >(1)* * % boost::log::attributes::local_clock()* * % boost::log::expressions::attr< severity_level >("Severity")* * % boost::log::expressions::message* * );*/* //We are going to define the formatter in a different style to try to get formatted output frontend -> set_formatter ( boost::log::expressions::stream << boost::log::attributes::counter< unsigned int >(1) <<" ["<< boost::log::attributes::local_clock() <<"] <"<< boost::log::expressions::attr< severity_level >("Severity") <<"> "<< boost::log::expressions::message ); The error I get is the next one: */home/victor/Programacion/workspace/opice/build-parallel/../libs/include/boost/log/utility/formatting_ostream.hpp:664:5: error: no match for ‘operator<<’ in ‘(& strm)->boost::log::v2_mt_posix::basic_formatting_ostream<CharT, TraitsT, AllocatorT>::stream [with CharT = char, TraitsT = std::char_traits<char>, AllocatorT = std::allocator<char>, boost::log::v2_mt_posix::basic_formatting_ostream<CharT, TraitsT, AllocatorT>::ostream_type = std::basic_ostream<char>]() << value’* And I really don't know what is happening. I also included a lot of files (I'm sure I included too much files, indeed) to be sure it was not caused by some undefined operator or something similar. However I still have the same problem. The includes are: #include <iostream> #include <fstream> #include <string> #include <boost/thread/shared_mutex.hpp> #include <boost/log/core.hpp> #include <boost/log/common.hpp> #include <boost/make_shared.hpp> #include <boost/log/expressions.hpp> #include <boost/log/utility/setup/file.hpp> #include <boost/log/utility/setup/console.hpp> //puede ser innecesario #include <boost/log/utility/setup/common_attributes.hpp> //puede ser innecesario #include <boost/log/utility/empty_deleter.hpp> #include<boost/thread/mutex.hpp> #include <boost/log/attributes/timer.hpp> #include <boost/log/attributes/mutable_constant.hpp> #include <boost/log/sources/severity_logger.hpp> #include <boost/log/utility/formatting_ostream.hpp> #include <boost/log/sinks/text_ostream_backend.hpp> #include <boost/log/sinks/sync_frontend.hpp> #include <boost/log/support/date_time.hpp> As you can see, they are probably redundant or innecessary but I could rip off that files when I could get the program compiled. Now, I'm out of ideas so any help you could bring me should be very appreciated. Thank you in advance. Victor Hevia

2 4

[1.55] PDF Documentation build available.
by John Maddock 14 Nov '13

14 Nov '13

The final PDF documentation build for Boost-1.55 is now available at https://sourceforge.net/projects/boost/files/boost-docs/1.55.0/ As ever this only contains documentation for the subset of Boost libraries that use quickbook/boostbook/docbook based documentation. Enjoy! John.

1 0

Boost 1.54.0 Header Warnings: Shadowed Variables
by Tom Browder 13 Nov '13

13 Nov '13

I am trying to use Boost 1.54.0 to replace a previous version (1.47) and am using g++ 4.7 with most warnings turned on. I am getting many -Wshadow errors and wonder why they exist. Surely the developers test for such. Here is one example from xpressive/detail/utility/hash_peek_bitset.hpp: Both 'icase' and 'count' are reported to shadow members of 'this'. Note that the bool arg is named 'icase' but the compiler reports 'this' has a member named 'icase' (as can be plainly seen below). In this example it's fairly clear what is intended, but then again maybe not (and it doesn't give the user much confidence in the code). It isn't good practice IMHO to do such so that is why I like to use some prefix or suffix to disambiguate the two variables. // Make sure all sub-expressions being merged have the same case-sensitivity bool test_icase_(bool icase) { std::size_t count = this->bset_.count(); if(256 == count) { return false; // all set already, nothing to do } else if(0 != count && this->icase_ != icase) { this->set_all(); // icase mismatch! set all and bail return false; } this->icase_ = icase; return true; } I could file many bugs but it begs the question of why the warnings are allowed in the first place. Suggestions? Thanks and best regards, -Tom

8 17

[Boost.Iterator] Problem compiling zip_iterator with clang and C++11
by Jonathan Jones 13 Nov '13

13 Nov '13

Hi folks, The following code fails to compile on OSX 10.8.5 with Xcode 5.0.1 and Boost 1.49.0. This is not real world code, but it demonstrates the problem I'm facing. #include <boost/iterator/zip_iterator.hpp> template<typename T> void foo() { boost::zip_iterator<boost::tuple<T*, T*> > iter; std::fill(iter, iter, std::make_pair(T(),T())); } void bar() { foo<int>(); } Here are the commands I used to compile (if I drop "-stdlib=libc++" from the compile line, the code compiles just fine): setenv DEVELOPER_DIR /Applications/Xcode5.0.1.app/Contents/Developer xcrun -sdk macosx10.8 clang++ -c zip_iterator.cpp -I<boost-path>/include -std=c++11 -stdlib=libc++ and here is a heavily formatted snippet of the key error: /Applications/Xcode5.0.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/c++/v1/algorithm:1824:1: note: candidate function [with _RandomAccessIterator = boost::zip_iterator<boost::tuples::tuple<int*, int*>>, _Tp = std::__1::pair<int, int>] not viable: no known conversion from typename iterator_traits<zip_iterator<tuple<int*, int*>>>::iterator_category (aka 'boost::detail::iterator_category_with_traversal<std::__1::input_iterator_tag, boost::random_access_traversal_tag>') to 'std::__1::random_access_iterator_tag' for 4th argument __fill(_RandomAccessIterator __first, _RandomAccessIterator __last, const _Tp& __value_, random_access_iterator_tag) Any help is appreciated. Thanks, Jon

1 0

[Math] BOOST_FPU_EXCEPTION_GUARD on Linux
by David Roberts 13 Nov '13

13 Nov '13

Hello, I have a program that makes considerable use of the gamma distribution from Boost.Math. Profiling with OProfile has shown that, on Linux, this program spends about 20% of its runtime calling the functions fesetexceptflag() and feclearexcept(). The code responsible for calling these is in the BOOST_FPU_EXCEPTION_GUARD macro which is defined in boost/math/tools/config.hpp. I have looked back through the source history to see when and why this macro was added, and it was in changeset 3186 from September 2006 with the comment "More linux fixes: finally got AMD64 machines to behave correctly" (see https://svn.boost.org/trac/boost/changeset/3186) In Boost 1.54 the conditions under which the guard macro is defined have been refined since it was originally added, but the guard class itself remains the same as in 2006. Given the performance penalty I am suffering as a result of constantly clearing and reseting the floating point exception flags, I have a couple of questions about this functionality: 1) Can anyone provide a specific test case that did not work without the BOOST_FPU_EXCEPTION_GUARD functionality but was fixed by its addition? It would be very useful to have such a test case because then I can check if this is still a problem on recent versions of Linux. 2) The commit comment for changeset 3186 refers to AMD64. Does this mean the original problem only occurred on AMD CPUs, or does this refer to the architecture, and hence it affected both Intel and AMD CPUs? Many thanks, David Roberts

2 1

[Graph] Static allocation of nodes and edges
by Sensei 13 Nov '13

13 Nov '13

Dear all, I need to optimize my code with regards to both memory and time. The problem is simple: pre-allocating the adjacency matrix. The graph may have a huge number of nodes N, but the number of edges K per node is limited. While N can be in the order of one hundred million, K is at most 10. The graph will be directed, so no symmetry is needed. Do you know if I can pre-allocate such an adjacency matrix? If not, I suppose I must use an adjacency list in order to minimize memory consumption, am I right? Thanks!

2 9

Help with lockfree queue
by TYSON Kieran 13 Nov '13

13 Nov '13

[@@ OPEN @@] Hello, I am using a global lockfree queue to transfer a message from different threads. The program compiles and runs without fault up until the program exits and the queues destructor is called. An unhandled exception is thrown on the destruction of the queue. Below is the code used to set up the queue. #define B1_OUTPUT_LENGTH_PER_CHANNEL (32000) #define B2_OUTPUT_LENGTH_PER_CHANNEL (32000) #define B3_OUTPUT_LENGTH_PER_CHANNEL (64000) #define NB_CHANNELS (8) typedef struct s_OutputMsg { float dataB1[(int)B1_OUTPUT_LENGTH_PER_CHANNEL*NB_CHANNELS]; float dataB2[(int)B2_OUTPUT_LENGTH_PER_CHANNEL*NB_CHANNELS]; float dataB3[(int)B3_OUTPUT_LENGTH_PER_CHANNEL*NB_CHANNELS]; int dataLength; } OutputMsg; boost::lockfree::queue<OutputMsg, boost::lockfree::fixed_sized<true>> dataMsgQueue(100); My first thoughts are that there are limitations on the size of the message because I have used simple integer queues in the past with no problem. Are there size limitations on the message of a lockfree queue? Thanks, Kieran This message contains OPEN information that is not sensitive and can be freely accessed by people both inside and outside of the Thales Group This email was classified by Tyson, Kieran on Wednesday, 13 November 2013 10:58:41 AM ------------------------------------------------------------------------- DISCLAIMER: This e-mail transmission and any documents, files and previous e-mail messages attached to it are private and confidential. They may contain proprietary or copyright material or information that is subject to legal professional privilege. They are for the use of the intended recipient only. Any unauthorised viewing, use, disclosure, copying, alteration, storage or distribution of, or reliance on, this message is strictly prohibited. No part may be reproduced, adapted or transmitted without the written permission of the owner. If you have received this transmission in error, or are not an authorised recipient, please immediately notify the sender by return email, delete this message and all copies from your e-mail system, and destroy any printed copies. Receipt by anyone other than the intended recipient should not be deemed a waiver of any privilege or protection. Thales Australia does not warrant or represent that this e-mail or any documents, files and previous e-mail messages attached are error or virus free. -------------------------------------------------------------------------

2 1

How to convert cmyk jpg file to rgb jpg file with BOOST.GIL?
by Guangchao Wang 13 Nov '13

13 Nov '13

I used following code: rgb8_image_t rgb8Img; jpeg_read_and_convert_image("CMYK.jpg", rgb8Img); //CMYK.jpg is CMYK image jpeg_write_view("RGB.jpg", const_view(rgb8Img)); to convert CMYK image to RGB image. The saved RGB.jpg is not correct. Could you give me some suggestion? Thanks.

2 2

[Locale] Getting correct system locale under Mac OS X
by Orhun Birsoy 11 Nov '13

11 Nov '13

I am using boost 1.55.0.rc2. I am running 10.8.5 and when I select "Norway (Norwegian Bokmal)" (nb_NO) as the region, LANG env. variable is undefined, making boost::locale::generator("") to generate a "C" locale. I can of-course get the locale identifier from NSLocale (or CFLocale) and initialize the boost::locale::generator with "nb_NO" which seems to be working, but with Mavericks things got even more interesting. It looks like, in 10.9 you can mix and match language with a country anyway you like i.e. I can select "Norway" as my region and "English" as my language and again LANG is empty but NSLocale returns "en_NO". But this time when I use boost::locale::generator("en_NO"), boost::locale::as::number uses "." (dot) as decimal separator, although NSLocale reports "," (comma). 1. Can boost::locale handle such combinations (en_NO, en_TR, etc)? (I am using ICU backend, others are explicitly turned off). a. for number formatting? b. for messages formatting (translations)? which mo will it pick for en_TR ? 2. How can I 'customize' locale generated by boost::locale to reflect the changes user might do in system locale settings (i.e. select en_US but change the decimal symbol)? Thanks. -- Orhun Birsoy

2 1

Thanks to everyone for all the work on 1.55.0
by Marshall Clow 11 Nov '13

11 Nov '13

I just wanted to take off my "release manager" hat and say, personally, thank you to all the people who tried out the RCs/Betas/etc, reported bugs, and suggested fixes. You were all a big help in making the release. -- 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

Boost 1.55.0 released!
by Marshall Clow 11 Nov '13

11 Nov '13

Release 1.55.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains one new library and numerous enhancements and bug fixes for existing libraries. === New Libraries === • Predef: This library defines a set of compiler, architecture, operating system, library, and other version numbers from the information it can gather of C, C++, Objective C, and Objective C++ predefined macros or those defined in generally available headers, from Rene Rivera. === Known bugs with Visual Studio 2013/Visual C++ 12 === Visual Studio 2013 was released quite late in the release process, so there exist several unresolved issues. These include: • Serialization can't compile because of a missing include. • Using has_member_function_callable_with from Boost.Container's allocator_traits causes a compile error (#9332). • For several libraries overloads with intializer lists are incorrectly reported as ambiguous. This is a Visual C++ bug and it isn't clear if there's a good workaround. • In libraries such as Unordered and MultiIndex, calling overloaded functions with initializer lists can result in a compile error, with Visual C++ claiming that the overloads are ambiguous. This is a Visual C++ bug and it isn't clear if there's a good workaround. This won't affect code that doesn't use initializer lists, or uses an initializer list that doesn't require an implicit conversion (i.e. an initializer list of the container's exact value type). • Thread: ex_scoped_thread compile fails (#9333). For details, including download links, see http://www.boost.org/users/news/version_1.55.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.55.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 Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes

2 1