- Boost - lists.preview.boost.org

Request for feedback - Map providing insertion order preserving iteration
by Gautam Sewani 24 Aug '09

24 Aug '09

Hi, We wanted to add a map to Boost C++ libraries which would allow iteration in the order in which elements were inserted, and would also provide logarithmic time retrieval. A simple design for this would be to have a balanced binary tree along with an auxiliary linked list of pointers to the keys in the tree. We would be grateful if you could provide feedback on the utility and design. Regards Gautam Sewani Satyam Shekhar

2 1

[signals2] How to build docs?
by John Maddock 24 Aug '09

24 Aug '09

I'm looking into building PDF versions of the docs for 1.40 and I'm having trouble building the signals2 docs. For example if I cd into libs/signals2/doc and build from there, then the XML code snippets aren't found. Likewise if I build as a dependency from doc/pdf. Any ideas? Thanks, John.

3 7

Re: [boost] [C++-sig] [Boost.Python] Request to merge some patches from trunk into 1.40 branch (was: Re: PySide has been released)
by Stefan Seefeld 24 Aug '09

24 Aug '09

Anderson, let me forward that mail to the main boost list, and ping Beman (release manager) and David (boost.python maintainer). Beman, David, if it's not too late, I may help merge trunk to the release branch. Let me know... Stefan On 08/21/2009 08:08 AM, Anderson Lizardo wrote: > I think it was not clear in the announcement, but PySide uses Boost.Python. > > And for it to work properly, we need a few patches that are already in > Boost SVN trunk, but in none of the release branches. > > Therefore, is it possible to get these patches merged into the 1.40 > release branch before the final release? That would make life a lot > easier for other distros to try PySide without requiring to apply > patches separately. > > The relevant commits are listed in http://www.pyside.org/downloads/, they are: > > Add generic call operator support. > https://svn.boost.org/trac/boost/changeset/47846 > Support C++ enums which have the same value. > https://svn.boost.org/trac/boost/changeset/53660 > Fix unsigned integer converters. > https://svn.boost.org/trac/boost/changeset/54919 > Fix unsigned integer converters (update). > https://svn.boost.org/trac/boost/changeset/54923 > > IMHO these patches fix important bugs in Boost.Python, and the first > two were in trunk even before the 1.39 release, but were never > merged... > > Thanks in advance, > -- ...ich hab' noch einen Koffer in Berlin...

3 2

[Boost.Python] Request to merge some commits from trunk into 1.40 branch
by Anderson Lizardo 24 Aug '09

24 Aug '09

