- Boost - lists.boost.org

Boost.Logging 1.51 Using VS2012.
by syvyi 09 Jan '13

09 Jan '13

Hello, my application which was successfully compiled on VS2010 brings the next errors using VS2012 c:\program files (x86)\boost\boost_1_51_0\boost\log\sources\basic_logger.hpp(227): error C2664: 'std::pair<_Ty1,_Ty2> boost::log_mt_nt5::basic_attribute_set<CharT>::insert(const std::pair<const boost::log_mt_nt5::basic_slim_string<CharT>,boost::log_mt_nt5::basic_attribute_set<CharT>::mapped_type> )' : cannot convert parameter 1 from 'std::pair<_Ty1,_Ty2>' to 'const std::pair<_Ty1,_Ty2> &' 4> with 4> [ 4> _Ty1=boost::log_mt_nt5::basic_attribute_set<char>::iter<false>, 4> _Ty2=bool, 4> CharT=char 4> ] 4> and 4> [ 4> _Ty1=std::basic_string<char,std::char_traits<char>,std::allocator<char>>, 4> _Ty2=boost::shared_ptr<boost::log_mt_nt5::attribute> 4> ] 4> and 4> [ 4> _Ty1=const boost::log_mt_nt5::basic_slim_string<char>, 4> _Ty2=boost::log_mt_nt5::basic_attribute_set<char>::mapped_type 4> ] 4> Reason: cannot convert from 'std::pair<_Ty1,_Ty2>' to 'const std::pair<_Ty1,_Ty2>' 4> with 4> [ 4> _Ty1=std::basic_string<char,std::char_traits<char>,std::allocator<char>>, 4> _Ty2=boost::shared_ptr<boost::log_mt_nt5::attribute> 4> ] 4> and 4> [ 4> _Ty1=const boost::log_mt_nt5::basic_slim_string<char>, 4> _Ty2=boost::log_mt_nt5::basic_attribute_set<char>::mapped_type 4> ] 4> No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called 4> c:\program files (x86)\boost\boost_1_51_0\boost\log\sources\basic_logger.hpp(226) : while compiling class template member function 'std::pair<_Ty1,_Ty2> boost::log_mt_nt5::sources::basic_logger<CharT,FinalT,ThreadingModelT>::add_attribute_unlocked(const std::basic_string<_Elem,_Traits,_Alloc> &,const boost::shared_ptr<T> &)' 4> with 4> [ 4> _Ty1=boost::log_mt_nt5::basic_attribute_set<char>::iter<false>, 4> _Ty2=bool, 4> CharT=char, 4> FinalT=manster::logger::manster_logger_mt, 4> ThreadingModelT=boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex>, 4> _Elem=char, 4> _Traits=std::char_traits<char>, 4> _Alloc=std::allocator<char>, 4> T=boost::log_mt_nt5::attribute 4> ] 4> c:\program files (x86)\boost\boost_1_51_0\boost\log\sources\severity_feature.hpp(188) : see reference to function template instantiation 'std::pair<_Ty1,_Ty2> boost::log_mt_nt5::sources::basic_logger<CharT,FinalT,ThreadingModelT>::add_attribute_unlocked(const std::basic_string<_Elem,_Traits,_Alloc> &,const boost::shared_ptr<T> &)' being compiled 4> with 4> [ 4> _Ty1=boost::log_mt_nt5::basic_attribute_set<char>::iter<false>, 4> _Ty2=bool, 4> CharT=char, 4> FinalT=manster::logger::manster_logger_mt, 4> ThreadingModelT=boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex>, 4> _Elem=char, 4> _Traits=std::char_traits<char>, 4> _Alloc=std::allocator<char>, 4> T=boost::log_mt_nt5::attribute 4> ] 4> c:\program files (x86)\boost\boost_1_51_0\boost\log\sources\channel_feature.hpp(212) : see reference to class template instantiation 'boost::log_mt_nt5::sources::basic_logger<CharT,FinalT,ThreadingModelT>' being compiled 4> with 4> [ 4> CharT=char, 4> FinalT=manster::logger::manster_logger_mt, 4> ThreadingModelT=boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex> 4> ] 4> c:\program files (x86)\boost\boost_1_51_0\boost\log\sources\basic_logger.hpp(315) : see reference to class template instantiation 'boost::log_mt_nt5::sources::channel<ChannelT>::apply<BaseT>' being compiled 4> with 4> [ 4> ChannelT=std::string, 4> BaseT=boost::log_mt_nt5::sources::basic_logger<char,manster::logger::manster_logger_mt,boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex>> 4> ] 4> c:\program files (x86)\boost\boost_1_51_0\boost\mpl\aux_\preprocessed\plain\apply_wrap.hpp(49) : see reference to class template instantiation 'boost::log_mt_nt5::sources::aux::inherit_logger_features::apply<PrevT,T>' being compiled 4> with 4> [ 4> PrevT=boost::log_mt_nt5::sources::basic_logger<char,manster::logger::manster_logger_mt,boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex>>, 4> T=boost::log_mt_nt5::sources::channel<std::string> 4> ] 4> c:\program files (x86)\boost\boost_1_51_0\boost\mpl\aux_\preprocessed\plain\apply.hpp(63) : see reference to class template instantiation 'boost::mpl::apply_wrap2<F,T1,T2>' being compiled 4> with 4> [ 4> F=boost::log_mt_nt5::sources::aux::inherit_logger_features, 4> T1=boost::log_mt_nt5::sources::basic_logger<char,manster::logger::manster_logger_mt,boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex>>, 4> T2=boost::log_mt_nt5::sources::channel<std::string> 4> ] 4> c:\program files (x86)\boost\boost_1_51_0\boost\mpl\aux_\preprocessed\plain\reverse_fold_impl.hpp(81) : see reference to class template instantiation 'boost::mpl::apply2<F,T1,T2>' being compiled 4> with 4> [ 4> F=boost::log_mt_nt5::sources::aux::inherit_logger_features, 4> T1=boost::log_mt_nt5::sources::basic_logger<char,manster::logger::manster_logger_mt,boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex>>, 4> T2=boost::log_mt_nt5::sources::channel<std::string> 4> ] 4> c:\program files (x86)\boost\boost_1_51_0\boost\mpl\reverse_fold.hpp(41) : see reference to class template instantiation 'boost::mpl::aux::reverse_fold_impl<N,First,Last,State,BackwardOp,ForwardOp>' being compiled 4> with 4> [ 4> N=2, 4> First=boost::mpl::v_iter<boost::mpl::vector2<boost::log_mt_nt5::sources::severity<severity_level>,boost::log_mt_nt5::sources::channel<std::string>>,0>, 4> Last=boost::mpl::v_iter<boost::mpl::vector2<boost::log_mt_nt5::sources::severity<severity_level>,boost::log_mt_nt5::sources::channel<std::string>>,2>, 4> State=boost::log_mt_nt5::sources::basic_logger<char,manster::logger::manster_logger_mt,boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex>>, 4> BackwardOp=boost::log_mt_nt5::sources::aux::inherit_logger_features, 4> ForwardOp=boost::mpl::arg<1> 4> ] 4> c:\program files (x86)\boost\boost_1_51_0\boost\log\sources\basic_logger.hpp(338) : see reference to class template instantiation 'boost::mpl::reverse_fold<Sequence,State,BackwardOp>' being compiled 4> with 4> [ 4> Sequence=boost::log_mt_nt5::sources::features<boost::log_mt_nt5::sources::severity<severity_level>,boost::log_mt_nt5::sources::channel<std::string>>, 4> State=boost::log_mt_nt5::sources::basic_logger<char,manster::logger::manster_logger_mt,boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex>>, 4> BackwardOp=boost::log_mt_nt5::sources::aux::inherit_logger_features 4> ] 4> d:\sankom\manster\manster\manster\manster_logger.h(160) : see reference to class template instantiation 'boost::log_mt_nt5::sources::basic_composite_logger<CharT,FinalT,ThreadingModelT,FeaturesT>' being compiled 4> with 4> [ 4> CharT=char, 4> FinalT=manster::logger::manster_logger_mt, 4> ThreadingModelT=boost::log_mt_nt5::sources::multi_thread_model<boost::log_mt_nt5::aux::light_rw_mutex>, 4> FeaturesT=boost::log_mt_nt5::sources::features<boost::log_mt_nt5::sources::severity<severity_level>,boost::log_mt_nt5::sources::channel<std::string>> 4> ] What is the solution ? -- View this message in context: http://boost.2283326.n4.nabble.com/Boost-Logging-1-51-Using-VS2012-tp464114… Sent from the Boost - Dev mailing list archive at Nabble.com.

