March 2009 - Boost - lists.preview.boost.org

[Curry] generic and currying multimethod class
by Nowake 08 Mar '09

08 Mar '09

Hi, I implement curried function library and upload to Vault. http://www.boostpro.com/vault/index.php?action=downloadfile&filename=curry.… - This function object create the object that imitates curried function. you can call target function in incremental steps. # but you must regist each argument sets by hand. - This function is generic function. you can set different function object to each argument sets. - This function can also use multimethod. # but you must use holder (similar as boost::any) to hold argument. # this class act dynamic visitor for holder. - This function object is poor performance. it takes much time to execute function. Samples: ____________________________________________________________________ // target function object struct test_function { string operator()() { return "operator()()"; }; string operator()(int& a) { return "operator()(int:" + lexical_cast<string>(a) + ")"; }; string operator()(int& a, double& b) { return "operator()(int:" + lexical_cast<string>(a) + ", double:" + lexical_cast<string>(b) + ")"; }; string operator()(const int& a) { return "operator()(const int:" + lexical_cast<string>(a) + ")"; }; string operator()(const int& a, const double& b) { return "operator()(const int:" + lexical_cast<string>(a) + ", const double:" + lexical_cast<string>(b) + ")"; }; }; BOOST_AUTO_TEST_CASE(test_pod) { // setup curry // create string return curry boost::curry<string> m00; // "entry" function to each argument sets. // nullary function m00.entry(test_function()); // unary function m00.entry<int>(test_function()); // binary function m00.entry<int, double>(test_function()); // you must "entry" each const type if you use const arguments. m00.entry<const int>(test_function()); m00.entry<const int, const double>(test_function()); // execute // incremental execution BOOST_AUTO(c00, m00()); BOOST_AUTO(c01, c00(100)); BOOST_AUTO(c02, c01(100.0)); BOOST_AUTO(r00, c02()); BOOST_CHECK_EQUAL(r00, "operator()(const int:100, const double:100)"); int i(100); double d(100.0); BOOST_CHECK_EQUAL(m00()(), "operator()()"); BOOST_CHECK_EQUAL(m00()(i)(), "operator()(int:100)"); BOOST_CHECK_EQUAL(m00()(i)(d)(), "operator()(int:100, double:100)"); // const value BOOST_CHECK_EQUAL(m00()(100)(), "operator()(const int:100)"); BOOST_CHECK_EQUAL(m00()(100)(100.0)(), "operator()(const int:100, const double:100)"); // with holder object (holder is similar to boost::any) boost::holder h0(100); boost::holder h1(100.0); BOOST_CHECK_EQUAL(m00()(h0)(), "operator()(int:100)"); BOOST_CHECK_EQUAL(m00()(h0)(h1)(), "operator()(int:100, double:100)"); }; Regrads. Nowake

1 0

[math] Please give me some advice.
by Dongfei Yin 08 Mar '09

08 Mar '09

Hi, I have upload the file to Vault, file name is "[math]AD.zip". I have VC++ 2008 and the source can work under it. Please give me some advice to improve it. Dongfei.

1 0

Re: [boost] [Boost-users] C++03 unique_ptr emulation
by Howard Hinnant 08 Mar '09

08 Mar '09

On Mar 6, 2009, at 9:30 AM, Sergey Skorokhodov wrote: > Hi, > > Howard Hinnant wrote: >> I've put up a new version of an C++03 emulated unique_ptr here: > > <skip> > > I tried to use this implementation with MSVC 7.1 sp1 and 9.0 sp1 and > encounter ICE in the following code: Sorry I don't have MSVC 7.1 to test against. Fwiw I dropped your code (copy/paste) into g++ 4.0 and it compiled, linked and ran without any memory leak or other memory related problems. -Howard > > > <code> > > #include <cstdlib> > #include <string> > #include "unique_ptr.hpp" > > > class Base > { > protected: > explicit Base( std::string const & src ) > { > target.reset( new char[src.length() + 1] ); > memcpy( target.get(), src.c_str(), src.length() ); > target[src.length()] = '0'; > } > > explicit Base( boost::unique_ptr<char[]> src ) > : target( move(src) ) > {} > virtual ~Base() {} > > private: > boost::unique_ptr<char[]> target; > }; > > class Derived : public Base > { > public: > explicit Derived( std::string const & src ) : Base( src ) {} > explicit Derived( boost::unique_ptr<char[]> src ) > : Base( move( src ) ) {} > virtual ~Derived() {} > }; > > int main(int argc, char * argv[]) > { > char const TEXT[] = "This is a text"; > boost::unique_ptr<char[]> ptxt( new char[sizeof(TEXT)] ); > Derived drv( move( ptxt ) ); > return 0; > } > > </code> > > Here is the exact compiler output: > > 1>c:\prj\vs2005\projects\unique_tsts\unique_tst\unique_tst.cpp(21) : > fatal error C1001: An internal error has occurred in the compiler. > 1>(compiler file 'f:\dd\vctools\compiler\utc\src\p2\ehexcept.c', > line 1454) > 1> To work around this problem, try simplifying or changing the > program near the locations listed above. > 1>Please choose the Technical Support command on the Visual C++ > 1> Help menu, or open the Technical Support help file for more > information > 1>Build log was saved at "file://c:\prj\VS2005\Projects\unique_tsts > \unique_tst\Debug\BuildLog.htm" > 1>unique_tst - 1 error(s), 0 warning(s) > > Is something wrong with my code or is it a "pure" MSVC bug? > > TIA > > -- > Sergey Skorokhodov > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Thoughts on make_shared and shared_from_this in a constructor
by Peter Dimov 07 Mar '09

