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

Fwd: [Boost-announce] [boost] [metaparse] Review period starts May 25th and ends June 7th
by Christophe Henry 28 May '15

28 May '15

I had sent this message only to the Developer mailing list. Please let me correct this mistake now. ------------------------------------------------------------------------------------------------------------------------- Dear all, The review of the Metaparse library starts next Monday, May 25th and ends June 7th. Metaparse was written by Abel Sinkovics. Metaparse is a parser generator library for template metaprograms. The purpose of this library is to support the creation of parsers that parse at compile time. This library is intended to be used for embedded domain specific language creation for C++ and can help libraries provide a better interface. It is similar to Boost.Spirit, however while parsers built with Spirit parse at run-time, parsers built with Metaparse parse at compile-time. It makes it possible for library authors to provide an interface that follows the common notation of the problem domain of the library. (eg. SQL queries, grammars, etc written in their common notation instead of similar-looking C++ expressions). For example there is a (yet incomplete) interface for Boost.Spirit that makes it possible to write MPLLIBS_REGEX("^[abcd][3-8]\\.foo$") instead of bos >> set[as_xpr('a')|'b'|'c'|'d'] >> range('3','8') >> '.' >> 'f' >> 'o' >> 'o' >> eos and make the parser built with Metaparse generate the latter expression from the former one. (It can be found here: https://github.com/istvans/mpllibs/tree/master/libs/xlxpressive) Since the library is based on template metaprogramming, the DSLs can be used for type validation as well. This is demonstrated by the type-safe printf implementation ( http://abel.web.elte.hu/mpllibs/safe_printf/index.html) It type-checks the arguments of a printf call based on the format string and has zero runtime overhead compared to unchecked printf. Parsers can be constructed in a declarative manner and (even though this is template metaprogramming based) remain readable. The implementation reflects the grammar it parses (with additional elements for semantic actions). Even though the library requires the parser author to write template metaprograms, the development of parsers is well supported by tools like Metashell and MDB. An important aspect of parsers (built with this library or another one) is error reporting for invalid input. The library offers tools for the parser authors to be able to provide useful error messages in case of parsing errors. Here is an example error report by a parser built with Metaparse (the parser can be found in the Getting Started guide of the library): ..... x__________________PARSING_FAILED__________________x<1, 5, unpaired<1, 1, literal_expected<')'>>> .... It is an error report letting the developer know that a closing paren is missing at line 1, column 5 and the unclosed opening paren is in line 1, column 1. Metaparse can be downloaded from Github: https://github.com/sabel83/mpllibs/tree/master/mpllibs/metaparse And a very complete tutorial: http://abel.web.elte.hu/mpllibs/metaparse/getting_started.html The tutorial also offers the nice feature of a link to metashell for quick-starting trying out the library: http://abel.web.elte.hu/shell/metashell.html Boost.Msm v3 also implements a new compile-time strings based front-end called eUML2 to demonstrate the power of the library and the conciseness and expressiveness it allows. Please have a look at the documentation: https://htmlpreview.github.io/?https://raw.githubusercontent.com/boostorg/m… Everybody on this list is invited to participate in this formal review. I hope to see your review of Metaparse, including your vote on acceptance, and I welcome your participation in the ensuing discussions on the Boost developers' mailing list. Please always include in your review a vote as to whether the library should be accepted into Boost. Additionally please consider giving feedback on the following general topics: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? - With what compiler? - Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Regards, Christophe Review Manager

1 0

[BGL] Dijkstra shortest paths with custom compare function and zero weight edges
by Christian Ofenböck 27 May '15

27 May '15

I'm using dijkstra_shortest_paths with a custom compare function like (Weight a, Weight b) { return a<=b; } As I've also got some zero weight edges within the graph this leads to problems with the test for negative weights in dijkstra_bfs_visitor's examine_edge-function. The test fails on checking zero weight edges and throws a negative_edge-exception (dijkstra_shortest_paths.hpp:190): if (m_compare(m_combine(m_zero, get(m_weight, e)), m_zero)) evaluates to if(0<=0) Any suggestions on how to solve this issue? For now I just got rid of the test, as I just use unsigned weight values, but of course that's not a sound solution.

1 0

question about filtered_graph
by breadbread1984 25 May '15

25 May '15

I am using boost graph library. In order to get a filtered graph, I adopted filtered_graph. I thought it could be used in the same way as adjacency_list. But when I get target and source from an edge of a filtered graph, I realized the target and source function doesn't accept filtered_graph as its argument. How can I get the two terminals of an edge from a filtered_graph then? Thanks for any hints in advance.

1 0

[Serialization] STL Containers and Non-Default Constructors
by Trevor Thoele 24 May '15

24 May '15

I have recently changed from a hand-rolled serializer to Boost's and while it's mostly been fantastic, there's one problem that I can't seem to shake - I cannot get it to serialize non-default constructible types. It fails on trying to generate code that requires the usage of a default constructor. In non-associative types (list/deque/vector), the loader seems to be calling the container's resize function with a default value_type argument, resulting in the attempted creation of the object through the default constructor. In associative types, the loader attempts to create a default constructed value_type, which results in an std::pair being defaultly constructed with one of the pieces being the non-default constructible type. The code below fails during compilation with the error "'A' : no appropriate default constructor available". It was built with MSVC++2013. #include <list> #include <fstream> #include <boost\archive\binary_iarchive.hpp> #include <boost\archive\binary_oarchive.hpp> #include <boost\serialization\access.hpp> #include <boost\serialization\list.hpp> class A { private: template<class Archive> void serialize(Archive &archive, unsigned int version) { archive & myInt; } friend boost::serialization::access; public: int myInt; A(int myInt) : myInt(myInt) {} A(const A &arg) : myInt(arg.myInt) {} A& operator=(const A &arg) { myInt = arg.myInt; return *this; } bool operator==(const A &arg) const { return myInt == arg.myInt; } }; namespace boost { namespace serialization { template<class Archive> inline void load_construct_data(Archive &archive, A *a, unsigned int file_version) { ::new(a)A(0); } } } int main() { { std::ofstream stream("file"); boost::archive::binary_oarchive archive(stream); std::list cont; cont.push_back(A(1)); archive << cont; } { std::ifstream stream("file"); boost::archive::binary_iarchive archive(stream); std::list cont; archive >> cont; } } My question is: is this behavior known and what is the best solution to this for an end-user? The tutorial for STL container serialization mentions using load/save_construct_data to get around this problem, yet the attempted code generation above do not take that solution into account so compilation will fail even if you overload those templates. The only solutions I can think of to circumvent this problem would be to require a public (the code ultimately fails in std code, which I guess you may be able to friend but would be quite strange) default constructor, or to hand-roll STL container serialization through non-intrusive serialize/save/load overloads and skip the provided overloads entirely. -- View this message in context: http://boost.2283326.n4.nabble.com/Serialization-STL-Containers-and-Non-Def… Sent from the Boost - Users mailing list archive at Nabble.com.

3 4

How to create a subgraph of a graph with specified vertexes?
by ffmm3＠163.com 24 May '15

24 May '15

Hi, I have a graph with several vertexes and edges, now I want to creates a subgraph object with the specified vertex set. What should I do? 发自 Windows 邮件

1 0

Is it Okay to Use the Boost Logo
by - 22 May '15

22 May '15

I tried to find out more about the licence for the logo but didn't get very far, but I now see that on Wikipedia the logo is also released under the Boost License so I presume that I can use it for my project page.

2 1

Please help: boost::format and Borland C++ version 0x564 errors
by Royce 22 May '15

22 May '15

I'm trying to use boost::format with Borland C++ Builder 6 (Compiler version 0x564) and can't get the boost code to compile. The code was working with sprintf but I need to be able to use numbered args (i.e. "The first string is %1% and the second string is %2%." ) for localization so that the language translators can change the position the arguments appear in the translated text. I get an "E2270 > expected" error in line of integral_c.hpp (boost 1_45_0). which is template< bool C > The code near the error is: #if !defined(BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION) \ && !BOOST_WORKAROUND(__BORLANDC__, <= 0x551) BOOST_MPL_AUX_ADL_BARRIER_NAMESPACE_OPEN // 'bool' constant doesn't have 'next'/'prior' members template< bool C > struct integral_c<bool, C> { BOOST_STATIC_CONSTANT(bool, value = C); typedef integral_c_tag tag; . >From what I can tell I should not have to define BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION, and defining it I breaks working code. I did find a reference to a bug that affects version Borland compiler versions 0x561 to 0x580 and I tried defining BOOST_BCB_PARTIAL_SPECIALIZATION_BUG. That did not help, but at least it didn't break anything. I am able to create a small test project and it works. I was able to get the same basic code to work in 50 or 60 places in 21 of the 23 *.cpp units in my primary project. This worked in my test code but broke in my main project. std::stringstream ss; ss << boost::format(LoadStr(STestWithString).c_str()) % "First" % "Second"; AnsiString translatedMsg = AnsiString(ss.str().c_str()); ShowMessage(translatedMsg); This also worked in my test program, but broke in my main project. std::string sRawMsg; AnsiString sDebug1 = "testArg1"; AnsiString sDebug2 = "testArg2"; sRawMsg = (boost::format("Testing %1% was first. %2% was second.") % sDebug1.c_str() % sDebug2.c_str()).str(); // ignoreW8080(boost::none); // Suppress false warning - Compiles to a nop. Any suggestions on solving this problem would be greatly appreciated. Royce Fessenden White Knight Software <http://www.whiteknightsw.com/> www.WhiteKnightSw.com 417.766.1852 royce(a)fessenden.com

1 0

Re: [Boost-users] threads and async questions and asnwers
by Victor Yankee 21 May '15

21 May '15

> > From: Michael Powell <mwpowellhtx(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] threads and async questions and asnwers > Message-ID: > < > CAMEoF_FUUVLa1Cq9_kCRLB-bSRMhH1fni5ft71-4pU-qvAy4fQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Thu, May 21, 2015 at 4:18 PM, Victor Yankee > <victor.whiskey.yankee(a)gmail.com> wrote: > > Hello List, > > > > I have a thread with a class and its method that raises a "question" > signal > > and needs to wait with a timeout for an "answer" signal. > > > > There are several worker threads, some of which may be connected to the > > question signal. The answer signal will be raised by a worker thread > only if > > it knows the answer; it is possible that no worker thread knows the > answer > > so no answer signal will be raised (hence need for timeout). The > question > > thread cannot know which worker thread to ask. > > Sounds like a homework question to me. Besides which, the problem > statement pretty much spelled out where you likely need to focus. > This is not homework; your response was not helpful. > > > What is a good way to achieve this using boost 1.58 and/or C++11? I am > using > > g++ 4.9 on 64bit ubuntu 14.04. > > > > Thanks, > > Vic

1 0

String split behaviour
by Venkateswara Rao Sanaka 21 May '15

21 May '15

Hi, I am getting two empty strings from the following program, void boost_split_test() { const string &text("-"); vector<string> tokens; split(tokens, text, boost::is_any_of("-"), token_compress_on); cout << "size of tokens " << tokens.size() << '\n'; for (auto const &e : tokens) cout << e.size() << '\n'; } Output: size of tokens 2 0 0 Is this expected output? I expecting an zero split parts. Could someone clarify? -- Thanks, :) Venki.

2 2

Does lock-less queue wait on empty queue ?
by Ran Shalit 21 May '15

21 May '15

Hello, I'm newbie of boost library. I would like to ask if the lockless queue waits on empty queue ? (I actually need it to wait). And another thing: Can the Pool library be build separately, so that I can use only the boost/pool files or do I need to use all boost sources in order to build just the pool. Thank you, Ran

6 6

[boost][algorithm] Overload of boost::algorithm::all_of_equal
by dariomt＠gmail.com 21 May '15

21 May '15