3 7

Requesting permission to merge 82408 to release
by Glen Fernandes 09 Jan '13

09 Jan '13

82408 is a fix for #7867 (found by Mathias) where BOOST_NO_EXCEPTIONS was not honored. Glen

2 1

[non-instrusive move] interest in new library?
by THOMAS JORDAN 09 Jan '13

09 Jan '13

Hi, Would there be interest for Boost in a small library providing a simple, non-instrusive emulation of move semantics for C++03 (though it could also be used in a C++11 environment)? It consists of a small number of 'move' function overloads, plus a trait class. It can be used facilitate move semantics/value-orientated programming in environments which lack/forbid C++11 or intrusive move libraries, and facilitate/force copy-elision and RVO optimisations in certain situations where they might otherwise not occur. Its mechanism is as follows: it detects at compile-time if the type of the argument(s) has a member swap function, and if so, it performs a swap, otherwise is calls the regular assignment operator. It can be used to provide an emulation of: move-assignment between lvalues moving an rvalue to an lvalue moving an lvalue to a temporary. It also supports moving between built-in arrays. Example use-cases are: //returning a value std::string foo(std::string s) { //append something to s //... //compiler can perform rvo, if just used 'return s;' compiler would not perform nrvo return move(s); } //passing a value std::string s("hello"); void bar(std::string s) {...} foo(s); //copy foo(move(s)); //move //moving a value into place void MyClass::MyClass(std::string s) { //move value into default constructed member move(s, s_); }