07 Mar '09

Let's take an example make_shared overload: template< class T, class A1, class A2 > boost::shared_ptr< T > make_shared( A1 const & a1, A2 const & a2 ) { boost::shared_ptr< T > pt( static_cast< T* >( 0 ), detail::sp_ms_deleter< T >() ); detail::sp_ms_deleter< T > * pd = boost::get_deleter< detail::sp_ms_deleter< T > >( pt ); void * pv = pd->address(); // #1 ::new( pv ) T( a1, a2 ); pd->set_initialized(); T * pt2 = static_cast< T* >( pv ); boost::detail::sp_enable_shared_from_this( &pt, pt2, pt2 ); return boost::shared_ptr< T >( pt, pt2 ); } The primary problem with calling shared_from_this in a constructor is that a shared_ptr to the object does not exist yet and may never will. But, when using make_shared, at the line marked //#1 we do have a shared_ptr that owns the storage of the future object T. So we should, in principle, be able to return a copy of it from shared_from_this. Unfortunately, we can't just move the sp_enable_shared_from_this call to #1 because (a) we can't convert an yet-unconstructed T to its enable_shared_from_this base if there's virtual inheritance along the way, and (b) even if we could, we can't initialize the weak_this_ member since it's not constructed yet. I can't think of a good way to pass this shared_ptr to the enable_shared_from_this base since we have no control over T.

2 3

Future or Property Tree?
by Ryan Gallagher 07 Mar '09

07 Mar '09

Forwarding a question that someone asked in a trac bug, "Will PropertyTree? make it into Boost 1.39.0???": https://svn.boost.org/trac/boost/ticket/1989 I guess this has to be asked at least once a year. ;-) http://thread.gmane.org/gmane.comp.lib.boost.devel/171719/ >From this thread it appears that the original author, Marcin, may no longer be available to maintain this library. Was this ever confirmed? However, a year ago Sebastian mentioned that he would be willing to support the library. I don't know if this offer is still good, but it seems that we should figure out what we're doing with this library. There was a list of items in the following thread about what Marcin felt should be done before the release: http://thread.gmane.org/gmane.comp.lib.boost.devel/171825/ In that thread Marcin wrote: """ IMO the issues that should be addressed before release are: - Simplification by removing some of the template arguments (arguable - maybe someone is using that?) - Figure out which parsers are unneccessary and get rid of them (cmdline parser?) - Get some docs toolchain to work properly and provide up-to-date docs. Lots of the text can be ported over (and my monkey english corrected from the original docs. - Speedup through use of a custom container (to replace std::list, needs some profiling work if it's even worth it) """ I believe that some of the parsers were already removed from svn. In the first link I posted (the trac ticket) were some patches I gave a long time back for the docs in quickbook form + doxygen. However, these were just meant to be a start based upon the original documentation (with a few English grammar corrections) and aren't really release-ready quite yet. (I'd have to see about getting the doc toolchain setup again myself, which I don't remember working so well on Windows, though Linux didn't give me any major problems.) On top of this list, at this point I think there would may be a few patches to review and apply from Trac. Do we have a committed maintainer? Can we make any plan of action for making this library release-ready or are we giving up on it? -Ryan

2 3

[optional] little addition
by Arno Schödl 07 Mar '09

07 Mar '09