Hi list, I usually find useful an overload of this function to check whether all elements in a range are equal *to each other*. Something like: template <typename Range> bool all_of_equal(const Range & r) { // return true on empty range if (boost::empty(r)) return true; // return true if all other elements are equal to the first element return boost::all_of_equal( boost::next( boost::begin(r) ), boost::end(r), *boost::begin(r)); } Would this be a useful addition to Boost.Algorithm?

2 1

How to call destructor on thread object?
by Lane 21 May '15

21 May '15

I'm using the boost meta state machine and upon entry of this state, I create two threads, and stop these threads in the on_exit(). In on_entry(), I call the functors of each class and create threads and add those to a boost thread_group. What I need to do now is call the destructor of the objects on the threads ( of ClassA and ClassB) within on_exit(). I'm unclear as to how the destructors of the objects would/should be called when interrupting the threads. The destructors are currently not being called. struct MyEvent : public msm::front::state<> { template <class Event, class FSM> void on_entry(Event const&, FSM&); template <class Event, class FSM> void on_exit(Event const&, FSM&); boost::thread_group threads; }; template <class Event, class FSM> void psm_::MyEvent::on_entry(Event const& ev, FSM& sm) { auto bb = std::make_shared<bounded_buffer<MyData> >(100); ClassA<bounded_buffer<MyData> > c_a(bb); ClassB<bounded_buffer<MyData> > c_b(bb); threads.add_thread(new boost::thread(c_a)); threads.add_thread(new boost::thread(c_b)); } template <class Event, class FSM> void psm_::MyEvent::on_exit(Event const& ev, FSM& sm) { threads.interrupt_all(); threads.join_all(); } template <class Buffer> class ClassB { private: typedef typename Buffer::value_type value_type; shared_ptr<Buffer> m_container; public: ClassB(shared_ptr<Buffer> buffer) : m_container(buffer) { } ~ClassB() { // ... } void operator()() { try { // ... do stuff boost::this_thread::interruption_point(); } catch(const boost::thread_interrupted&) { // ... } } }

3 8

Is it Okay to Use the Boost Logo?
by stellarpower＠googlemail.com 19 May '15

19 May '15

Hello all, Just a quick question, as I couldn't find any compiled binaries for mingw32 I ended up compiling Boost and I was thinking of putting the compiled libraries online, probably on Sourceforge, to save others from the effort. Of course, I'll be making it clear that they're not official or anything. Is it okay for me to use the Boost logo on the project page? Thanks

1 0

"see reference to class template instantiation '...' being compiled" was shown
by Kaosun DJ 19 May '15

19 May '15

Hello, When I executed b2.exe, a message as "see reference to class template instantiation '...' being compiled" was shown. Were any libraries required? My environment is - Windows 8.1 64 bit (version 6.3 build 9600) (ja-JP) - Microsoft Visual Studio Express 2013 for Windows Desktop (version 12.0.30723.00 Update 3) (ja-JP) The reply of b2.exe is as follows. compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\xml_grammar.obj xml_grammar.cpp C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2798) : warning C4996: 'std::_Equal1': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2783) : see declaration of 'std::_Equal1' c:\users\kaosun.earthgroove\downloads\temp\boost_1_58_0\libs\serialization\src\basic_xml_grammar.ipp(452) : see reference to class template instantiation 'bool std::equal<std::_String_iterator<std::_String_val<std::_Simple_types<char>>>,const char*>(_InIt1,_InIt1,_InIt2)' being compiled with [ _InIt1=std::_String_iterator<std::_String_val<std::_Simple_types<char>>> , _InIt2=const char * ] c:\users\kaosun.earthgroove\downloads\temp\boost_1_58_0\libs\serialization\src\basic_xml_grammar.ipp(438): while compiling class template member function 'void boost::archive::basic_xml_grammar<char>::init(std::basic_istream<char,std::char_traits<char>> &)' libs\serialization\src\xml_grammar.cpp(51) : see reference to class template instantiation 'boost::archive::basic_xml_grammar<char>' being compiled : : Snip : : compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\xml_iarchive.obj xml_iarchive.cpp C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2798) : warning C4996: 'std::_Equal1': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2783) : see declaration of 'std::_Equal1' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/basic_xml_iarchive.ipp(67) : see reference to class template instantiation 'bool std::equal<std::_String_iterator<std::_String_val<std::_Simple_types<char>>>,const char*>(_InIt1,_InIt1,_InIt2)' being compiled with [ _InIt1=std::_String_iterator<std::_String_val<std::_Simple_types<char>>> , _InIt2=const char * ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/basic_xml_iarchive.ipp(45): while compiling class template member function 'void boost::archive::basic_xml_iarchive<Archive>::load_end(const char *)' with [ Archive=boost::archive::xml_iarchive ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/xml_iarchive.hpp(50) : see reference to class template instantiation 'boost::archive::basic_xml_iarchive<Archive>' being compiled with [ Archive=boost::archive::xml_iarchive ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/xml_iarchive.hpp(132) : see reference to class template instantiation 'boost::archive::xml_iarchive_impl<boost::archive::xml_iarchive>' being compiled compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\xml_oarchive.obj xml_oarchive.cpp C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2132) : warning C4996: 'std::_Copy_impl': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2113) : see declaration of 'std::_Copy_impl' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/xml_oarchive_impl.ipp(84) : see reference to class template instantiation '_OutIt std::copy<boost::archive::iterators::xml_escape<const char *>,boost::archive::iterators::ostream_iterator<char>>(_InIt,_InIt,_OutIt)' being compiled with [ _OutIt=boost::archive::iterators::ostream_iterator<char> , _InIt=boost::archive::iterators::xml_escape<const char *> ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/xml_oarchive_impl.ipp(74): while compiling class template member function 'void boost::archive::xml_oarchive_impl<boost::archive::xml_oarchive>::save(const std::string &)' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/xml_oarchive.hpp(123) : see reference to class template instantiation 'boost::archive::xml_oarchive_impl<boost::archive::xml_oarchive>' being compiled C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2113) : see declaration of 'std::_Copy_impl' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/iterators/mb_from_wchar.hpp(91) : warning C4996: 'wctomb': This function or variable may be unsafe. Consider using wctomb_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\stdlib.h(567) : see declaration of 'wctomb' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/iterators/mb_from_wchar.hpp(85): while compiling class template member function 'void boost::archive::iterators::mb_from_wchar<boost::archive::iterators::xml_escape<InputIterator>>::fill(void)' with [ InputIterator=const wchar_t * ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/iterators/mb_from_wchar.hpp(65) : see reference to class template instantiation 'void boost::archive::iterators::mb_from_wchar<boost::archive::iterators::xml_escape<InputIterator>>::fill(void)' being compiled with [ InputIterator=const wchar_t * ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/xml_oarchive_impl.ipp(45) : see reference to class template instantiation 'boost::archive::iterators::mb_from_wchar<boost::archive::iterators::xml_escape<InputIterator>>' being compiled with [ InputIterator=const wchar_t * ] : : Snip : : compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\basic_text_woprimitive.obj basic_text_woprimitive.cpp C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2132) : warning C4996: 'std::_Copy_impl': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2113) : see declaration of 'std::_Copy_impl' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/basic_text_oprimitive.ipp(67) : see reference to class template instantiation '_OutIt std::copy<boost::archive::iterators::insert_linebreaks<boost::archive::iterators::base64_from_binary<boost::archive::iterators::transform_width<const char *,6,8,char>,char>,76,const char>,boost::archive::iterators::ostream_iterator<CharType>>(_InIt,_InIt,_OutIt)' being compiled with [ _OutIt=boost::archive::iterators::ostream_iterator<CharType> , _InIt=boost::archive::iterators::insert_linebreaks<boost::archive::iterators::base64_from_binary<boost::archive::iterators::transform_width<const char *,6,8,char>,char>,76,const char> ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/basic_text_oprimitive.ipp(33): while compiling class template member function 'void boost::archive::basic_text_oprimitive<std::wostream>::save_binary(const void *,size_t)' libs\serialization\src\basic_text_woprimitive.cpp(30) : see reference to class template instantiation 'boost::archive::basic_text_oprimitive<std::wostream>' being compiled compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\text_wiarchive.obj text_wiarchive.cpp compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\text_woarchive.obj text_woarchive.cpp compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\utf8_codecvt_facet.obj utf8_codecvt_facet.cpp compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\xml_wgrammar.obj xml_wgrammar.cpp C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2798) : warning C4996: 'std::_Equal1': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2783) : see declaration of 'std::_Equal1' c:\users\kaosun.earthgroove\downloads\temp\boost_1_58_0\libs\serialization\src\basic_xml_grammar.ipp(452) : see reference to class template instantiation 'bool std::equal<std::_String_iterator<std::_String_val<std::_Simple_types<wchar_t>>>,const char*>(_InIt1,_InIt1,_InIt2)' being compiled with [ _InIt1=std::_String_iterator<std::_String_val<std::_Simple_types<wchar_t>>> , _InIt2=const char * ] c:\users\kaosun.earthgroove\downloads\temp\boost_1_58_0\libs\serialization\src\basic_xml_grammar.ipp(438): while compiling class template member function 'void boost::archive::basic_xml_grammar<wchar_t>::init(std::basic_istream<wchar_t,std::char_traits<wchar_t>> &)' libs\serialization\src\xml_wgrammar.cpp(51) : see reference to class template instantiation 'boost::archive::basic_xml_grammar<wchar_t>' being compiled compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\xml_wiarchive.obj xml_wiarchive.cpp C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2132) : warning C4996: 'std::_Copy_impl': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2113) : see declaration of 'std::_Copy_impl' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/xml_wiarchive_impl.ipp(61) : see reference to class template instantiation '_OutIt std::copy<boost::archive::iterators::mb_from_wchar<std::_String_const_iterator<std::_String_val<std::_Simple_types<wchar_t>>>>,char*>(_InIt,_InIt,_OutIt)' being compiled with [ _OutIt=char * , _InIt=boost::archive::iterators::mb_from_wchar<std::_String_const_iterator<std::_String_val<std::_Simple_types<wchar_t>>>> ] C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2798) : warning C4996: 'std::_Equal1': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2783) : see declaration of 'std::_Equal1' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/basic_xml_iarchive.ipp(67) : see reference to class template instantiation 'bool std::equal<std::_String_iterator<std::_String_val<std::_Simple_types<wchar_t>>>,const char*>(_InIt1,_InIt1,_InIt2)' being compiled with [ _InIt1=std::_String_iterator<std::_String_val<std::_Simple_types<wchar_t>>> , _InIt2=const char * ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/basic_xml_iarchive.ipp(45): while compiling class template member function 'void boost::archive::basic_xml_iarchive<Archive>::load_end(const char *)' with [ Archive=boost::archive::xml_wiarchive ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/xml_wiarchive.hpp(64) : see reference to class template instantiation 'boost::archive::basic_xml_iarchive<Archive>' being compiled with [ Archive=boost::archive::xml_wiarchive ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/xml_wiarchive.hpp(146) : see reference to class template instantiation 'boost::archive::xml_wiarchive_impl<boost::archive::xml_wiarchive>' being compiled C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/iterators/mb_from_wchar.hpp(91) : warning C4996: 'wctomb': This function or variable may be unsafe. Consider using wctomb_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\stdlib.h(567) : see declaration of 'wctomb' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/iterators/mb_from_wchar.hpp(85): while compiling class template member function 'void boost::archive::iterators::mb_from_wchar<std::_String_const_iterator<std::_String_val<std::_Simple_types<wchar_t>>>>::fill(void)' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/iterators/mb_from_wchar.hpp(65) : see reference to class template instantiation 'void boost::archive::iterators::mb_from_wchar<std::_String_const_iterator<std::_String_val<std::_Simple_types<wchar_t>>>>::fill(void)' being compiled C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/xml_wiarchive_impl.ipp(56) : see reference to class template instantiation 'boost::archive::iterators::mb_from_wchar<std::_String_const_iterator<std::_String_val<std::_Simple_types<wchar_t>>>>' being compiled compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\debug\link-static\runtime-link-static\threading-multi\xml_woarchive.obj xml_woarchive.cpp C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2132) : warning C4996: 'std::_Copy_impl': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2113) : see declaration of 'std::_Copy_impl' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/xml_woarchive_impl.ipp(89) : see reference to class template instantiation '_OutIt std::copy<boost::archive::iterators::xml_escape<const wchar_t *>,boost::archive::iterators::ostream_iterator<wchar_t>>(_InIt,_InIt,_OutIt)' being compiled with [ _OutIt=boost::archive::iterators::ostream_iterator<wchar_t> , _InIt=boost::archive::iterators::xml_escape<const wchar_t *> ] C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/impl/xml_woarchive_impl.ipp(75): while compiling class template member function 'void boost::archive::xml_woarchive_impl<boost::archive::xml_woarchive>::save(const std::wstring &)' C:\Users\kaosun.EARTHGROOVE\Downloads\temp\boost_1_58_0\boost/archive/xml_woarchive.hpp(140) : see reference to class template instantiation 'boost::archive::xml_woarchive_impl<boost::archive::xml_woarchive>' being compiled C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xutility(2113) : see declaration of 'std::_Copy_impl' : : Snip : : compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\release\link-static\runtime-link-static\threading-multi\xml_oarchive.obj xml_oarchive.cpp .\boost/archive/iterators/mb_from_wchar.hpp(91) : warning C4996: 'wctomb': This function or variable may be unsafe. Consider using wctomb_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\stdlib.h(567) : see declaration of 'wctomb' .\boost/archive/iterators/mb_from_wchar.hpp(85): while compiling class template member function 'void boost::archive::iterators::mb_from_wchar<boost::archive::iterators::xml_escape<InputIterator>>::fill(void)' with [ InputIterator=const wchar_t * ] .\boost/archive/iterators/mb_from_wchar.hpp(65) : see reference to class template instantiation 'void boost::archive::iterators::mb_from_wchar<boost::archive::iterators::xml_escape<InputIterator>>::fill(void)' being compiled with [ InputIterator=const wchar_t * ] .\boost/archive/impl/xml_oarchive_impl.ipp(45) : see reference to class template instantiation 'boost::archive::iterators::mb_from_wchar<boost::archive::iterators::xml_escape<InputIterator>>' being compiled with [ InputIterator=const wchar_t * ] .\boost/archive/impl/xml_oarchive_impl.ipp(58) : see reference to class template instantiation 'void boost::archive::save_iterator<const _Elem*>(std::ostream &,InputIterator,InputIterator)' being compiled with [ _Elem=wchar_t , InputIterator=const wchar_t * ] .\boost/archive/impl/xml_oarchive_impl.ipp(54): while compiling class template member function 'void boost::archive::xml_oarchive_impl<boost::archive::xml_oarchive>::save(const std::wstring &)' .\boost/archive/xml_oarchive.hpp(123) : see reference to class template instantiation 'boost::archive::xml_oarchive_impl<boost::archive::xml_oarchive>' being compiled : : Snip : : compile-c-c++ bin.v2\libs\serialization\build\msvc-12.0\release\link-static\runtime-link-static\threading-multi\xml_wiarchive.obj xml_wiarchive.cpp .\boost/archive/iterators/mb_from_wchar.hpp(91) : warning C4996: 'wctomb': This function or variable may be unsafe. Consider using wctomb_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\stdlib.h(567) : see declaration of 'wctomb' .\boost/archive/iterators/mb_from_wchar.hpp(85): while compiling class template member function 'void boost::archive::iterators::mb_from_wchar<std::_String_const_iterator<std::_String_val<std::_Simple_types<wchar_t>>>>::fill(void)' .\boost/archive/iterators/mb_from_wchar.hpp(65) : see reference to class template instantiation 'void boost::archive::iterators::mb_from_wchar<std::_String_const_iterator<std::_String_val<std::_Simple_types<wchar_t>>>>::fill(void)' being compiled .\boost/archive/impl/xml_wiarchive_impl.ipp(56) : see reference to class template instantiation 'boost::archive::iterators::mb_from_wchar<std::_String_const_iterator<std::_String_val<std::_Simple_types<wchar_t>>>>' being compiled

2 2

[thread] Do we can a non backward compatible version with non-blocking futures?
by Vicente J. Botet Escriba 18 May '15

18 May '15

Hi, in Boost 1.58 I fixed some issues as the result of the async and future<T>:then() was not a blocking future as the documentation described. However the implementation is horrible and I suspect that it is subject to deadlocks. BTW, I added already some fixes on the develop branch. Sometime ago I started in a branch an implementation that don't use blocking futures [1]. Well the implementation is also horrible after making futures non-blocking, but less ;-) The problem is that now I have some issues with the executors :( Anyway, Gor has told me that with the blocking implementation he is unable to define await_suspend (using resumable functions) >It is just if .then returns a blocking future, I cannot subscribe a callback to .then in await_suspend. >await_suspend(f, cb) { > f.then(cb); >} &will block here preventing coroutine from suspending I don't know yet if he will reach to configure boost::future<T> on the non-blocking branch. My question is if the Boost community will accept (or even wants) a breaking change on a near release (when I would reach to fix the executors issues) including non-blocking futures instead of the current blocking futures. Best, Vicente [1] https://github.com/boostorg/thread/tree/feature/non_blocking_futures

1 0

Broken web site documentation link
by Bennet Fauber 18 May '15

18 May '15

>From this page, http://www.boost.org/doc/libs/1_58_0/tools/build/index.html there is a link called "Documentation" under the Boost Build graphic that purports to link to http://www.boost.org/doc/libs/1_58_0/tools/build/doc/html/index.html but clicking on that link yields the following web page: ========================== 404 Not Found File "/home/www/live.boost.org/common/code/../../doc/archives/boost_1_58_0/tools/build/doc/html/index.html" not found. Unable to find file. ========================== Sorry for posting to the wrong place is if this is not it. -- bennet

1 0

Boost Phoenix & language lambdas
by Robert Jones 16 May '15

16 May '15

I'm sure this has been asked before, and apologies in advance to the programming gods of Boost.Phoenix, but has Phoenix effectively been replaced by language lambdas, or are there still things for which Phoenix is the best answer? Thx, Rob.

3 2

Some strange boost headers errors
by alfonso santimone 15 May '15

15 May '15

Hi guys, i'm a boost newbie. I've got to include boost libraries in the include path of a VisualStudio 2012 project. When i try to compile i have all these errors. Every errors is related to missing headers ( boost ones and even standard Win ones ) and to synthax errors depending on missing headers i guess. Do someone have any idea on what's wrong here? I just post here a few lines of errors, but the other ones are all of the same kind Error 1 error C2061: syntax error : identifier 'boost' C:\boost_1_57_0\boost\core\ checked_delete.hpp 24 1 csound~ Error 2 error C2059: syntax error : ';' C:\boost_1_57_0\boost\core\checked_delete.hpp 24 1 csound~ Error 3 error C2449: found '{' at file scope (missing function header?) C:\boost_1_57_0\boost\core\checked_delete.hpp 25 1 csound~ Error 4 error C2059: syntax error : '}' C:\boost_1_57_0\boost\core\checked_delete.hpp 67 1 csound~ Error 5 error C2054: expected '(' to follow 'using' C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\cstddef 19 1 csound~ Error 6 error C2061: syntax error : identifier 'using' C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\cstddef 19 1 csound~ Error 7 error C2061: syntax error : identifier 'boost' C:\boost_1_57_0\boost\smart_ptr\detail\sp_nullptr_t.hpp 23 1 csound~ Error 8 error C2059: syntax error : ';' C:\boost_1_57_0\boost\smart_ptr\detail\sp_nullptr_t.hpp 23 1 csound~ Error 9 error C2449: found '{' at file scope (missing function header?) C:\boost_1_57_0\boost\smart_ptr\detail\sp_nullptr_t.hpp 24 1 csound~ Error 10 error C2059: syntax error : '}' C:\boost_1_57_0\boost\smart_ptr\detail\sp_nullptr_t.hpp 41 1 csound~ Error 11 error C2054: expected '(' to follow 'using' C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\cstdlib 19 1 csound~ Error 12 error C2061: syntax error : identifier 'using' C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\cstdlib 19 1 csound~ Error 13 error C2061: syntax error : identifier 'abort' C:\Program Files (x86)\Microsoft Visual Studio many thanks in advance bests alfonso www.elgallorojorecords.com soundcloud.com/alfonsosantimone www.facebook.com/alfonsosantimone

5 11

[flyweights] private constructor, friend access
by r＠primef.actor 15 May '15

15 May '15

Dear all, On a project of mine, I started to use Boost.Flyweight. I would like users of my class to only be able to instantiate objects of my class by using the Boost.Flyweight mechanism. For this, I make my class constructor private. However, when doing so the corresponding flyweight factory also cannot instantiate my class. What classes do I need to `friend` in order to make this work? Here's a small self-contained example of the problem: class X { public: int data() const { return m_data; } struct key_extractor { int operator()(const X& x) const { return x.data(); } } typedef boost::flyweights::flyweight < boost::flyweights::keyvalue < int, X, key_extractor > > flyweight; private: int m_data; X(int x) : m_data(x) {} // friend declarations should go here }; int main() { auto my_x = X::flyweight(42); return 0; } Kind regards, Raoul Wols

2 1

boost `help
by Uthpal Urubail 14 May '15

14 May '15

Experts, Is there a direct way in boost to group numbers by deviation (by given percentage)? Regards, UJ

3 2

Managed shared memory size restrictions
by Veranika Liaukevich 14 May '15

14 May '15

Hello everybody, Is there any restriction to the size of managed shared memory regions? Should it be in multiples of the page size? I did not manage to find any relevant information in the documentation, but managed_shared_memory creation and managed_shared_memory::grow sometimes fail with small memory sizes specified. Examples: 1) When I create a managed_shared_memory segment with size 40, the creation fails with interprocess_exception::library_error. 2) I created managed_shared_memory with initial size 1000, then increased the size by 24 bytes, I got this: /usr/include/boost/interprocess/mem_algo/rbtree_best_fit.hpp:514: void boost::interprocess::rbtree_best_fit<MutexFamily, VoidMutex, MemAlignment>::grow(boost::interprocess::rbtree_best_fit<MutexFamily, VoidMutex, MemAlignment>::size_type) [with MutexFamily = boost::interprocess::mutex_family; VoidPointer = boost::interprocess::offset_ptr<void>; long unsigned int MemAlignment = 0ul; boost::interprocess::rbtree_best_fit<MutexFamily, VoidMutex, MemAlignment>::size_type = long unsigned int]: Assertion `new_block->m_size >= BlockCtrlUnits' failed. Aborted (core dumped) I use boost 1.55.0 on Ubuntu 14.04 64bit. Code used for testing: #include <boost/interprocess/managed_shared_memory.hpp> const char *shmname = "MyBoostShmTest"; // Usage: ./progname [init-memory-size] [grow-memory-size] int main(int argc, char **argv) { using namespace boost::interprocess; struct shm_remove { shm_remove() { shared_memory_object::remove(shmname); } ~shm_remove(){ shared_memory_object::remove(shmname); } } remover; size_t size = atoi(argv[1]); size_t grow_size = atoi(argv[2]); { managed_shared_memory segment(create_only, shmname, size); } { managed_shared_memory::grow(shmname, grow_size); } return 0; } Thanks, Veranika

1 0

[bccl] how to use predefined concepts to restrict a template argument via sfinae
by Nick Stokes 13 May '15

13 May '15

The use case is from Boost Graph, but my question is a general one about Boost Concept Check Library: How to "restrict" a template class/function argument based on concepts. For instance, I want to overload functions based on Graph or VertexListGraph or similar refinement. template<class VertexListGraph, XXX > void foo( VertexListGraph& g ) {...} where XXX is somekind of SFINAE that leverages boost::VertexListGraphConcept. Thanks, Nick

2 1

[BGL] pull requests?
by Mads Jensen 13 May '15

13 May '15

Hi, I don't know if this is the right list to send this to. However, there is a fair amount of trivial pull requests for the Boost Graph Library. Most of which address small errors in the documentation. There hasn't been any activity in that repository since August last year. Can someone with write access please have a look at it? -- Med venlig hilsen / Kind regards, Mads Jensen Life holds no terrors when you have embraced the philosophy of flipism! -- Carl Barks (Walt Disney Comics & Stories 149)

1 0

Boost.Coroutine Debian package
by Konrad Zemek 13 May '15

13 May '15

Hey everyone, I have asked this question the person who introduced Boost.Coroutine in the Debian package (control files can be found in debian svn repository [1]) a few days ago but have not received a reply: Does anyone happen to know why - for Debian package - Boost.Coroutine is built as a static library only? Our project prefers dynamic linking, and we also need -fPIC since we're building shared libraries as well, yet Boost.Coroutine is one of two libraries (the other one being Boost.Exception) built only as a non-fPIC static version. I have modified the control files to enable building libboost_coroutine.so, and we're currently using it for our project seemingly without any problem, but it worries me that there must have been a reason for the special treatment of Boost.Coroutine package. And a "by the way" question if anyone happens to know, I'm curious why Debian unstable still provides Boost 1.55 as the newest version? [1] svn://anonscm.debian.org/pkg-boost/boost Konrad

1 0

[Geometry] warnings
by PB 12 May '15

12 May '15

Hello, Using Boost 1.58 on VC9 (MSVC++ 2008) compiling a small program generates warnings in the Geometry headers in Release and Debug modes. Please let me know if this is a Boost.Geometry issue or something I'm not doing correctly. The program source ================= #include <boost/geometry.hpp> #include <boost/geometry/geometries/geometries.hpp> #include <boost/geometry/geometries/point_xy.hpp> #include <boost/geometry/geometries/polygon.hpp> typedef boost::geometry::model::d2::point_xy<double> point; typedef boost::geometry::model::polygon<point,false> polygon; typedef boost::geometry::model::linestring<point> polyline; int main() { polygon green, blue; green.outer().push_back(point(-1.0, 1.0)); green.outer().push_back(point(1.0, 1.0)); green.outer().push_back(point(1.0, -1.0)); green.outer().push_back(point(-1.0, -1.0)); blue.outer().push_back(point(0.5, 0.5)); blue.outer().push_back(point(0.5, 1.5)); blue.outer().push_back(point(1.5, 1.5)); blue.outer().push_back(point(1.5, 0.5)); std::vector<polygon> output; boost::geometry::intersection(blue, green, output); } Warning summary ============== Warning 1 warning C4244: 'initializing' : conversion from 'const coordinate_type' to 'const promoted_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 96 Warning 2 warning C4244: 'initializing' : conversion from 'const coordinate_type' to 'const promoted_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 97 Warning 3 warning C4244: 'initializing' : conversion from 'const coordinate_type' to 'const promoted_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 98 Warning 4 warning C4244: 'initializing' : conversion from 'const coordinate_type' to 'const promoted_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 99 Warning 5 warning C4244: 'argument' : conversion from '__int64' to 'const double', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\algorithms\detail\recalculate.hpp 51 Warning 6 warning C4244: 'argument' : conversion from '__int64' to 'const double', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\algorithms\detail\recalculate.hpp 51 Warning 7 warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 88 Warning 8 warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 89 Warning 9 warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 91 Warning 10 warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 92 Warning 11 warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 93 Warning 12 warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data c:\releases\lib\boost\boost_1_58_0\include\boost\geometry\strategies\cartesian\side_by_triangle.hpp 94 Warnings in more detail =============== 1>------ Build started: Project: boost_geom_warnings, Configuration: Release Win32 ------ 1>Compiling... 1>main.cpp 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(96) : warning C4244: 'initializing' : conversion from 'const coordinate_type' to 'const promoted_type', possible loss of data 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(138) : see reference to function template instantiation 'PromotedType boost::geometry::strategy::side::side_by_triangle<>::side_value<CoordinateType,PromotedType,P1,P2,P,EpsPolicy>(const P1 &,const P2 &,const P &,EpsPolicy &)' being compiled 1> with 1> [ 1> PromotedType=promoted_type, 1> CoordinateType=coordinate_type, 1> P1=robust_point_type, 1> P2=robust_point_type, 1> P=robust_point_type, 1> EpsPolicy=boost::geometry::strategy::side::side_by_triangle<>::eps_policy<boost::geometry::math::detail::equals_factor_policy<promoted_type>> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(234) : see reference to function template instantiation 'PromotedType boost::geometry::strategy::side::side_by_triangle<>::compute_side_value<CoordinateType,PromotedType,AreAllIntegralCoordinates>::apply<P1,P2,P,boost::geometry::strategy::side::side_by_triangle<>::eps_policy<Policy>>(const P1 &,const P2 &,const P &,EpsPolicy &)' being compiled 1> with 1> [ 1> PromotedType=promoted_type, 1> CoordinateType=coordinate_type, 1> AreAllIntegralCoordinates=true, 1> P1=robust_point_type, 1> P2=robust_point_type, 1> P=robust_point_type, 1> Policy=boost::geometry::math::detail::equals_factor_policy<promoted_type>, 1> EpsPolicy=boost::geometry::strategy::side::side_by_triangle<>::eps_policy<boost::geometry::math::detail::equals_factor_policy<promoted_type>> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/point_is_spike_or_equal.hpp(51) : see reference to function template instantiation 'int boost::geometry::strategy::side::side_by_triangle<>::apply<Point1,Point2,Point3>(const P1 &,const P2 &,const P &)' being compiled 1> with 1> [ 1> Point1=robust_point_type, 1> Point2=robust_point_type, 1> Point3=robust_point_type, 1> P1=robust_point_type, 1> P2=robust_point_type, 1> P=robust_point_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/point_is_spike_or_equal.hpp(117) : see reference to function template instantiation 'bool boost::geometry::detail::point_is_spike_or_equal<robust_point_type,robust_point_type,robust_point_type>(const Point1 &,const Point2 &,const Point3 &)' being compiled 1> with 1> [ 1> Point1=robust_point_type, 1> Point2=robust_point_type, 1> Point3=robust_point_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/append_no_dups_or_spikes.hpp(95) : see reference to function template instantiation 'bool boost::geometry::detail::point_is_spike_or_equal<Point,boost::geometry::model::d2::point_xy<CoordinateType>,boost::geometry::model::d2::point_xy<CoordinateType>,RobustPolicy>(const Point1 &,const Point2 &,const Point3 &,const RobustPolicy &)' being compiled 1> with 1> [ 1> Point=point_type, 1> CoordinateType=double, 1> RobustPolicy=rescale_policy_type, 1> Point1=point_type, 1> Point2=boost::geometry::model::d2::point_xy<double>, 1> Point3=boost::geometry::model::d2::point_xy<double> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/traverse.hpp(289) : see reference to function template instantiation 'void boost::geometry::detail::overlay::append_no_dups_or_spikes<ring_type,Point,RobustPolicy>(Range &,const Point &,const RobustPolicy &)' being compiled 1> with 1> [ 1> Point=point_type, 1> RobustPolicy=rescale_policy_type, 1> Range=ring_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/overlay.hpp(232) : see reference to function template instantiation 'void boost::geometry::detail::overlay::traverse<Reverse1,Reverse2,Geometry1,Geometry2>::apply<RobustPolicy,container_type,ring_container_type>(const Geometry1 &,const Geometry2 &,boost::geometry::detail::overlay::operation_type,const RobustPolicy &,Turns &,Rings &)' being compiled 1> with 1> [ 1> Reverse1=true, 1> Reverse2=true, 1> Geometry1=polygon, 1> Geometry2=polygon, 1> RobustPolicy=rescale_policy_type, 1> Turns=container_type, 1> Rings=ring_container_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/intersection/interface.hpp(57) : see reference to function template instantiation 'OutputIterator boost::geometry::detail::overlay::overlay<Geometry1,Geometry2,Reverse1,Reverse2,ReverseOut,GeometryOut,Direction>::apply<RobustPolicy,std::back_insert_iterator<_Container>,Strategy>(const Geometry1 &,const Geometry2 &,const RobustPolicy &,OutputIterator,const Strategy &)' being compiled 1> with 1> [ 1> OutputIterator=std::back_insert_iterator<std::vector<polygon>>, 1> Geometry1=polygon, 1> Geometry2=polygon, 1> Reverse1=true, 1> Reverse2=true, 1> ReverseOut=true, 1> GeometryOut=OneOut, 1> Direction=overlay_intersection, 1> RobustPolicy=rescale_policy_type, 1> _Container=std::vector<polygon>, 1> Strategy=boost::geometry::strategy_intersection<boost::geometry::cartesian_tag,polygon,polygon,boost::geometry::model::d2::point_xy<double>,rescale_policy_type> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/intersection/interface.hpp(138) : see reference to function template instantiation 'bool boost::geometry::dispatch::intersection<Geometry1,Geometry2>::apply<rescale_policy_type,GeometryOut,boost::geometry::strategy_intersection<Tag,Geometry1,Geometry2,IntersectionPoint,RobustPolicy>>(const Geometry1 &,const Geometry2 &,const RobustPolicy &,GeometryOut &,const Strategy &)' being compiled 1> with 1> [ 1> Geometry1=polygon, 1> Geometry2=polygon, 1> GeometryOut=std::vector<polygon>, 1> Tag=boost::geometry::cartesian_tag, 1> IntersectionPoint=boost::geometry::model::d2::point_xy<double>, 1> RobustPolicy=rescale_policy_type, 1> Strategy=boost::geometry::strategy_intersection<boost::geometry::cartesian_tag,polygon,polygon,boost::geometry::model::d2::point_xy<double>,rescale_policy_type> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/intersection/interface.hpp(302) : see reference to function template instantiation 'bool boost::geometry::resolve_variant::intersection<Geometry1,Geometry2>::apply<GeometryOut>(const Geometry1 &,const Geometry2 &,GeometryOut &)' being compiled 1> with 1> [ 1> Geometry1=polygon, 1> Geometry2=polygon, 1> GeometryOut=std::vector<polygon> 1> ] 1> .\main.cpp(24) : see reference to function template instantiation 'bool boost::geometry::intersection<polygon,polygon,std::vector<_Ty>>(const Geometry1 &,const Geometry2 &,GeometryOut &)' being compiled 1> with 1> [ 1> _Ty=polygon, 1> Geometry1=polygon, 1> Geometry2=polygon, 1> GeometryOut=std::vector<polygon> 1> ] 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(97) : warning C4244: 'initializing' : conversion from 'const coordinate_type' to 'const promoted_type', possible loss of data 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(98) : warning C4244: 'initializing' : conversion from 'const coordinate_type' to 'const promoted_type', possible loss of data 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(99) : warning C4244: 'initializing' : conversion from 'const coordinate_type' to 'const promoted_type', possible loss of data 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/recalculate.hpp(51) : warning C4244: 'argument' : conversion from '__int64' to 'const double', possible loss of data 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/recalculate.hpp(224) : see reference to function template instantiation 'void boost::geometry::detail::recalculate::recalculate_point<Dimension>::apply<Geometry1,Geometry2,Strategy>(Point1 &,const Point2 &,const Strategy &)' being compiled 1> with 1> [ 1> Dimension=2, 1> Geometry1=boost::geometry::model::d2::point_xy<double>, 1> Geometry2=boost::geometry::model::d2::point_xy<double>, 1> Strategy=rescale_policy_type, 1> Point1=boost::geometry::model::d2::point_xy<double>, 1> Point2=boost::geometry::model::d2::point_xy<double> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/handle_tangencies.hpp(109) : see reference to function template instantiation 'void boost::geometry::recalculate<boost::geometry::model::d2::point_xy<CoordinateType>,boost::geometry::model::d2::point_xy<CoordinateType>,const RobustPolicy>(Geometry1 &,const Geometry2 &,const Strategy &)' being compiled 1> with 1> [ 1> CoordinateType=double, 1> RobustPolicy=rescale_policy_type, 1> Geometry1=boost::geometry::model::d2::point_xy<double>, 1> Geometry2=boost::geometry::model::d2::point_xy<double>, 1> Strategy=rescale_policy_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/handle_tangencies.hpp(96) : while compiling class template member function 'void boost::geometry::detail::overlay::sort_in_cluster<TurnPoints,Indexed,Geometry1,Geometry2,RobustPolicy,Reverse1,Reverse2,Strategy>::get_situation_map(const Indexed &,const Indexed &,boost::geometry::model::d2::point_xy<CoordinateType> &,boost::geometry::model::d2::point_xy<CoordinateType> &,boost::geometry::model::d2::point_xy<CoordinateType> &,boost::geometry::model::d2::point_xy<CoordinateType> &,boost::geometry::model::d2::point_xy<CoordinateType> &,boost::geometry::model::d2::point_xy<CoordinateType> &) const' 1> with 1> [ 1> TurnPoints=container_type, 1> Indexed=indexed_turn_operation, 1> Geometry1=polygon, 1> Geometry2=polygon, 1> RobustPolicy=const rescale_policy_type, 1> Reverse1=true, 1> Reverse2=true, 1> Strategy=boost::geometry::strategy::side::side_by_triangle<>, 1> CoordinateType=double 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/handle_tangencies.hpp(742) : see reference to class template instantiation 'boost::geometry::detail::overlay::sort_in_cluster<TurnPoints,Indexed,Geometry1,Geometry2,RobustPolicy,Reverse1,Reverse2,Strategy>' being compiled 1> with 1> [ 1> TurnPoints=container_type, 1> Indexed=indexed_turn_operation, 1> Geometry1=polygon, 1> Geometry2=polygon, 1> RobustPolicy=const rescale_policy_type, 1> Reverse1=true, 1> Reverse2=true, 1> Strategy=boost::geometry::strategy::side::side_by_triangle<> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/enrich_intersection_points.hpp(290) : see reference to function template instantiation 'void boost::geometry::detail::overlay::handle_cluster<IndexType,true,true,nc_iterator,TurnPoints,Geometry1,Geometry2,const RobustPolicy,Strategy>(Iterator,Iterator,TurnPoints &,boost::geometry::detail::overlay::operation_type,const Geometry1 &,const Geometry2 &,RobustPolicy &,const Strategy &)' being compiled 1> with 1> [ 1> IndexType=indexed_turn_operation, 1> TurnPoints=container_type, 1> Geometry1=polygon, 1> Geometry2=polygon, 1> RobustPolicy=rescale_policy_type, 1> Strategy=boost::geometry::strategy::side::side_by_triangle<>, 1> Iterator=nc_iterator 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/enrich_intersection_points.hpp(533) : see reference to function template instantiation 'void boost::geometry::detail::overlay::enrich_sort<indexed_turn_operation,true,true,_Ty2,TurnPoints,Geometry1,Geometry2,RobustPolicy,Strategy>(Container &,TurnPoints &,boost::geometry::detail::overlay::operation_type,const Geometry1 &,const Geometry2 &,const RobustPolicy &,const Strategy &)' being compiled 1> with 1> [ 1> _Ty2=std::vector<indexed_turn_operation>, 1> TurnPoints=container_type, 1> Geometry1=polygon, 1> Geometry2=polygon, 1> RobustPolicy=rescale_policy_type, 1> Strategy=boost::geometry::strategy::side::side_by_triangle<>, 1> Container=std::vector<indexed_turn_operation> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/overlay.hpp(215) : see reference to function template instantiation 'void boost::geometry::enrich_intersection_points<true,true,container_type,Geometry1,Geometry2,RobustPolicy,boost::geometry::strategy::side::side_by_triangle<>>(TurnPoints &,boost::geometry::detail::overlay::operation_type,const Geometry1 &,const Geometry2 &,const RobustPolicy &,const Strategy &)' being compiled 1> with 1> [ 1> Geometry1=polygon, 1> Geometry2=polygon, 1> RobustPolicy=rescale_policy_type, 1> TurnPoints=container_type, 1> Strategy=boost::geometry::strategy::side::side_by_triangle<> 1> ] 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/recalculate.hpp(51) : warning C4244: 'argument' : conversion from '__int64' to 'const double', possible loss of data 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/recalculate.hpp(52) : see reference to function template instantiation 'void boost::geometry::detail::recalculate::recalculate_point<Dimension>::apply<Point1,Point2,Strategy>(Point1 &,const Point2 &,const Strategy &)' being compiled 1> with 1> [ 1> Dimension=1, 1> Point1=boost::geometry::model::d2::point_xy<double>, 1> Point2=boost::geometry::model::d2::point_xy<double>, 1> Strategy=rescale_policy_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/recalculate.hpp(224) : see reference to function template instantiation 'void boost::geometry::detail::recalculate::recalculate_point<Dimension>::apply<Geometry1,Geometry2,Strategy>(Point1 &,const Point2 &,const Strategy &)' being compiled 1> with 1> [ 1> Dimension=2, 1> Geometry1=boost::geometry::model::d2::point_xy<double>, 1> Geometry2=boost::geometry::model::d2::point_xy<double>, 1> Strategy=rescale_policy_type, 1> Point1=boost::geometry::model::d2::point_xy<double>, 1> Point2=boost::geometry::model::d2::point_xy<double> 1> ] 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(88) : warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(138) : see reference to function template instantiation 'PromotedType boost::geometry::strategy::side::side_by_triangle<CalculationType>::side_value<CoordinateType,PromotedType,P1,P2,P,EpsPolicy>(const P1 &,const P2 &,const P &,EpsPolicy &)' being compiled 1> with 1> [ 1> PromotedType=promoted_type, 1> CalculationType=coordinate_type, 1> CoordinateType=coordinate_type, 1> P1=robust_point_type, 1> P2=robust_point_type, 1> P=robust_point_type, 1> EpsPolicy=boost::geometry::strategy::side::side_by_triangle<coordinate_type>::eps_policy<boost::geometry::math::detail::equals_factor_policy<promoted_type>> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(234) : see reference to function template instantiation 'PromotedType boost::geometry::strategy::side::side_by_triangle<CalculationType>::compute_side_value<CoordinateType,PromotedType,AreAllIntegralCoordinates>::apply<P1,P2,P,boost::geometry::strategy::side::side_by_triangle<CalculationType>::eps_policy<Policy>>(const P1 &,const P2 &,const P &,EpsPolicy &)' being compiled 1> with 1> [ 1> PromotedType=promoted_type, 1> CalculationType=coordinate_type, 1> CoordinateType=coordinate_type, 1> AreAllIntegralCoordinates=true, 1> P1=robust_point_type, 1> P2=robust_point_type, 1> P=robust_point_type, 1> Policy=boost::geometry::math::detail::equals_factor_policy<promoted_type>, 1> EpsPolicy=boost::geometry::strategy::side::side_by_triangle<coordinate_type>::eps_policy<boost::geometry::math::detail::equals_factor_policy<promoted_type>> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/cart_intersect.hpp(140) : see reference to function template instantiation 'int boost::geometry::strategy::side::side_by_triangle<CalculationType>::apply<RobustPoint,RobustPoint,RobustPoint>(const P1 &,const P2 &,const P &)' being compiled 1> with 1> [ 1> CalculationType=coordinate_type, 1> RobustPoint=robust_point_type, 1> P1=robust_point_type, 1> P2=robust_point_type, 1> P=robust_point_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/cart_intersect.hpp(107) : see reference to function template instantiation 'boost::tuples::tuple<T0,T1> boost::geometry::strategy::intersection::relate_cartesian_segments<Policy,CalculationType>::apply<Segment1,Segment2,RobustPolicy,robust_point_type>(const Segment1 &,const Segment2 &,const RobustPolicy &,const RobustPoint &,const RobustPoint &,const RobustPoint &,const RobustPoint &)' being compiled 1> with 1> [ 1> T0=boost::geometry::segment_intersection_points<boost::geometry::model::d2::point_xy<double>,boost::geometry::segment_ratio_type<boost::geometry::model::d2::point_xy<double>,rescale_policy_type>::type>, 1> T1=boost::geometry::policies::relate::segments_direction::return_type, 1> Policy=boost::geometry::policies::relate::segments_tupled<boost::geometry::policies::relate::segments_intersection_points<boost::geometry::segment_intersection_points<boost::geometry::model::d2::point_xy<double>,boost::geometry::segment_ratio_type<boost::geometry::model::d2::point_xy<double>,rescale_policy_type>::type>>,boost::geometry::policies::relate::segments_direction>, 1> CalculationType=void, 1> Segment1=boost::geometry::model::referring_segment<const boost::geometry::model::d2::point_xy<double>>, 1> Segment2=boost::geometry::model::referring_segment<const boost::geometry::model::d2::point_xy<double>>, 1> RobustPolicy=rescale_policy_type, 1> RobustPoint=robust_point_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/get_turn_info_helpers.hpp(220) : see reference to function template instantiation 'boost::tuples::tuple<T0,T1> boost::geometry::strategy::intersection::relate_cartesian_segments<Policy,CalculationType>::apply<boost::geometry::model::referring_segment<ConstOrNonConstPoint>,boost::geometry::model::referring_segment<ConstOrNonConstPoint>,RobustPolicy>(const Segment1 &,const Segment2 &,const RobustPolicy &)' being compiled 1> with 1> [ 1> T0=boost::geometry::segment_intersection_points<boost::geometry::model::d2::point_xy<double>,boost::geometry::segment_ratio_type<boost::geometry::model::d2::point_xy<double>,rescale_policy_type>::type>, 1> T1=boost::geometry::policies::relate::segments_direction::return_type, 1> Policy=boost::geometry::policies::relate::segments_tupled<boost::geometry::policies::relate::segments_intersection_points<boost::geometry::segment_intersection_points<boost::geometry::model::d2::point_xy<double>,boost::geometry::segment_ratio_type<boost::geometry::model::d2::point_xy<double>,rescale_policy_type>::type>>,boost::geometry::policies::relate::segments_direction>, 1> CalculationType=void, 1> ConstOrNonConstPoint=const boost::geometry::model::d2::point_xy<double>, 1> RobustPolicy=rescale_policy_type, 1> Segment1=boost::geometry::model::referring_segment<const boost::geometry::model::d2::point_xy<double>>, 1> Segment2=boost::geometry::model::referring_segment<const boost::geometry::model::d2::point_xy<double>> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/get_turn_info_helpers.hpp(214) : while compiling class template member function 'boost::geometry::detail::overlay::intersection_info<Point1,Point2,TurnPoint,RobustPolicy>::intersection_info(const Point1 &,const Point1 &,const Point1 &,const Point2 &,const Point2 &,const Point2 &,const RobustPolicy &)' 1> with 1> [ 1> Point1=boost::geometry::model::d2::point_xy<double>, 1> Point2=boost::geometry::model::d2::point_xy<double>, 1> TurnPoint=boost::geometry::model::d2::point_xy<double>, 1> RobustPolicy=rescale_policy_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/get_turn_info.hpp(926) : see reference to class template instantiation 'boost::geometry::detail::overlay::intersection_info<Point1,Point2,TurnPoint,RobustPolicy>' being compiled 1> with 1> [ 1> Point1=boost::geometry::model::d2::point_xy<double>, 1> Point2=boost::geometry::model::d2::point_xy<double>, 1> TurnPoint=boost::geometry::model::d2::point_xy<double>, 1> RobustPolicy=rescale_policy_type 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/get_turns.hpp(297) : see reference to function template instantiation 'OutputIterator boost::geometry::detail::overlay::get_turn_info<AssignPolicy>::apply<boost::geometry::model::d2::point_xy<CoordinateType>,boost::geometry::model::d2::point_xy<CoordinateType>,turn_info,RobustPolicy,std::back_insert_iterator<_Container>>(const Point1 &,const Point1 &,const Point1 &,const Point2 &,const Point2 &,const Point2 &,bool,bool,bool,bool,const TurnInfo &,const RobustPolicy &,OutputIterator)' being compiled 1> with 1> [ 1> OutputIterator=std::back_insert_iterator<container_type>, 1> AssignPolicy=boost::geometry::detail::overlay::assign_null_policy, 1> CoordinateType=double, 1> RobustPolicy=rescale_policy_type, 1> _Container=container_type, 1> Point1=boost::geometry::model::d2::point_xy<double>, 1> Point2=boost::geometry::model::d2::point_xy<double>, 1> TurnInfo=turn_info 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/get_turns.hpp(426) : see reference to function template instantiation 'bool boost::geometry::detail::get_turns::get_turns_in_sections<Geometry1,Geometry2,Reverse1,Reverse2,Section1,Section2,TurnPolicy>::apply<Turns,RobustPolicy,InterruptPolicy>(int,const Geometry1 &,const Section1 &,int,const Geometry2 &,const Section2 &,bool,const RobustPolicy &,Turns &,InterruptPolicy &)' being compiled 1> with 1> [ 1> Geometry1=polygon, 1> Geometry2=polygon, 1> Reverse1=true, 1> Reverse2=true, 1> Section1=boost::geometry::section<box_type,2>, 1> Section2=boost::geometry::section<box_type,2>, 1> TurnPolicy=TurnPolicy, 1> Turns=container_type, 1> RobustPolicy=rescale_policy_type, 1> InterruptPolicy=boost::geometry::detail::get_turns::no_interrupt_policy 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/partition.hpp(641) : see reference to function template instantiation 'bool boost::geometry::detail::get_turns::section_visitor<Geometry1,Geometry2,Reverse1,Reverse2,Turns,TurnPolicy,RobustPolicy,InterruptPolicy>::apply<boost::geometry::section<Box,DimensionCount>>(const Section &,const Section &)' being compiled 1> with 1> [ 1> Geometry1=polygon, 1> Geometry2=polygon, 1> Reverse1=true, 1> Reverse2=true, 1> Turns=container_type, 1> TurnPolicy=TurnPolicy, 1> RobustPolicy=rescale_policy_type, 1> InterruptPolicy=boost::geometry::detail::get_turns::no_interrupt_policy, 1> Box=box_type, 1> DimensionCount=2, 1> Section=boost::geometry::section<box_type,2> 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/get_turns.hpp(485) : see reference to function template instantiation 'void boost::geometry::partition<Box,ExpandPolicy1,OverlapsPolicy1>::apply<sections_type,sections_type,boost::geometry::detail::get_turns::section_visitor<Geometry1,Geometry2,Reverse1,Reverse2,Turns,TurnPolicy,RobustPolicy,InterruptPolicy>>(const InputCollection1 &,const InputCollection2 &,VisitPolicy &,size_t,VisitBoxPolicy)' being compiled 1> with 1> [ 1> Box=box_type, 1> ExpandPolicy1=boost::geometry::detail::section::get_section_box, 1> OverlapsPolicy1=boost::geometry::detail::section::overlaps_section_box, 1> Geometry1=polygon, 1> Geometry2=polygon, 1> Reverse1=true, 1> Reverse2=true, 1> Turns=container_type, 1> TurnPolicy=TurnPolicy, 1> RobustPolicy=rescale_policy_type, 1> InterruptPolicy=boost::geometry::detail::get_turns::no_interrupt_policy, 1> InputCollection1=sections_type, 1> InputCollection2=sections_type, 1> VisitPolicy=boost::geometry::detail::get_turns::section_visitor<polygon,polygon,true,true,container_type,TurnPolicy,rescale_policy_type,boost::geometry::detail::get_turns::no_interrupt_policy>, 1> VisitBoxPolicy=boost::geometry::detail::partition::visit_no_policy 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/get_turns.hpp(1002) : see reference to function template instantiation 'void boost::geometry::detail::get_turns::get_turns_generic<Geometry1,Geometry2,Reverse1,Reverse2,TurnPolicy>::apply<RobustPolicy,Turns,InterruptPolicy>(int,const Geometry1 &,int,const Geometry2 &,const RobustPolicy &,Turns &,InterruptPolicy &)' being compiled 1> with 1> [ 1> Geometry1=polygon, 1> Geometry2=polygon, 1> Reverse1=true, 1> Reverse2=true, 1> TurnPolicy=TurnPolicy, 1> RobustPolicy=rescale_policy_type, 1> Turns=container_type, 1> InterruptPolicy=boost::geometry::detail::get_turns::no_interrupt_policy 1> ] 1> c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/algorithms/detail/overlay/overlay.hpp(203) : see reference to function template instantiation 'void boost::geometry::get_turns<true,true,boost::geometry::detail::overlay::assign_null_policy,Geometry1,Geometry2,RobustPolicy,container_type,boost::geometry::detail::get_turns::no_interrupt_policy>(const Geometry1 &,const Geometry2 &,const RobustPolicy &,Turns &,InterruptPolicy &)' being compiled 1> with 1> [ 1> Geometry1=polygon, 1> Geometry2=polygon, 1> RobustPolicy=rescale_policy_type, 1> Turns=container_type, 1> InterruptPolicy=boost::geometry::detail::get_turns::no_interrupt_policy 1> ] 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(89) : warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(91) : warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(92) : warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(93) : warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data 1>c:\releases\lib\boost\boost_1_58_0\include\boost/geometry/strategies/cartesian/side_by_triangle.hpp(94) : warning C4244: 'initializing' : conversion from '__int64' to 'const coordinate_type', possible loss of data 1>Build log was saved at "file://c:\cpp\boost_geom_warnings\Release\BuildLog.htm" 1>boost_geom_warnings - 0 error(s), 12 warning(s) ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

2 2

Re: [Boost-users] boost::intrusive::slist push_back() => error: static assertion failed:
by Jonas Printzén 11 May '15

11 May '15

Mail-list failed to send me the reply from Ion, attempting a reply anyways... *(mail-list owner, what i do wrong?)* Thanx Ion. I got it to work as you suggested. Found old gtest - loggs that confirmed that the cache_last option wasn't needed in old code so this must be a change . Oh, and yes. uint64_t... :-) .. yes I modified the code after cut-paste. The docs for 1.55 intrusive slist under "Using base hooks <http://www.boost.org/doc/libs/1_55_0/doc/html/intrusive/usage.html#intrusiv…>" shows example with push_back() without mentioning cache_last. Mabey it should be push_front() in that example? Nifty to get to pick and choose level of overhead :-) /Jonas

2 1

[range] no matching function for call to make_begin_strided_iterator?
by Oliver Kowalke 11 May '15

11 May '15

Hi, if the test app below does not use adaptor strided in the for-range loop it works. If the adaptors is used the app fails with: ../../../../../boost/range/adaptor/strided.hpp: In instantiation of ‘boost::range_detail::strided_range<Rng, Category>::strided_range(Difference, Rng&) [with Difference = int; Rng = foo::X<int>; Category = boost::iterators::single_pass_traversal_tag]’: ../../../../../boost/range/adaptor/strided.hpp:656:54: required from ‘boost::range_detail::strided_range<Rng> boost::range_detail::operator|(Rng&, const boost::range_detail::strided_holder<Difference>&) [with Rng = foo::X<int>; Difference = int; typename boost::iterators::pure_iterator_traversal<typename boost::range_iterator<C>::type>::type = boost::iterators::single_pass_traversal_tag]’ fibonacci.cpp:188:50: required from here ../../../../../boost/range/adaptor/strided.hpp:631:34: error: no matching function for call to ‘make_begin_strided_iterator(foo::X<int>&, int&, boost::mpl::eval_if<boost::is_convertible<std::input_iterator_tag, boost::iterators::incrementable_traversal_tag>, boost::mpl::identity<std::input_iterator_tag>, boost::iterators::detail::old_category_to_traversal<std::input_iterator_tag> >::type)’ >::type()), Could you give me a hint what is missing? thx, Oliver #include <iostream> #include <iterator> #include <vector> #include <boost/range.hpp> #include <boost/range/adaptor/strided.hpp> namespace foo { template< typename T > class X { private: typedef std::vector< T > vec_t; vec_t vec_; public: X( vec_t const& vec) : vec_( vec) { } class iterator : public std::iterator< std::input_iterator_tag, T > { private: X * x_; typename vec_t::iterator i_; public: typedef typename iterator::pointer pointer_t; typedef typename iterator::reference reference_t; iterator() : x_( 0), i_() {} explicit iterator( X * x) : x_( x), i_( x_->vec_.begin() ) {} iterator( iterator const& other) : x_( other.x_), i_( other.i_) {} iterator & operator=( iterator const& other) { if ( this == & other) return * this; x_ = other.x_; i_ = other.i_; return * this; } bool operator==( iterator const& other) const { return other.x_ == x_ && other.i_ == i_; } bool operator!=( iterator const& other) const { return other.x_ != x_ || other.i_ != i_; } iterator & operator++() { ++i_; return * this; } iterator operator++( int) { i_++; return * this; } reference_t operator*() const { return * i_; } pointer_t operator->() const { return & ( * i_); } }; class const_iterator : public std::iterator< std::input_iterator_tag, const T > { private: X * x_; typename vec_t::const_iterator i_; public: typedef typename iterator::pointer pointer_t; typedef typename iterator::reference reference_t; const_iterator() : x_( 0), i_() {} explicit const_iterator( X * x) : x_( x), i_( x_->vec_.begin() ) {} const_iterator( const_iterator const& other) : x_( other.x_), i_( other.i_) {} const_iterator & operator=( const_iterator const& other) { if ( this == & other) return * this; x_ = other.x_; i_ = other.i_; return * this; } bool operator==( const_iterator const& other) const { return other.x_ == x_ && other.i_ == i_; } bool operator!=( const_iterator const& other) const { return other.x_ != x_ || other.i_ != i_; } const_iterator & operator++() { ++i_; return * this; } const_iterator operator++( int) { i_++; return * this; } reference_t operator*() const { return * i_; } pointer_t operator->() const { return & ( * i_); } }; friend class iterator; friend class const_iterator; }; template< typename T > typename X< T >::iterator range_begin( X< T > & c) { return typename X< T >::iterator( & c); } template< typename T > typename X< T >::const_iterator range_begin( X< T > const& c) { return typename X< T >::const_iterator( & c); } template< typename T > typename X< T >::iterator range_end( X< T > &) { return typename X< T >::iterator(); } template< typename T > typename X< T >::const_iterator range_end( X< T > const&) { return typename X< T >::const_iterator(); } template< typename T > typename X< T >::iterator begin( X< T > & c) { return boost::begin( c); } template< typename T > typename X< T >::const_iterator begin( X< T > const& c) { return boost::begin( c); } template< typename T > typename X< T >::iterator end( X< T > & c) { return boost::end( c); } template< typename T > typename X< T >::const_iterator end( X< T > const& c) { return boost::end( c); } } namespace boost { template< typename T > struct range_mutable_iterator< foo::X< T > > { typedef typename foo::X< T >::iterator type; }; template< typename T > struct range_const_iterator< foo::X< T > > { typedef typename foo::X< T >::const_iterator type; }; } int main() { std::vector< int > vec = { 1,2,3,4,5,6,7,8,9,10 }; auto x = foo::X< int >( vec); for (auto i : x | boost::adaptors::strided( 2) ) std::cout << i << " "; std::cout << '\n'; }

2 1

boost::intrusive::slist push_back() => error: static assertion failed: (cache_last)
by Jonas Printzén 09 May '15

09 May '15

Hi All! First post... Attempt switching to intrusive slist for efficiency, the following example is simply cut-paste from docs. Won't compile! g++ 4.9.1 complains as inlined in code below. #include <boost/intrusive/slist.hpp> using namespace boost::intrusive; struct point : slist_base_hook<> { int64_t x,y; }; using points = slist<point>; int main() { points plist; point p1,p2,p3; ACCEPT( 0U == plist.size() ); plist.push_back( p1 ); // => error: static assertion failed: (cache_last) ACCEPT( 1U == plist.size() ); } The code is from the docs of my version (1.55) and im pretty sure this or similar worked before. (1.54 i think) Please help, what am I missing?

2 1

Re: [Boost-users] lexical_cast between double and string slow in Visual Studio 2013
by David Roberts 07 May '15

07 May '15

> That issue is unknown. I'd really appreciate the investigation. I have done some more investigation, and there are two factors that only cause the slowness when they both occur together. > Try excluding the lexical_cast from test, I have a feeling that this is only MSVC related issue: > > #include <sstream> > #include <string> > > int main (int, char **) > { > for (double count = 0.0; count < 1000000.0; count += 1.41) > { > std::stringstream ss; > ss << count; > std::string result = std::move(ss.str()); > ss.str(std::string()); > > ss << result; > ss >> count; > } > > return 0; > } > Running your test program does not exhibit the problem. It runs in around 3 seconds on my machine when built with either Visual Studio 2010 or Visual Studio 2013. However, changing it very slightly to match more closely what lexical_cast does internally does recreate the problem: #include <sstream> #include <string> int main (int, char **) { for (double count = 0.0; count < 1000000.0; count += 1.41) { std::stringstream ss; ss.unsetf(std::ios::skipws); ss.precision(17); ss << count; std::string result = std::move(ss.str()); ss.str(std::string()); ss << result; ss >> count; } return 0; } The effect of setting the precision to 17 is that lots of 9s appear in the string representations. (The number 17 is what boost::detail::lcast_get_precision(double*) chooses.) Without the precision call the contents of the string called result start off like this: 0 1.41 2.82 4.23 5.64 7.05 8.46 9.87 11.28 12.69 With precision set to 17 they start off like this: 0 1.4099999999999999 2.8199999999999998 4.2299999999999995 5.6399999999999997 7.0499999999999998 8.4599999999999991 9.8699999999999992 11.279999999999999 12.69 This happens for both Visual Studio 2010 and Visual Studio 2013. Then the next difference is that Visual Studio 2013 spends a lot longer handling all the extra 9s. Changing the program so that the double is converted to a string using std::stringstream without a precision call and then back to double using lexical_cast takes about 3 seconds for both Visual Studio 2010 and Visual Studio 2013. It is the combination of having all the extra 9s to parse and using Visual Studio 2013 that makes the test using lexical_cast to go both ways slow. Both Visual Studio 2010 and Visual Studio 2013 do the conversion by calling std::num_get<char,std::istreambuf_iterator<char,std::char_traits<char> > >::do_get() which then calls a function called _Stodx() which is implemented in xstod.c. This function is very different for the two versions. In Visual Studio 2010 it's a relatively thin wrapper around the C function strtod(). In Visual Studio 2013 _Stodx() has got a completely new implementation that's generated by #including xxstod.h with some macros defined. The original C function strtod() is much faster than the new _Stodx() when there are lots of 9s at the end of the strings being parsed. This modification to the program: #include <sstream> #include <string> #include <stdlib.h> int main (int, char **) { for (double count = 0.0; count < 1000000.0; count += 1.41) { std::stringstream ss; ss.unsetf(std::ios::skipws); ss.precision(17); ss << count; std::string result = std::move(ss.str()); ss.str(std::string()); ss << result; char *endptr; count = strtod(ss.str().c_str(), &endptr); } return 0; } has a runtime of about 3 seconds even though it's got to cope with all the 9s. I guess only someone from Microsoft or Dinkumware could comment on why _Stodx() was reimplemented. But the other thing is that by setting precision to 17 lexical_cast is bloating the string representations of the doubles with lots of 9s in both Visual Studio 2010 and Visual Studio 2013. Setting precision to 15 instead prevents this, and makes the original test run faster even with Visual Studio 2013 (about 4 seconds rather than 10). Regards, David

5 4

[MultiIndex] getting the index from set::lower_bound() iterator (or a replacement/extension)
by U.Mutlu 07 May '15

07 May '15

Hi, I need a container like std::set which delivers also the index when using the member function lower_bound(). IMO std::set lacks this important functionality. I cannot use std::distance(myset.begin(), it), because that is very slow as it walks again all the items from the beginning. Can boost MultiIndex be used for this, or any other alternatives/workarounds? Here's a demonstration of what I need: struct TS { /*...*/ }; set<TS> myset; TS S(/*...*/); auto it = myset.lower_bound(S); if (it != myset.end()) { size_t ix = ...howto get the index, ie. the rank?... //... } -- Thx Uenal

3 2

boost container help
by Uthpal Urubail 07 May '15

07 May '15

Experts, I am looking for help on a container where I could group the objects having similar properties Ex: struct phyProp { unsigned int color; double height; double weight; std::string location; }; Can I use boost for grouping the objects having same property? [With tolerance?] Any help is highly appreciated. Regards, UJ

3 2

error: type/value mismatch at argument 1 in template parameter
by Lane 06 May '15

06 May '15

bounded_buffer is taken from the boost circular_buffer examples which wraps operations with lock acquisition and release (more type-safe). I've changed up the calls slightly for my app and the problem is, I am having difficulty compiling. I was hoping to make the calls like below w/o the need for a template function (as in the example) since I'm in the function where I'd like to make the calls. --- bounded_buffer<MyData> bb(200); Consumer<bounded_buffer> consumer(bb); Producer<bounded_buffer> producer(bb); boost::thread* c_thread = new boost::thread(consumer); boost::thread* p_thread = new boost::thread(producer); threads.add_thread(c_thread); threads.add_thread(p_thread); --- Here are the compile errors: error: type/value mismatch at argument 1 in template parameter list for 'template<class Buffer> class Consumer' error: expected a type, got 'bounded_buffer' The example code I'm using is, http://www.boost.org/doc/libs/1_55_0/libs/circular_buffer/example/circular_…

2 1

Can a mapped_file larger than 2GB be random seeked?
by Narcélio Filho 05 May '15

05 May '15

(I'm resending this because it seems that my other message got garbled.) I'm writting on random positions on a mapped file, but it seems that if I seek past 2GB, write something, then seek to a lower position, I got a segfault. Here is the code: #include <cassert> #include <iostream> #include <fstream> #include <boost/iostreams/stream.hpp> #include <boost/iostreams/device/mapped_file.hpp> using namespace std; using boost::iostreams::stream; using boost::iostreams::mapped_file; int main(int argc, char** argv) { const size_t GIGA = 1024l*1024l*1024l; const size_t FILESIZE = 2l * GIGA + 10000; ofstream block("file", ios::binary | ios::out); assert(block.good()); block.seekp(FILESIZE); block.write("", 1); block.close(); mapped_file mappedFile("file"); stream<mapped_file> file(mappedFile, ios::binary|ios::out); assert(mappedFile.is_open()); char buffer[10] = {0}; cout << 0 << endl; file.seekp(0); file.write(buffer, 1); cout << FILESIZE - 1 << endl; file.seekp(FILESIZE - 1); file.write(buffer, 1); cout << 1 * GIGA << endl; file.seekp(1 * GIGA); file.write(buffer, 1); return 0; } I'm compiling under Ubuntu 14.10 (amd64): $ g++ boost-mmap.cpp -lboost_iostreams $ ./a.out 0 2147493647 Segmentation fault (core dumped) Everything is 64-bits: $ file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=d39e3dc0c99e666631747e496bf798b92e4d4c71, not stripped I have the same issue compiling with Visual Studio and running under Windows 8 (amd64). What I'm doing wrong? -- []s, Narcélio.

3 4

boost thread + container.
by Andreas Hehn 05 May '15

05 May '15

Hello boost-users readers, I stumbled across some funny behavior of the headers of boost::thread and boost::container/boost::move for C++O3. I am unsure if this is a known shortcoming of those libraries or if it is a bug. I didn't find anything on the topic in the documentation so far. The problem is dependent on the include order of the two files: * boost/container/vector.hpp * boost/thread/thread.hpp The following code causes several compilation errors (boost-1.58.0/git, g++-4.9.2) related to the move emulation of boost::thread: #include <boost/container/vector.hpp> #include <boost/thread/thread.hpp> int main() { boost::container::vector<boost::thread> v; v.resize(10); return 0; } It prints several error messages starting with boost/container/detail/copy_move_algo.hpp:285:112: error: no matching function for call to ‘move(boost::thread&)’. The following error messages are also boost::move releated "failed" enable_ifs and so on. If I switch the order of the includes everything compiles just fine. Is there a requirement on the order of the includes that I overlooked or is this a bug? Best, Andreas

1 0

How to stage one sub libary in C++ boost
by J Ronald 05 May '15

05 May '15

1. I have been built one sub library as below successfully: b2 locale toolset=msvc address-model=64 link=static threading=multi runtime-link=shared variant=release 2. Then, I tried to run: b2 stage Unexpectedly, it'll build other sub libraries, instead of copy the built sub sub library to the stage directory as the document says. Is there any automatic way to get the final built result in one directory?

1 0

Efficiently pass data from thread to main
by Lane 05 May '15

05 May '15

Using boost, I start a thread from the main process as such. MyWorkThread newThread; newThread = boost::thread(newThread); And in the worker thread class (MyWorkThread), I have a read function which reads from a USB device as much data as it can deliver. This function can be called several hundred times a second. MyThread::read() } //... while () { MyData data; if (hasMore(dev, &data)) // lots of data here // need to get it back to the main thread } } } I'm trying to figure out how to efficiently get this data back to the main process to be placed in a buffer since it can be called so often. - Would making a callback to the main process be the way to go? If so, any pointers how using boost? - Or should I just have a global data buffer and store it directly?

2 1

[serialization] std::shared_ptr with Boost >= 1.53
by Rüdiger Berlich 04 May '15

04 May '15

Hi there, I need to support various versions of Boost, but am in the process of porting our entire code base to C++11. This involves replacing those constructs of Boost that are now in the standard with their C++11-counterparts. A prime example is std::shared_ptr. However, most of our code needs to be serializable. I know that serialization of std::shared_ptr is possible with Boost 1.58. But 1.53 (the oldest version I need to support) cannot serialize std::shared_ptr . Is there any reason not to include the 1.58-Version of #include <boost/serialization/shared_ptr.hpp> instead of the older version, if I detect a Boost-version < 1.58 ? Thanks and Best Regards, Beet

4 12

[Multiprecision] Get mantissa of a float
by Leonardo Yvens 04 May '15

04 May '15

Hello, I'm new to the Multiprecision library, and am trying to extract the mantissa from a float. Using cpp_bin_float, it's easy to get the exponent, but how can I get the mantissa in a normalized form (1.xxxxxxxxxx)? I tried messing with the limbs, they contain large powers of two, but I couldn't interpret that. Thank you very much, Leo Y.

2 2

Can a mapped_file bigger than 2GB be random seeked?
by Narcélio Filho 04 May '15

04 May '15

Hello! I'm writting on random positions on a mapped file, but it seems that if I seek past 2GB, write something, then seek to a lower position, I got a segfault. Here is the code: #include <iostream> #include <fstream> #include <boost/iostreams/stream.hpp> #include <boost/iostreams/device/mapped_file.hpp> using namespace std; using boost::iostreams::stream; using boost::iostreams::mapped_file; int main(int argc, char** argv) { const size_t GIGA = 1024l*1024l*1024l; const size_t FILESIZE = 2l * GIGA + 10000; ofstream block("file", ios::binary | ios::out); assert(block.good()); block.seekp(FILESIZE); block.write("", 1); block.close(); mapped_file mappedFile("file"); stream<mapped_file> file(mappedFile, ios::binary | ios::out); assert(mappedFile.is_open()); char buffer[10] = {0}; cout << 0 << endl; file.seekp(0); file.write(buffer, 1); cout << FILESIZE - 1 << endl; file.seekp(FILESIZE - 1); file.write(buffer, 1); cout << 1 * GIGA << endl; file.seekp(1 * GIGA); file.write(buffer, 1); return 0; } I compile and run on Ubuntu 14.10/amd64: $ g++ example.cpp -lboost_iostreams 0 2147493647 Segmentation fault (core dumped) I also get the same error on Windows 8/amd64. What I'm doing wrong? []s, Narcélio.

1 0

[c++now] Perhaps of interest to Boost library users
by Niall Douglas 03 May '15

03 May '15

https://plus.google.com/+nialldouglas/posts/DsAdUV4RgY5 Content of post for convenience: Just finished my C++ Now 2015 presentation with exactly one week to go! Currently 90 slides for a 90 minute long presentation, I had originally been worried I'd be boring but I think, even if I do say so myself, that this will be one of the more interesting talks at C++ Now this year. It reviews *ten* C++ 11/14 only libraries close to entering Boost, three of which in detail (Boost.AFIO, Boost.Fiber, Boost.DI) and one in very great detail (Boost.APIBind), indeed I spend about 45 slides on APIBind as I believe it provides the foundation stone for a fully modular C++ 11 only Boost 2.0 branch with very significant improvements over Boost 1.0. I also draw some sweeping personal general opinions from the ten library review, and I'll try to answer these questions: * Why do these libraries require C++ 11 or 14? From an end user perspective. * Is there a common theme of the most popular C++ 11/14 features used? * Is there a common theme in choice of library design and use of third party libraries? * Are there techniques used in one library which would make a lot of sense to be used in another library, but for some reason are not? * Do these new libraries take notice of one another and integrate themselves well with other libraries, or are they ivory towers? * How many of these forthcoming libraries explicitly seek to contribute to future C++ standardization? Boost only a few years ago was in a state of sickly malaise after the exit of several big names who had dominated it since its inception. Indeed, in 2013 no new libraries had entered in two years, and nobody could say if Boost was going to be the venue for the next generation of C++ 11/14 libraries approaching standardisation or whether some other venue (especially WG21 itself) would take over. Since 2013 *seventeen* new libraries have either entered Boost or entered the formal review queue, almost a third of which are C++ 11/14 mandatory libraries, whilst WG21's efforts to invent new libraries have not panned out well to date. Traffic on the Boost mailing lists which had become anaemic has once again returned to mass-delete-without-reading levels. It looks like Boost is going to remain the place to be for the highest quality C++ libraries, especially those intended for eventual standardisation. The big question is whether the C++ 11/14 mandatory libraries are so different from the 98/03 libraries in design and philosophy that a C++ 11/14 only Boost 2.0 distribution is warranted? Robert Ramey will be presenting on his vision for Boost 2.0 at C++ Now 2015, and he kindly has allowed me to add my ha'pennies worth after he finishes during which I will summarise my empirical findings from the ten library review. So watch out for the recorded videos! -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

2 2

[BGL] I think the invariant in ResourceExtensionFunction for r_c_shortest_paths is not correct
by Alberto Maria Santini 02 May '15

02 May '15

The documentation for 1.58.0 (http://www.boost.org/doc/libs/1_58_0/libs/graph/doc/r_c_shortest_paths.html) correctly states that: >>> The implementation is a label-setting algorithm. This means that there must be one or more resources whose cumulated consumption(s) after extension is/are always at least as high as before. This is similar to the Dijkstra algorithm for the SPP without resource constraints where the distance measure must be non-negative. It is sufficient if there is one resource with a non-negative resource consumption along all arcs (for example, non-negative arc lengths or non-negative arc traversal times). >>> But, later on, it says: >>> If ref models the ResourceExtensionFunction concept, and if the type Resource_Container models the ResourceContainer concept, after the call ref( const Graph& g, Resource_Container& new_cont, const Resource_Container& old_cont, graph_traits<Graph>::edge_descriptor ) the expression old_cont <= new_cont evaluates to true. This is because, as stated above, the implementation is a label-setting algorithm. Therefore, the Less-Than operator for ResourceContainer must compare one or more resource(s) whose resource consumption(s) along any arc is/are non-decreasing in order for the algorithm to work properly. >>> Now, saying that "old_cont <= new_cont" is much stricter than it should be. The correct requirement (first quote) is that there is **at least one** resource whose consumption monotonically doesn’t decrease. What "old_cont <= new_cont” requires, is that **all** resources’ consumptions are monotonically non-decreasing. These two things are equivalent iff the label only has one resource. Can someone confirm that my observation makes sense? In this case, I’ll open a ticket and submit a patch for the documentation. Can someone also confirm that this check is *not* enforced in r_c_shortest_paths.hpp? Thanks, AS

1 0

Official Stance on CMake Adoption
by Michael Ainsworth 02 May '15

02 May '15

What is the official stance on CMake adoption? Is if simply a fork in the development, or will all of Boost eventually be built using CMake? Michael

3 3

Re: [Boost-users] [boost] [ANN] "Die Boost C++ Bibliotheken", 2nd edition available (German edition)
by Rüdiger Berlich 01 May '15

01 May '15

Let me just say that the book is excellent! Thanks, Boris, for supplying such a comprehensive source of information on Boost. Best Regards, Ruediger > Am 01.05.2015 um 12:31 schrieb Boris Schäling <boris(a)highscore.de>: > > Just a quick announcement: The 2nd edition of my book "Die Boost C++ Bibliotheken" (German edition) is available. > > - It introduces 72 Boost libraries. > - It contains more than 430 examples. > - The print version has 600 pages. > - There is also a Kindle, Epub and PDF version. > - It's also online: <http://dieboostcppbibliotheken.de/> > > There is hardly any difference between the German and the English language edition. The German language edition is a bit more up-to-date after the English language edition has been published in September last year. But there is no need to read the book again in case you read the English language edition already. > > For those who don't know German: The English language edition remains available online at <http://theboostcpplibraries.com/>. > > Boris > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Boost.Cgi Status
by Michael Ainsworth 01 May '15

01 May '15

What is the status of Boost.Cgi by Darren Garvey? It seems that the library hasn't been accepted and it's now 2015 - at least 7 years after last Boost Users mailing list post regarding its status. Michael

2 2

[gsoc15] This year's GSoC students
by Niall Douglas 27 Apr '15

27 Apr '15

Dear Boost, It is our pleasure to announce this year's winning GSoC students and projects: 1. Damian Vicino Topic: Safe Float (boost::safe_numerics<float>) Mentor: Robert Ramey 2. Rajaditya Mukherjee Topic: Boost uBLAS EigenSolver Mentor: David Bellot 3. Anurag Ghosh Topic: Boost Document Library Mentor: Antony Polukhin 4. Nikhar Agrawal Topic: Boost.Fixed-Point Mentor: Paul A. Bristow 5. Benedek Thaler Topic: Enhanced vector and deque containers Mentor: Thorsten Ottosen 6. Louis Dionne Topic: Improved compile-time associative data structures for Hana Mentor: Joel Falcou 7. Jakub Szuppe Topic: Improving Boost.Compute Mentor: Kyle Lutz Congratulations to these students for passing an exceptionally tough contest this year, and our thanks to the above mentors for making themselves available. Finally, thank you Google for another year of funding and to those open source orgs who released duplicate students to us, we appreciate it! Niall and Boris --- Boost C++ Libraries Google Summer of Code 2015 admin https://svn.boost.org/trac/boost/wiki/SoC2015

1 0

Re: [Boost-users] boost examples
by Max 27 Apr '15

27 Apr '15

----- Original Message ----- From: mloskot <mateusz(a)loskot.net> To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] boost examples Date: 2015-04-24 18:01 mloskot wrote > On 23 April 2015 at 11:44, Trek < > trek830@ > > wrote: >> Is there a central link where all official boost examples are hosted? > > No. You may check http://theboostcpplibraries.com/ for unofficial ones. ----- -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org The book, Beyond the C++ Standard Library, also used to be a very good starting point of my understanding the boost libraries. Max

1 0

[Pyhton] (re)binding class instance in python object
by Tamas.Ruszkai＠leica-geosystems.com 27 Apr '15

27 Apr '15

Hi, I have a plain C++ class which I want to exposed to python. The pyhton object accesses the C++ class via smart pointer. class Sensor : public boost::enable_shared_from_this<Sensor> { public: Sensor(int port); ~Sensor() void Open(); void SendCommand(const std::string& command); void Close(); private: int _port; }; auto sensorClassTypeObject = boost::python::class_<Sensor, boost:: shared_ptr<Sensor>>("Sensor", boost::python::init<int>()) .def("Open", &Sensor::Open) .def("SendCommand", &Sensor::SendCommand) .def("Close", &Sensor::Close); The question is: if I already have one instance of the C++ class (in a dependency injection container) then how can I create in the C++ part an instance of the python wrapper so that it does not create a new instance of Sensor, but uses my existing Sensor instance? Then I would put this instance into one of the python modules (this part would be made in C++) inside the python interpreter to be able to access it via script. Something like that: shared_ptr<Sensor> sensorInstance = DIContainer.Resolve<Sensor>(); boost::object pythonInstance = sensorClassTypeObject(sensorInstance); pythonInterpreterWrapper.AddToModule("__main__", pythonInstance); Best Regards, Tamas

1 0

[msm] Event does not get processed after exiting an interrupt state
by Chrisopher Vogl 27 Apr '15

27 Apr '15

Hi all! I got a state machine with 2 regions. The second region has two states ("Run" and "Interrupt"), one is an interrupt state. The region starts in the non interrupt state, just like in the MSM example "Orthogonal regions, terminate state, event deferring". The event called Ev_Resume leads to a transition from state Interrupt back to state Run. In on_entry() of Run I fire an event which never gets processed. Is at that time the FSM still interrupted, i.e. event processing still blocked? Christopher

2 1

Re: [Boost-users] [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
by Paul A. Bristow 24 Apr '15

24 Apr '15

> -----Original Message----- > From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Richard > Sent: 17 March 2015 17:20 > To: boost(a)lists.boost.org > Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years > > Another quarter has gone by and another Boost release is prepared for beta and I see *no* changes to > Boost.Test listed in the release notes.> > So here we are, waiting another 3 months for *simple* changes to be reflected in this library while the > maintainer insists that the fixes are available, yet they continue not to be deployed into any shipping release. It is indeed really deplorable that we don't have Boost.Test updates in a release. Though in mitigation I note that we are really struggling to get out a GIT-driven release at all, (and some of the new troubles are with asynch-exceptions in Boost.Test. See this thread Re: [boost] Running b2 on develop needs asynch-exceptions=on.) However, Richard's hard work on improved docs have been refined and completed by Raffi Enficiaud. Many bug fixes are in the develop branch (including some very new and prompt bug fixes, for example https://svn.boost.org/trac/boost/ticket/11054) I also understand that the fear of Boost.Test updates causing trouble with other libraries, and worse with users test, is a cause for caution in a release version. So it would be really good if *lots more users could download and use the version in the Boost.Test develop branch* so we can get current user feedback. (My experience is good using this, and the test matrix is also good). You can download just Boost.Test either using GIT or as a zip from https://github.com/boostorg/test/tree/develop and substitute it for the contents of the current release modular-boost/libs/test folder (Don't forget to rebuild the Boost.Test library unless you only use the included version). If nothing else, you will find Raffi's shiny new Boostbook docs finally allow you to find what you want to know without frustration. I'd very much like to see this new docs version in the 1.58 documentation release (despite any new features not being in the code release). Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

5 5

[log] Possible to explicitly disable AVX2?
by Jason Roehm 24 Apr '15

24 Apr '15

I am building Boost.Log on a relatively new machine whose compiler and CPU both support the AVX2 instruction set. Boost.Log detects this at build time and configures its compiler flags accordingly to use the AVX2 instruction set. I'd like to use the resulting binaries, however, on older systems that do not have AVX2 support. Is it possible to explicitly disable this at build time? I didn't see any mention of it in the documentation, and my attempts to parse the Jamfile's intentions were not successful. Thank you. Jason

1 0