1 0

[log] v2 beta 1 mini-review request
by Andrey Semashev 09 Jan '13

09 Jan '13

Hi, It's been a while since Boost.Log v1 was reviewed back in 2010. Here is the review result: http://lists.boost.org/boost-announce/2010/03/0256.php But the time was spent for purpose as the library took substantial changes. I've just uploaded the v2 beta 1 to the SourceForge project page: Code: http://sourceforge.net/projects/boost-log/files/boost-log-2.0-beta1-r800.zi… Docs: http://boost-log.sourceforge.net/libs/log/doc/html/index.html SVN: svn co https://boost-log.svn.sourceforge.net/svnroot/boost-log/trunk/boost-log I must say this is not the final release; the docs are not quite complete (in particular, the Extending the library section has not been updated yet) and the code may have rough edges here and there. But it is good enough to review the changes, or the whole library if you haven't got acquainted with v1. The change log is quite big, you can see it here: http://boost-log.sourceforge.net/libs/log/doc/html/log/changelog.html I'll just mention the most significant highlights here: - Character type support unified. Log records, core, filters and most sinks have been made character type agnostic. It is possible now to emit log records with messages with different character types in a single application. Character code conversion will be performed as needed when formatting log records. - Filters and formatters were rewritten and are now based on Boost.Phoenix. Unified attribute value placeholders in filters and formatters. The template expressions now reside in the common namespace "expressions". - Added support for attribute keywords in filters and formatters. Attribute keywords identify particular attribute values within log records; their use significantly simplify template expressions syntax. - Reworked attribute value extraction. In fact, the old extraction API has been split into visitation and the new extraction APIs. In conjunction with attribute keywords this makes extracting attribute values very simple. - Introduced a concept of a default sink which is used when no sinks are registered in the logging core. The sink outputs formatted log records to the console. - Trivial logging now outputs to console by default. Actually, trivial logging logs to the default sink by default. - Asynchronous sink now supports customizing record queueing strategies. New bounded queue strategies solve the problem of log records piling in the queue. - Attributes are now implemented following the pimpl pattern; it is no longer needed to create attributes using make_shared or new. This simplified attribute registration code. - Channel logger now allows changing channel name after construction. I don't plan any major changes to the code until the final release, unless something critical comes up during the review. I will keep updating the docs in the coming days and will request permission to merge to Boost when done. Comments are welcome.