I just started using boost::optional, and this proved to be generically useful, but I believe is currently not in boost::optional: template< class T, class Tcompatible > bool optional_assign( T& t, boost::optional<Tcompatible> const& optt ) { if( optt ) { t=*optt; return true; } else { return false; } } so you can write boost::optional< TMyValue > TryToGetT(); T t; if( !optional_assign( t, TryToGetT () ) { ... other way to get t ... } instead of the more verbose: boost::optional< TMyValue > TryToGetT(); T t; boost::optional< TMyValue > const& optt=TryToGetT(); if( optt ) { t=*optt; } else { ... other way to get t ... } get_optional_value_or is similar, but the alternative must be an expression and is eagerly evaluated, both of which may be undesirable. Arno -- Dr. Arno Schoedl · aschoedl(a)think-cell.com Technical Director think-cell Software GmbH · Invalidenstr. 34 · 10115 Berlin, Germany http://www.think-cell.com · phone +49-30-666473-10 · toll-free (US) +1-800-891-8091 Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl · Amtsgericht Charlottenburg, HRB 85229

4 23

[1.38.0] PDF package of Boost documentation released.
by John Maddock 07 Mar '09

07 Mar '09

Folks, A package containing PDF versions of Boost's documentation is now available for Boost-1.38.0 from the usual sourceforge download site: http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=15971… Please note that due to the diverse range of tools in use within Boost it has not been possible to produce PDF's for all of Boost's libraries, those currently included as PDF's are: accumulators any array asio bimap range complex-tr1 concepts config conversion date_time foreach function hash interprocess intrusive iterator math-gcd math mpi octonion optional phoenix program_options proto python_tutorial quaternion ref regex scope_exit signals static_assert string_algo thread tr1 tribool type_traits typeof units unordered variant xpressive Documentation for the following tools are also included in this package: bjam boost_build boostbook quickbook Regards, John Maddock.

6 9

[serialization] Text/Binary archive Is there a bug?
by Kasra 07 Mar '09

07 Mar '09

Hi guys, I was working withe boost.serialization and found a peculiar problem: when I use a binary archive I successfully serialize the objects but fail to deserialize them, while with text archive both of the operations occur without a problem!! Is there a special note about binary archives that I haven't done or could this be a bug? -- Kasra

2 1

Formal Review: Boost.RangeEx
by Thorsten Ottosen 06 Mar '09

06 Mar '09

Dear Developers and Users, It's my pleasure to announce that the review of Neil Groves' RangeEx library starts today and lasts until March 3, 2009. What is it? +++++++++++ The library provide two very useful extensions to the range library 1. Range-based algorithms. E.g. boost::sort( rng ); which is a convenient wrapper of instead of std::sort( boost::begin(rng), boost::end(rng) ); But the new interface also allows for more expressive code because (on the fly) composition of algorithms suddenly is possible. 2. Range adaptors. E.g. std::vector<int> vec = ...; boost::copy( vec | boost::adaptors::reversed, std::ostream_iterator<int>( std::cout ) ); where the expression "vec | boost::adaptors::reversed" wraps the iterators of the range on the left in reverse iterators. The library provides a wide range (no pun intended) of Range adaptors, and they are a powerful way to create ranges on the fly and pass them to algorithms. Getting the library +++++++++++++++++++ The library may be downloaded from http://www.cs.aau.dk/~nesotto/boost/range_ex.zip or from the Boost vault under "Algorithms". The docs may be browsed online here http://www.cs.aau.dk/~nesotto/boost/libs/range/ Please note that the documentation is integrated with the current Range ilbrary. Therefore the relevant sections for the review is http://www.cs.aau.dk/~nesotto/boost/libs/range/doc/adaptors.html and http://www.cs.aau.dk/~nesotto/boost/libs/range/doc/algorithms.html The code may be browsed here: http://www.cs.aau.dk/~nesotto/boost/boost/range/ Notice the library is header only (exception: the adaptor tokenized() depends on Boost.Regex). Writing a review ++++++++++++++++ If you feel this is an interesting library, then please submit your review to the developer list (preferably), or to the review manager. Here are some questions you might want to answer in your review: - 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? And finally, every review should answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Special considerations ++++++++++++++++++++++ Various RangeEx like libraries have been implemented in the past. You might want to compare with those libraries when you form your oppinion: 1. John Torjo's range lib http://rangelib.synesis.com.au/libs/boost-rangelib-20040913.zip http://torjo.com/rangelib/index.html 2. Adobe's ASL libraries include range-based algorithms: http://stlab.adobe.com/group__algorithm.html I'm looking forward to your review. best regards Thorsten, Review Manager

18 101

Re: [boost] [math] Does any one interesting in calculating derivative for a expression automatically?
by Brandon Kohn 06 Mar '09

06 Mar '09

-------------------------------------------------- From: "Dongfei Yin" <yin.dongfei(a)gmail.com> Sent: Friday, March 06, 2009 8:04 AM To: <boost(a)lists.boost.org> Subject: Re: [boost] [math] Does any one interesting in calculating derivative for a expression automatically? > You know, there are too many functions in math, so I think I can't > implement all of them, the functions included in standard library is > enough for me. and I will make it easy to be extended. what do you think > about it, I mean how many functions should I implement. > My advice would be to make the interface for supporting math functions extensible and held at arms length. The std math functions like pow, sin etc are generally working only with native types. There are those among us that use things like GMP or rational number libraries with unlimited precision for our numerical types. In these cases we have either defined our own trig or transcendental functions or had them supplied with a 3rd party lib. It would be nice to be able to generate derivative expressions which then may be applied to these types and with the use of our specialized math functions. Hope this helps, With regards, Brandon

1 0