- Boost - lists.boost.org

[Who's Using Boost?] FaceBook
by Brian Wood 05 Jun '12

05 Jun '12

Thanks for the link. I notice Folly has an IntrusiveList derived from boost::intrusive::list. We have a nickname for boost::intrusive::list also -- ilist. Perhaps there are others who have done the same? Shalom, Brian Wood Ebenezer Enterprises http://webEbenezer.net

1 0

[bind] Move Parameters?
by Daniel Larimer 05 Jun '12

05 Jun '12

Say I have some synchronous code like this: vector<data> v; some_method( std::move(v) ) Now I want to call to make that some_method call asynchronous so what I really want is function<void()> f = bind( some_method, boost::rref( std::move(v) ) ) asio_io_service.post(f); // performs async move of v into some_method asio_io_service.post(f); // undefined, or throw bound parameter has already moved... As far as I can tell there is no current support for anything like this, and I think it could be very useful. Dan

1 0

Re: [boost] [git/modularization] Suggested names for branches?
by Sean Chittenden 04 Jun '12

04 Jun '12

> The three branches in question, with the git-flow names in parens, > were the main development branch (develop), release prep branches (?), > and the branch with actual releases (master). > > Is there a better usual convention for these names? I have a vague > memory of someone mentioning "master" for the main development branch, > "release" for the branch with the actual releases, and maybe > "beta-x.xx.x" for release prep branches. re: git flow branch names, I'd advocate for their use simply because it matches all of the external training material (videos, docs, flow charts, etc) available regarding the use of git flow (and it reduces the friction for getting initially setup). I agree that they aren't ideal and much prefer the naming convention used by the FreeBSD project (where branch names indicate a stable API, 9-STABLE, 8-STABLE, etc., vs -CURRENT), but I'd stick with the default names for now and then in a release or three consider changing from the defaults to something boost specific. -sc # Initialize default git flow branches git flow init -d # From project/.git/config [gitflow "branch"] master = master develop = develop [gitflow "prefix"] feature = feature/ release = release/ hotfix = hotfix/ support = support/ versiontag = -- Sean Chittenden sean(a)chittenden.org

1 0

folly (Facebook's open source C++ library)
by Tudor Bosman 04 Jun '12

04 Jun '12

https://www.facebook.com/notes/facebook-engineering/folly-the-facebook-open… I'm Tudor, one of the folly developers. I'll try to answer your questions or poke the appropriate people :) Re: "NO EXCEPTIONS" in the README -- the README file was intended for internal Facebook contributors (hence stray references to internal paths), and "NO EXCEPTIONS" referred to "no exceptions to the rules above", NOT "no C++ exceptions". Will fix / clarify / remove soon. -Tudor.

2 1

[Who's Using Boost?] FaceBook
by Dave Abrahams 04 Jun '12

04 Jun '12

as noted in https://www.facebook.com/notes/facebook-engineering/folly-the-facebook-open… -- Dave Abrahams BoostPro Computing http://www.boostpro.com

5 4

asio::epoll_reactor::complete_operations_and_timers() - thread saftey
by Hite, Christopher 04 Jun '12

04 Jun '12

I thought I'd take a look at the epoll_reactor implementation. I thinking of using asio proactor style code to use kernel bypass libraries. I wanted to see how you do async IO with a pool of threads. I think I see a bug. None of the operations there done outside of the lock seem thread safe. They unsafely modify linked lists. lock.unlock(); read_op_queue_.complete_operations(); write_op_queue_.complete_operations(); except_op_queue_.complete_operations(); Chris

1 0

[python] run python script from bjam
by lcaminiti 03 Jun '12

03 Jun '12

Hello all, I build a Boost.Python module and install it using bjam as follow: python-extension pydef : deduced_params_pydef.cpp : <library>/boost/python//boost_python <library>/boost/regex//boost_regex <link>shared:<define>BOOST_REGEX_DYN_LINK=1 ; install pydef_install : pydef : <install-dependencies>on <install-type>SHARED_LIB <install-type>PYTHON_EXTENSION <location>. ; I the same dir I have a python script deduced_params_pydef.py which will import the module and test it. How do I run the python script automatically from bjam so to fully compile and test the module that my code generates? Something like (this doesn't work of course): # Make sure pydef target is built first, then runs python deduced_params_pydef.py run-py pydef_install : deduced_params_pydef.py ; Thanks a lot. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-python-run-python-script-from-bjam… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 2

boost.unordered undocumented methods
by niXman 03 Jun '12

03 Jun '12

Hello! In the documentation for boost-1.49.0 the following methods are not documented: https://github.com/ryppl/boost-svn/blob/master/boost/unordered/unordered_ma… https://github.com/ryppl/boost-svn/blob/master/boost/unordered/unordered_ma… https://github.com/ryppl/boost-svn/blob/master/boost/unordered/unordered_ma… https://github.com/ryppl/boost-svn/blob/master/boost/unordered/unordered_ma… https://github.com/ryppl/boost-svn/blob/master/boost/unordered/unordered_se… https://github.com/ryppl/boost-svn/blob/master/boost/unordered/unordered_se… https://github.com/ryppl/boost-svn/blob/master/boost/unordered/unordered_se… https://github.com/ryppl/boost-svn/blob/master/boost/unordered/unordered_se… -- Regards, niXman ___________________________________________________ Dual-target(i686/x86_64) MinGW compilers for i686/x86_64 hosts: http://sourceforge.net/projects/mingwbuilds/

1 0

Is there interest in copyable type_info that does not require RTTI (was: Is there interest in typeid(TYPE).name() like function that does not require RTTI)
by Antony Polukhin 03 Jun '12

03 Jun '12

Hi, There is a detail/sp_typeinfo.hpp which is not documented, and has some drawbacks. This header provides type_info like class that can be used with RTTI disabled. I am proposing to refactor this header, move it to utility/template_info.hpp and document it as a separate utility. Refactored header will provide classes template_info_ptr, template_info<T>, type_info_ptr and free function get_template_info<T>() Advantages: 1) more portable and reliable than detail::sp_typeinfo (no sp_typeid_<T>::ti_ public static variable) 2) copyable type_info like classes 3) has all the type_info functions + name_demangle 4) works with disabled RTTI 5) better functionality: no need to write macros like: #if defined( BOOST_NO_TYPEID ) # define BOOST_FUNCTION_COMPARE_TYPE_ID(X,Y) ((X)==(Y)) #elif (defined(__GNUC__) && __GNUC__ >= 3) \ || defined(_AIX) \ || ( defined(__sgi) && defined(__host_mips)) # include <cstring> # define BOOST_FUNCTION_COMPARE_TYPE_ID(X,Y) \ (std::strcmp((X).name(),(Y).name()) == 0) # else # define BOOST_FUNCTION_COMPARE_TYPE_ID(X,Y) ((X)==(Y)) #endif 6) user can explicitly chose between template_info+template_info_ptr and type_info+type_info_ptr 7) no macro (get_template_info<T>() instead of &BOOST_SP_TYPEINFO(T) ) Disadvantages: 1) Does not work with variables (but you can still use BOOST_TEMPLATE_INFO_PTR(BOOST_TYPEOF(var))) 2) BOOST_CURRENT_FUNCTION produces long strings, and that could lead to code bloat when RTTI disabled Some usage examples: int main () { // Portable way that works with and without RTTI: copyable_type_info t1 = get_template_info<std::string>(); copyable_type_info t2 = get_template_info<int>(); // class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > std::cerr << t1.name_demangled() << '\n'; // int std::cerr << t2.name_demangled() << '\n'; // false std::cerr << (t1 == t2) << '\n'; // true std::cerr << (t1 != t2) << '\n'; copyable_type_info t1_copy = t1; // .?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@ std::cerr << get_template_info<std::string>().name() << '\n'; // class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > std::cerr << get_template_info<std::string>().name_demangled() << '\n'; // explicitly using no-RTTI methods // int>::name_begin(void) std::cerr << template_info<int>::name_begin() << '\n'; // int std::cerr << template_info<int>::name_demangled() << '\n'; // class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > >::name_begin(void) std::cerr << template_info<std::string>::name_begin() << '\n'; // class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > std::cerr << template_info<std::string>::name_demangled() << '\n'; template_info_ptr p1 = template_info<int>::construct(); template_info_ptr p2 = template_info<std::string>::construct(); std::cerr << (p1 == p2) << '\n'; std::cerr << (p1 != p2) << '\n'; } If there is interest, I can commit code to sandbox and request for review. P.S.: As I know, Boost.Function, Boost.Shared_ptr and Boost.Exception use code similar to what I am proposing. Following libraries use typeid() and can benefit from using proposed classes: Boost.MSM, Boost.Math, Boost.Test, Boost.Graph, Boost.Units, Boost.XPressive, Boost.Any, Boost.Statechart -- Best regards, Antony Polukhin

3 4

[filesystem] Linker error against std::codecvt in VS2012 RC
by Lars Viklund 02 Jun '12

02 Jun '12

Hi list, I foolishly installed the Visual Studio 2012 RC yesterday night and made an overnight build of Boost. It seems like there's something awry, as I'm getting a mysterious linker error in Filesystem's path.obj [1], even in a fresh empty testbed project. I'm linking Boost statically and the CRT dynamically. If I link the CRT statically, the linker error goes away. Has anyone else installed this software and can reproduce this problem? I'm building Boost against trunk, r78785. I dread to think of the horror that I will have go through in actually reporting a bug against the runtime itself :( [1] 1>libboost_filesystem-vc110-mt-gd-1_50.lib(path.obj) : error LNK2001: unresolved external symbol "protected: virtual int __thiscall std::codecvt<wchar_t,char,int>::do_length(int const &,char const *,char const *,unsigned int)const " (?do_length@?$codecvt@_WDH@std@@MBEHABHPBD1I@Z) -- Lars Viklund | zao(a)acc.umu.se

4 5