3 4

[interprocess] (OS X) waiting on condition variable = CPU 100% + fans running loud
by Francisco Lopes 08 Jan '13

08 Jan '13

Hi, I was implementing a kind of server using shared memory. The server should keep idle, waiting for a request and I do this by waiting on a condition variable, of course. I then noticed my fans running high when I let the server waiting a little longer while testing and discovered this happens simply because of some busy loop implementation for condition waiting. Is there any reason for that? Given the interprocess library age, there's no way for implementing a non-busy interprocess condition variable waiting available? https://svn.boost.org/trac/boost/ticket/6108 Regards, Francisco Lopes

6 15

Re: [boost] [interprocess] (OS X) waiting on condition variable = CPU 100% + fans running loud
by Peter Dimov 08 Jan '13

08 Jan '13

> > Clang has std::atomic though, doesn't it? It probably supports the > > __sync intrinsics as well. > > Actually, it seems to support the even better __atomic intrinsics: > > http://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html Also here: http://libcxx.llvm.org/atomic_design_a.html

2 2

Re: [boost] [interprocess] (OS X) waiting on condition variable = CPU 100% + fans running loud
by Peter Dimov 08 Jan '13

08 Jan '13

> Clang has std::atomic though, doesn't it? It probably supports the __sync > intrinsics as well. Actually, it seems to support the even better __atomic intrinsics: http://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html

1 0

[release] permission to merge (fix show-stopper in 1.53-rc)
by Oliver Kowalke 08 Jan '13

08 Jan '13

I'd like to merge trunk to release in order to fix bug #7864 (unresolved symbols on Windows)

2 2

Re: [boost] new proposal: order statistics tree (Szymon Wojciechowski)
by Leo Goodstadt 07 Jan '13

07 Jan '13

> On Fri, Jan 04, 2013; 4:33am, "Rahul Sr" <srivasrrahul(a)gmail.com> wrote: > > On Wed, Jan 2, 2013 at 3:46 PM, Szymon Wojciechowski wrote: > > Briefly, it is container which allows logarithmic inserting, searching and > > erasing as in set, but additionally it permits to access elements via > > numerical value - key order. > > Will it be like this? > http://stackoverflow.com/questions/11230734/c-stl-order-statistic-tree > http://www.opensource.apple.com/source/llvmgcc42/llvmgcc42-2336.9/libstdc++… The libstdc++ policy based data structure (pb_ds) order statistic tree only has "set" behaviour. It takes a certain amount of extra work to use it as a replacement for multiset and multimap. They recommend using a set (tree) of lists to use pb_ds::tree like a multiset. However, this obviously doesn't work for order_statistic tree: each of the duplicates is only counted once (each list of duplicates is a single element in the tree). Does your order statistic tree allow duplicates? Leo Goodstadt

2 1

[parameter] std proposal
by Lorenzo Caminiti 07 Jan '13

07 Jan '13

Hello all, Is there a C++ standard proposal for named parameter addition? I am looking for an "N-paper" for named parameters similar to N2081 for concepts, or N1962 for contracts. Thank you. -- Sent from my mobile device Lorenzo

6 8