[I accidentally sent this e-mail to the C++-sig mailing list, please don't consider it a cross-post] As announced on the C++-sig mailing list, PySide was released: www.pyside.org. I think it was not clear in the announcement, but PySide uses Boost.Python. And for it to work properly, we need a few patches that are already in Boost SVN trunk, but in none of the release branches. Therefore, is it possible to get these patches merged into the 1.40 release branch before the final release? That would make life a lot easier for other distros to try PySide without requiring to apply patches separately. The relevant commits are listed in http://www.pyside.org/downloads/, they are: Add generic call operator support: https://svn.boost.org/trac/boost/changeset/47846 Support C++ enums which have the same value: https://svn.boost.org/trac/boost/changeset/53660 Fix unsigned integer converters: https://svn.boost.org/trac/boost/changeset/54919 Fix unsigned integer converters (update): https://svn.boost.org/trac/boost/changeset/54923 I think these patches fix important bugs in Boost.Python, and the first two were in trunk even before the 1.39 release, but were never merged... Thanks in advance, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil

2 1

[persistence] interface overview
by Stefan Strasser 24 Aug '09

24 Aug '09

A while ago, I proposed a persistence library and there was some interest. Since then, the prototype has evolved into a feature-complete, reasonably optimized, implementation. Here's a quick recap of what the library is supposed to do: --------- int main(){ ... shared_ptr<A> shared(new A); db_ptr<A> db(new A); ... } // "shared" is destroyed, "db" is saved to disk to ensure data consistency, there are transactions introduced: transaction tx; //change_objects tx.commit(); if change_objects throws an exception, causing tx to be destroyed without commit() being called, all changes are undone. --------- there is no complete documentation yet, but I've written an overview of the library interface, which can be found here: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=overvi… I'd appreciate your comments. please note the "open issues" section.

4 5

[unordered] allocators and EBO
by Thorsten Ottosen 24 Aug '09

24 Aug '09

Hi James, (Sorry I called you Jeremy in the other post). When the allocator is empty, you should avoid storing them as members in different internal structures, and make the allcator a base class of some of these structures. Thanks -Thorsten

2 2

[mpl] patch for non-typeof map::insert
by Steven Watanabe 24 Aug '09

24 Aug '09

AMDG mpl::map insert can fail after an erase, because it uses size instead of order to determine the next order. The patch https://svn.boost.org/trac/boost/attachment/ticket/2042/insert_impl.hpp.pat… fixes this. Okay to commit? In Christ, Steven Watanabe

3 3

bjam - help please
by Edward Grace 23 Aug '09

23 Aug '09

Since I'm trying to Boostify (is that a legitimate word now? - heck you can verb anything these days) my code, I decided to try bjam: Gulp, having been weaned on automake and fiends [sic] it looks like it should be easy enough, but I've fallen at the first hurdle: In Jamroot: using gcc : 4.4 : g++-4 ; exe example_basic : example_basic.cpp : <include>. ; The <include>. line, as I understand it will mean the #include <blah> that I use will pick up stuff in the same directory as the source file (this seems ok). My problem is the link stage, $ bjam example_basic ...found 53 targets... ...updating 1 target... gcc.link bin/gcc-4.4/debug/example_basic /usr/bin/ld: unknown flag: --start-group collect2: ld returned 1 exit status "g++-4" -o "bin/gcc-4.4/debug/example_basic" -Wl,--start- group "bin/gcc-4.4/debug/example_basic.o" -Wl,-Bstatic -Wl,- Bdynamic -Wl,--end-group -g ...failed gcc.link bin/gcc-4.4/debug/example_basic... I've no idea where all this --start-group stuff comes from -- never seen it before. Any ideas? -ed ------------------------------------------------ "No more boom and bust." -- Dr. J. G. Brown, 1997

2 6

regex/ICU fix
by Vladimir Prus 23 Aug '09

23 Aug '09

As reported previously, --build-type=complete does not work if ICU is also configured. The below patch makes build process suppress building static Boost.Regex in this case. The wording is as follows: ghost@wind:~/Work/Boost/boost-svn$ bjam link=static runtime-link=static --with-regex .... warning: when using ICU, Boost.Regex must be a dynamic library warning: forcing link=shared runtime-link=shared for Boost.Regex Note: Building Boost.Regex with Unicode/ICU support enabled Using ICU in /usr/include Note that the warning is printed before the message that we're using ICU, which is ugly, but what I have is a minimal change. I'll tweak those configuration messages for 1.41. Comments? Ok for release branch? - Volodya

3 13

[1.40] PDB fix merge
by Vladimir Prus 23 Aug '09

23 Aug '09

Steven Watanabe has recently reported that a bug in Boost.Build caused boost libraries to be rebuilt when bjam is invoked again after a successful build. This affects msvc. I've just now reproduced and fixed this on trunk: https://svn.boost.org/trac/boost/changeset/55717 Since this fairly annoying behaviour, I would like to merge it to release branch. OK? I'd expect at least on trunk msvc tester to cycle shortly, so I should be able to merge tomorrow morning. Thanks, Volodya

3 3

[mirror] automatic reflection / boost.mirror still in development?
by strasser＠uni-bremen.de 23 Aug '09

23 Aug '09

is boost.mirror (sandbox: https://svn.boost.org/svn/boost/sandbox/mirror/boost/mirror/ ) still in development? looks a bit abandonded to me. when I first saw it I was not too excited about it because I don't think a reflection library that requires the user to register every c++ construct manually is very usable. but GCC recently (finally) integrated a plugin infrastructure, so it would be possible to automatically generate reflection information. I've worked with the GCC internal tree before, it's pretty close to the c++ constructs in the early stages. something like this would be possible: test.cpp: //include result of GCC plugin of test.cpp: #include "test.rpp" class myclass{ int myvar; double myfunction(); }; int main(){ typedef reflection::myclass::myvar::type ret; BOOST_STATIC_ASSERT(is_same<ret,int>::value); typedef reflecton::myclass::myfunction::type::return_type ret; BOOST_STATIC_ASSERT(is_same<ret,double>::value); } //or, lookup in MPL map: template<class T> char const *lookup_name(){ return reflection::type<T>::name; } or anything else you can do with MPL sequences, like iterating over class members. this would have some downsides though: - GCC the library user must install GCC. other compilers can still be used for compilation, but the code to be reflected must be portable to GCC. - license the code generating plugin must be GPLed. that does not affect the license of the user code or other parts of boost though. acceptable downsides imho, given that there are no practical alternatives in sight, like a standard conforming boost C++ parser. what do you think?

4 4

[Exception] Why is there no non-const version of get_error_info?
by Adam Badura 23 Aug '09

23 Aug '09

get_error_info takes a const exception object and returns a pointer to const data object of respective error_info. But why is there no way of getting non-const pointer (which would allow to modify the data)? This is especially strange because operator << can be used to add data to a const exception object so I don't see reason for not being able to get modifiable data back (at least from non-const exception object). Having this would allow me to safely gather exception data before throwing or during exception propagation. What I wanted was to insert an empty vector of data to the preconstructed exception object. Then obtain the vector with get_error_info (since operator << adds a copy I have to get the actual object). Then call reserve on the obtained vector and start the actual operation. During the operation I can gather (possible) error data and safely add it to the vector since memory is already reserved. In the end if any error data was gathered I will throw the preconstructed exception object. In reasonable implementation this should be safe as well. (Similar thing might be done while propagating the exception.) With current code (lack of non-const get_error_info) it is not possible. I have to get the vector from exception object. Then add data to the vector (this may fail). Then again add vector to the exception object (overwriting old vector; this may fail). And in the end throw (if needed). Alternatively I could preconstruct vector, reserve space add data to it. Then in the end if I will throw the data vector is there for me. However I still have to add it to the exception object and this still may fail. Adam Badura

4 15

[fusion] Minor interface change
by Joel de Guzman 23 Aug '09

23 Aug '09

Hi Y'all, Heads up. There will be a minor interface change. vector0 will now be a template: vector0<> to better reflect MPL. This also addresses Boost Trac ticket #1608: https://svn.boost.org/trac/boost/ticket/1608 Please adjust your code accordingly, or holler if you have any complaints. Unless there are objections, I'll commit the code as soon as all the relevant regression tests pass. Regards, -- Joel de Guzman http://www.boostpro.com http://spirit.sf.net

2 3

request for help: g++ compiler error in mapreduce library
by Craig Henderson 22 Aug '09

22 Aug '09

Can someone please help me with a g++ compiler error with my MapReduce library test program? My primary development platform is MSVC 2005 on Windows. I have an Ubuntu box with g++ 4.3.3 which I am not particularly familiar with. Compiling the test program 'mrtest' in boost-sandbox/libs/mapreduce/test on g++, I get an error which I cannot resolve: mrtest.cpp:228: error: expected primary-expression before '>' token here's the piece of code (the full source is in https://svn.boost.org/svn/boost/sandbox/libs/mapreduce/test/mrtest.cpp) typename Job::datasource_type datasource(spec); Job job(datasource, spec); job.run<boost::mapreduce::schedule_policy::cpu_parallel<Job> >(result); // <-- ERROR The code compiles and runs fine on Windows. Any ideas? Thanks -- Craig Craig Henderson <http://craighenderson.co.uk/> http://www.craighenderson.co.uk http://www.siteupdatenotification.com

2 3

Subversion update and boost release schedule
by Marshall Clow 21 Aug '09

21 Aug '09

Begin forwarded message: > Date: Fri, 21 Aug 2009 17:00:19 -0400 > From: "Kim, DongInn" <dikim(a)osl.iu.edu> > To: all-osl-users(a)osl.iu.edu > Subject: [all-osl-users] Upgrading of the OSL SVN server and trac > Sender: osl-mailman-bounces(a)wowbagger.osl.iu.edu > > Hi, > > The new version(1.6.3) of subversion was released on June 2009. It > has a lot of good features included and many bugs are fixed. > http://subversion.tigris.org/servlets/ProjectNewsList > > The OSL would like to upgrade the current subversion(ver 1.5.5) to > get the benefit of the new version. > The upgrade would start at 8:00AM(E.T.) and is expected to take > 8hours on Wed, Aug 26, 2009. > > The subversion service and trac websites services would NOT be > available during the following time period. > > Date: Wed, Aug 26, 2009 > Time: > - 5:00am-1:00pm Pacific US time > - 6:00am-2:00pm Mountain US time > - 7:00am-3:00pm Central US time > - 8:00am-4:00pm Eastern US time > - 12:00pm-8:00pm GMT > > Meanwhile, I will upgrade trac-0.11 to 0.11.5 during this downtime > too. > > Please let me know if you have any concerns or questions about this > upgrade. > > Regards, > > -- > - DongInn How will this interact with the boost release schedule? -- Marshall

2 1

[range] [1.40] iterator_range::size broken for non-random access iterators
by Ryan Gallagher 21 Aug '09

21 Aug '09

We were just upgrading from 1.34.1 to 1.39.0 and I ran into this issue which I note is still in the trunk (and I would assume the 1.40 candidate). The definition of iterator_range::size is using operator- where it should be using std::distance as it did in boost 1.34 days: """ difference_type size() const { BOOST_ASSERT( !is_singular() ); return m_End - m_Begin; } """ It used to be: """ #if BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x582)) return std::distance<IteratorT>( m_Begin, m_End ); #else return std::distance( m_Begin, m_End ); #endif """ I'm not sure why it would have changed but it's no longer working with bi-directional iterators, etc. Can we put back the old version? Can we get this fixed for 1.40? Thanks, -Ryan

2 5

Checking for return types (result_of) - redux..
by Edward Grace 21 Aug '09

21 Aug '09

Dear all, So, I have nearly figured out what to do, however it seems -- deliberately in fact, that the behaviour of result_of<???> is different when passed a function and a functor. Though I am not sure, the documentation: http://www.boost.org/doc/libs/1_39_0/libs/utility/ utility.htm#result_of "When F is a class type with a **member type result_type**, result_of<F(T1, T2, ..., TN)> is F::result_type." appears to imply that this is the way it should be (emphasis mine). So does the following in fact, http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1454.html So it seems that my original instinct (it's hard) was correct after all. Surely result_of<functor()>::type should resolve to the result type in the same way as it does for anything else callable (like a function). Anything else seems to be a big fat pain in the rear... Or, put another way, can I get what I want? Example below, the problem is s.member_function(one). Help! -ed #include <boost/mpl/assert.hpp> #include <boost/utility/result_of.hpp> #include <boost/type_traits/is_same.hpp> void void_f() {} unsigned unsigned_f() { return 1; } // We want member_function to accept any callable object (functor, // function pointer) thing that returns an unsigned integer. // // value = f(); // // Should work. struct S { template <class O> void member_function(O f) { // We require that the function/functor f returns an unsigned integer. BOOST_MPL_ASSERT( (boost::is_same<unsigned, typename boost::result_of<O()>::type>) ); unsigned sum(0); sum += f(); } }; struct one_functor { // This is apparently needed if we want to use result_of<..> on nullary functors like this. // typedef unsigned result_type; unsigned operator()() { return 1; } }; int main() { S s; one_functor one; unsigned val=one(); // We can assign to the val from the // instantiated functor. // THIS DOES NOT WORK AS IT SHOULD... s.member_function(one); // This does not work as // boost::result_of<O()> is, apparently // one_functor instead of unsigned // // Uncommenting the typedef in one_functor makes it // work - but it seems like a right pain in the rear. s.member_function(unsigned_f); // Works fine. // s.member_function(void_f); // Dies as it should! return 0; }

5 12

[1.40] OK to patch docs on release branch?
by John Maddock 21 Aug '09

21 Aug '09

Is it still Ok to patch the docs on the release branch? I have one small patch for the Boostbook docs (currently they produce invalid Docbook XML :-( ), and one for the doc/pdf/Jamfile.v2. Cheers, John.

2 2

[1.40] Any new libraries in 1.40?
by John Maddock 21 Aug '09

21 Aug '09

Are there any new libraries in 1.40 that need their docs adding to the PDF build? If there are then they need to be added to the release notes as well BTW... Just double checking yours, John.

2 2

graph_parallel
by Vladimir Prus 21 Aug '09

21 Aug '09

I notice that release branch now has libs/graph_parallel. I have a couple of questions about that: 1. I don't see any mention of this addition at http://beta.boost.org/users/news/version_1_40_0 Jeremiah, unless I've missed something, would you please add something to release notes? 2. Normally, directories under libs/ correspond to libraries. I do not see any review for new library called graph_parallel on: http://www.boost.org/community/review_schedule.html, which suggest to me this is actually part of Boost.Graph libraries. Why does it have top-level directory? Thanks, Volodya

2 1

Checking for return type -- BOOST_STATIC_ASSERT?
by Edward Grace 21 Aug '09

21 Aug '09

I'd like to be able to make certain that a function/functor returns a double precision floating point value. I was always under the impression that it's essentially impossible to check things based on return type. Is there a way to do this? Something like BOOST_STATIC_ASSERT, who knows perhaps that *can* do it.. Ideally I would like to have some sort of compile type warning so that in the following context, class myclass { public: ... template <class O> a_func(O functor) { ASSERT_IS_A_FUNCTOR(O); ASSERT_RETURN_TYPE_CONVERTABLE_TO_FLOAT(O); } }; if O is compatible with the concept of a functor and O returns a type that can be converted to a float, then we are good to go -- otherwise I'd like an intelligible error. If, for example, O is of the type 'void (*)()' I'd like it (the compiler) to spit out, "The function pointer of type O must of signature float (*)()" Any ideas? -ed ------------------------------------------------ "No more boom and bust." -- Dr. J. G. Brown, 1997

4 8

Re: [boost] [interprocess] SHARING_VIOLATION due to antivirus
by raindog＠macrohmasheen.com 21 Aug '09

21 Aug '09

I can confirm that I received your message twice. ------Original Message------ From: Isidor Zeuner Sender: boost-bounces(a)lists.boost.org To: boost(a)lists.boost.org ReplyTo: boost(a)lists.boost.org Sent: Aug 20, 2009 9:21 PM Subject: Re: [boost] [interprocess] SHARING_VIOLATION due to antivirus > Quoting Lars Hagstrom <lars(a)update.uu.se>: > > > Yes, of course it is due to bad AV. But for me it would still be handy > > if boost.interprocess was a little bit more tolerant towards that. If my > > software crashes it will be perceived as buggy, however much I blame AV... > > One thing you can do is to, at startup, detect if nod32.dll is loaded in your > process, and throw up a warning dialog to tell the user that the AV software is > buggy. > This seems inappropriate since, if anything, the operating system kernel which forces user space programmers into busy waiting for obtaining locks could be considered buggy by design in that regard. However, this bug could even be warned about at compile time, so we could solve this in boost itself. It is probably inappropriate to do so by default, but for administrators of heterogenous systems it might become handy to have a preprocessor flag which can warn if someone is about to deploy software which uses features the operating system was not designed for, so it can be considered to move the application to a more appropriate platform. Best regards, Isidor PS: The moderation software of this list seems to be broken. I sent this message before, received a "...was successfully received by the Boost mailing list" acknowledgement after a while, but over 12 hours later the message is still neither "successfully received", nor have I got any new status information. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Sent from my Verizon Wireless BlackBerry

2 1

[interprocess] SHARING_VIOLATION due to antivirus
by Lars Hagstrom 21 Aug '09

21 Aug '09

Hi, I've discovered that there is some unfortunate interaction of boost::interprocess and at least one antivirus product (ESET Nod32). The problem manifests on some installations, and the symptom is that an interprocess_exception with a native error code of 32 (ERROR_SHARING_VIOLATION) occurs when a named_semaphore (or other named objects) are opened (well, I've only seen it when opening, but depending on the AV product I guess it may happen when creating as well). Googling a bit on this I found http://support.microsoft.com/kb/316609, which suggests that AV products take exclusive locks on files just as a file is being opened, which sometimes upsets calls to CreateFile. What they suggest is doing retries when a sharing violation occurs. I'm not really saying that this is a boost.interprocess bug, but at least for me it would be handy if it was a little bit more tolerant towards AV products. I've managed (after quite a lot of hard work) to get a test environment where I can reproduce this quite easily, so I'm more than willing to help out with testing. Cheers Lars

7 12

ABI Compliance checker
by Neal Becker 20 Aug '09

20 Aug '09

I wonder if something like this could be added to boost release process to warn of incompatibilities? http://ispras.linux-foundation.org/index.php/ABI_compliance_checker

2 1

[ptr_container] new_clone overload
by Frank Mori Hess 20 Aug '09

20 Aug '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've noticed that ptr_container/clone_allocator.hpp contains an undocumented overload of new_clone that accepts a pointer-to-const: template< class T > inline T* new_clone( const T* r ); It is annoying because it doesn't support a pointer-to-non-const argument, resulting in a compile error if you try. Any chance one of the following could be done? 1) remove it 2) add a pointer-to-non-const overload 3) change it to template< class T > T* new_clone( T* r ); 4) or if you care about always returning a pointer-to-non-const change it to template< class T > typename remove_const<T>::type * new_clone( T* r ); -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkpxsyoACgkQ5vihyNWuA4WnCACgwzxlNxG8z8NAln6Ra8+fNHsn Yr8AoL5a8Bdvkoya1p99GcS1W8N2WSjk =rSZQ -----END PGP SIGNATURE-----

2 5