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

[SoC] project ideas: BigInt
by Andrew Sutton 11 Mar '10

11 Mar '10

I put BigInt back on the project ideas board with a caveat that some approaches aren't viable due to licensing concerns and that successful proposals should include discussion of those concerns. Out of curiosity, do we have a summary of those licensing issues and other concerns for this project? I haven't had the time to dig through archives. If we're accepting for BigInt, should also solicit a project for arbitrary precision floats? What about a fixed point data structure? Andrew Sutton andrew.n.sutton(a)gmail.com

4 6

[log] Review attempt
by Roland Bock 11 Mar '10

11 Mar '10

Hi, good to see that boost.log is being formally reviewed! From what I read in the documentation so far, I am really looking forward to seeing the library included in boost. I sure want to do some tests, hoping to replace our current logging system, soon, but today I can only answer the following review item: - Did you try to use the library? With what compiler? Did you have any problems? Yes, I tried and failed to compile it. Details are below. Platform: Ubuntu 8.04, 64bit, g++ 4.2.4 Intel QuadCore 2.5GHz, 8GB Ram Compilation: ============ Sounds embarassing, but I failed to compile the library. I copied the folders boost, lib and doc from boost-log-RC4 to boost_1_42_0, called ./bootstrap.sh ./bjam -d+2 --build-dir=build --with-log --prefix=/my/install/path link=shared runtime-link=shared install All looked well until this point: gcc.compile.c++ build/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi/filter_parser.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -fno-strict-aliasing -DBOOST_ALL_NO_LIB=1 -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_DLL -DBOOST_LOG_SETUP_BUILDING_THE_LIB=1 -DBOOST_LOG_SETUP_DLL -DBOOST_LOG_USE_NATIVE_SYSLOG=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -DDATE_TIME_INLINE -DNDEBUG -I"." -c -o "build/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi/filter_parser.o" "libs/log/src/filter_parser.cpp" The process cc1plus was running about 20 minutes (100%CPU, moderate RAM usage) before anything else happened. Then, after lots and lots of very long error messages, it continues like this: ...skipped <pbuild/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi>libboost_log.so.1.42.0 for lack of <pbuild/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi>attribute_set.o... Hmm. Not sure how to proceed. Should I send the whole bunch of error messages to the list as an attachment? Regards, Roland

5 13

Summer of Code 2010
by Vladimir Prus 11 Mar '10

11 Mar '10

Folks, Google Summer of Code will continue in 2010, and I believe the organization applications will be accepted starting March 8. Are we going to participate, and if so, who is taking responsibility for submitting the application? Thanks, Volodya

15 41

[log] Boost.Log formal review
by Ralf Globisch 10 Mar '10

10 Mar '10

Firstly, thanks for the wonderfully written library Andrey. * 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. Yes, definitely! The general review checklist is provided below: * What is your evaluation of the design? Good design and simple enough to use. Highly flexible and not too complex. * What is your evaluation of the implementation? Did not consider the implementation. * What is your evaluation of the documentation? Detailed documentation that details rationale, design decisions, tutorials, etc. AFAIR there was no link to the examples in the documentation, that perhaps could be added (if it isn't there already) to make it easier to get started. * What is your evaluation of the potential usefulness of the library? A logging library is a necessary debugging tool and is very useful if not neccessary in any application. A "standard" (and boost is as close to standard as it gets) logging library is long overdue. After searching extensively for a suitable logging library, I finally came across this library which satisfied all my demands. I had previously implemented my own logging library for use in a project which had specific requirements and this library met all of them and is far superior. However I should also mention that I have only recently compiled and tested the library using the provided examples as a quick guide to get going so my experience with the library is somewhat limited. * Did you try to use the library? With what compiler? Did you have any problems? Briefly, used some of the examples to get started. I would have liked to play with the library more but am submitting this review now due to limited time constraints. - Compilation: Compiled under Windows 7, Visual Studio 2008 without any problems * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I compiled the library and built a couple of the examples, changed parameters just to get an introductory feel. By no means an in-depth study. Read through the documentation. For me most importantly, I compared the functionality of the log library to the functional requirements of a logging library I wrote for use in a commercial real time streaming system and this library met all requirements and is far more flexible and superior to my own implementation. * Are you knowledgeable about the problem domain? Somewhat, I have written my own logging library although nowhere near as extensive as this one. Also, I am fairly new to boost (started using aspects of boost less than two years ago) and from reading through this mailing list I still have a lot to learn about c++/design, etc. From a previous post about the log library: > FWIW, I consider this library to be > http://en.wikipedia.org/wiki/Data_logging > and not the database/filesystem logging stuff, > http://en.wikipedia.org/wiki/Write_ahead_logging Agreed. This library allows one to log all application-related information in a simple manner and provides an effective debugging tool. Regards, Ralf -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support.

1 0

[SoC] [Asio] User input
by Andrew Sutton 10 Mar '10

10 Mar '10

A couple of years ago there was an SoC idea to extend Asio with user-input. This seemed like it may have been a pretty good idea. I think it would be great if, minimally, Boost provided some mechanism of interacting with a shell in raw input mode--in a well-designed and portable way, of course :) Did any work actually occur in this direction? Does it still seem like a viable SoC project? Would anybody be willing to mentor it? Andrew Sutton andrew.n.sutton(a)gmail.com

4 7

[bimap] Includes serialization headers even if BOOST_BIMAP_DISABLE_SERIALIZATION is defined
by Christian Holmquist 10 Mar '10

10 Mar '10

Hello, I noticed this issue with boost 1.42, but it might have been there for a while. Quite a few headers have #include <boost/serialization/nvp.hpp> I think the above should be guared with #ifndef BOOST_BIMAP_DISABLE_SERIALIZATION #include <boost/serialization/nvp.hpp> #endif Regards, Christian

2 2

[signals2] missing Jamfile and compile errors with VC8
by Michael Caisse 10 Mar '10

10 Mar '10

I was surprised to not find a Jamfile in the libs/signals2/example directory. Please find an example below. The reason I headed toward the examples is that I'm having trouble with this type of line and VC8: typedef boost::signals2::signal<void ()> signal_t; In fact doc_view_acm.cpp will not compile because of it. disconnect_and_block.cpp also has compilation errors. Results verified in 1.41 and 1.42 with VC8 and gcc 4.3.2 --------------------------------------------------------- # Boost.Signals2 Library project : requirements <source>/boost//headers ; exe hello_world_slot : hello_world_slot.cpp ; exe hello_world_multi_slot : hello_world_multi_slot.cpp ; exe ordering_slots : ordering_slots.cpp ; exe passing_slots : passing_slots.cpp ; exe extended_slot : extended_slot.cpp ; exe custom_combiners : custom_combiners.cpp ; exe disconnect_and_block : disconnect_and_block.cpp ; exe doc_view : doc_view.cpp ; exe doc_view_acm : doc_view_acm.cpp ; exe doc_view_acm_deconstruct : doc_view_acm_deconstruct.cpp ; exe postconstructor_ex1 : postconstructor_ex1.cpp ; exe postconstructor_ex2 : postconstructor_ex2.cpp ; exe predestructor_example : predestructor_example.cpp ; exe signal_return_value : signal_return_value.cpp ; exe slot_arguments : slot_arguments.cpp ; --------------------------------------------------------------- -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

2 3

[signals2] lamda placeholder collision
by Michael Caisse 10 Mar '10

10 Mar '10

I am converting some older code to use signals2. The old source uses boost.lambda which results in a collision of placeholders from bind (included by signals2) and lambda. I converted to phoenix about a year ago and I'll fix this "problem" by moving the lambdas to phoenix ... but ... what is supposed to be the correct course of action for source wanting to use both signals2 and Boost.Lambda? Regards - michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

2 2

Soc: project idea
by Michele Caini 10 Mar '10

10 Mar '10

Hi all, what about extending GIL with a watermarking framework? I'm not an expert in using GIL, however if users are able to handle images via a generic way, I think it's possible (and quite easy) to develop an infrastructure of algorithms that manage images adding watermarks. Watermarking is a know problem, today. ;-) Michele

1 0

[inspect] More changes to Inspection Report
by Beman Dawes 09 Mar '10

09 Mar '10

More changes to the Inspection Report: * Line numbers are now shown when a problem is associated with a specific line in a file. * Apple macros clashes now show the specific name causing the problem. * Spacing is optimized so that problems without line numbers don't take up so much report space. See the results at http://boost.cowic.de/rc/inspect-trunk.html Thanks to everyone who commented yesterday! --Beman

6 6

enable_shared_from_this2
by Berserker 09 Mar '10

09 Mar '10

After experiencing some troubles with boost::python and enable_shared_from_this (as already reported in the past by someone to Peter Dimov), I started looking at the new (not documented) class enable_shared_from_this2. I made two changes in init_weak_once and now it seems to support shared_from_this in constructors and shared pointers "reinitialization". The original code (from boost 1.40): void init_weak_once() const { if( weak_this_._empty() ) { shared_this_.reset(static_cast< T* >( 0 ), detail::esft2_deleter_wrapper()); weak_this_ = shared_this_; } } The "patched" code: void init_weak_once() const { // Reinitialization support if( weak_this_.expired() ) { // shared_from_this in costructors support shared_this_.reset(static_cast <T*>(const_cast<enable_shared_from_this2>(this)), detail::esft2_deleter_wrapper()); weak_this_ = shared_this_; } } I know that the static_cast/const_cast is "problematic" on VC6 (and maybe other compilers) but it could be solved using an offset from enable_shared_from_this2 * to T *. I've attached a testcase that shows the problems with the current enable_shared_from_this2 implementation (with the proposed patch it works). Any feedback about this? struct null_deleter { template <typename T> inline void operator()(T *p) const { } }; class EnableThisPtrTester : public boost::enable_shared_from_this2<EnableThisPtrTester> { public: EnableThisPtrTester() { } EnableThisPtrTester(shared_ptr<EnableThisPtrTester> &ptr) { ptr = shared_from_this(); BOOST_CHECK(ptr); } }; BOOST_AUTO_TEST_CASE(test_enable_this_ptr) { { shared_ptr<EnableThisPtrTester> ptr1; shared_ptr<EnableThisPtrTester> ptr2(new EnableThisPtrTester(ptr1)); BOOST_CHECK(ptr1 == ptr2); BOOST_CHECK(ptr1.use_count() == ptr2.use_count()); BOOST_CHECK(ptr1->shared_from_this() == ptr1); BOOST_CHECK(ptr1->shared_from_this().use_count() == ptr1.use_count()); shared_ptr<EnableThisPtrTester> ptr3 = ptr2->shared_from_this(); BOOST_CHECK(ptr2 == ptr3); BOOST_CHECK(ptr2.use_count() == ptr3.use_count()); BOOST_CHECK(ptr1->shared_from_this().use_count() == ptr1.use_count()); } { shared_ptr<EnableThisPtrTester> ptr1; EnableThisPtrTester tester(ptr1); shared_ptr<EnableThisPtrTester> ptr2 = tester.shared_from_this(); BOOST_CHECK(ptr1 == ptr2); BOOST_CHECK(ptr1.use_count() == ptr2.use_count()); ptr1.reset(); ptr2.reset(); } { EnableThisPtrTester tester; { shared_ptr<EnableThisPtrTester> ptr1 = tester.shared_from_this(); shared_ptr<EnableThisPtrTester> ptr2 = tester.shared_from_this(); BOOST_CHECK(ptr1 == ptr2); BOOST_CHECK(ptr1.use_count() == ptr2.use_count()); shared_ptr<EnableThisPtrTester> ptr3(&tester, null_deleter()); BOOST_CHECK(ptr1 == ptr3); BOOST_CHECK(ptr1.use_count() == ptr3.use_count()); shared_ptr<EnableThisPtrTester> ptr4 = tester.shared_from_this(); BOOST_CHECK(ptr4 == ptr1); BOOST_CHECK(ptr4 == ptr3); BOOST_CHECK(ptr1.use_count() == ptr4.use_count()); BOOST_CHECK(ptr3.use_count() == ptr4.use_count()); } BOOST_CHECK(tester.shared_from_this()); } }

7 22

[SoC] C++0x Project Ideas
by Andrew Sutton 09 Mar '10

09 Mar '10

Previous years' SoC project ideas suggested porting some or all of a library to C++0x. I wanted to get a read on whether or not Boost developers think that there is value in these kinds of projects. I think there are some interesting pros and cons. One aspect of these projects that worries me about these kinds of projects is that they can force programmers to work in the netherworld between two major versions of the language. They may end up porting the libraries to a CPP abstraction layer rather than actually writing C++0x, which may artificially constrain the ported implementations. I would personally see students write native C++0x than trying to write something in between. Maybe not "porting" as much as "migrating". The obvious downside is that native C++0x ports may not be easily integrated into Boost. Thoughts? Andrew Sutton andrew.n.sutton(a)gmail.com

2 2

[la] [static size matrix/vector linear algebra library] More feedback
by Agustín K-ballo Bergé 09 Mar '10

09 Mar '10

A few more things I've noticed while using Boost.LA · boost/la/all.hpp conflicts with boost/assign/list_of.hpp if Boost.Assign is included first. I think this has to do with missing includes in a few headers. · Expressions like rotx_matrix() * roty_matrix() don't work. The temporaries have to be stored in proper matrix variables first. Apparently its result type does not model a valid matrix? (just guessing). · Could we have translation_matrix and scale_matrix, just as we have rot*_matrix ? · There is no (vector) normalize function. The implementation is straightforward. · During RangeEx review, the use of views and algorithms was widely discussed. It would be good for Boost.LA to follow the same conventions decided back then. IIRC, `m | transposed` was a lazy view and `transpose(m)` returned a new (eagerly) modified value. I should go back to the archives to confirm this was indeed the conclusion. · I would like to have X, Y, Z and W placeholders be convertible to the axis versor. However I don't think this can be actually implemented. Maybe something like versor<float,3>( X ) or unit_vector<float,3>( X ) would be better. Agustín K-ballo Bergé.- http://talesofcpp.blogspot.com

2 3

[program_options] validation_error in 1.42
by Alexander Fokin 09 Mar '10

09 Mar '10

It seems the way program_options deals with validation errors was changed in 1.42. Constructor of validation_error now takes kind_t and option name and value. Before 1.42 it was possible to specify what exactly was wrong with the option value in the constructor of validation_error. Now I see no options but to subclass validation_error. Was this change intentional? Also, documentation need to be fixed to reflect these changes. More precisely, the following line in "Custom Validators" section will lead to compilation error: > throw validation_error("invalid value"); -- Best regards, Alexander Fokin, ru.elric(a)gmail.com.

3 2

[utility/swap] MSVC 10 test failure, unsigned long to std::bitset conversion invalid?
by Niels Dekker - address until 2010-10-10 09 Mar '10

09 Mar '10

There's a regression failure of Microsoft Visual C++ 10 on a unit test of the boost::swap utility: > > ..\libs\utility\swap\test\std_bitset.cpp(20) : error C2440: > 'initializing' : cannot convert from 'unsigned long' to > 'std::bitset<_Bits>' > No constructor could take the source type, or constructor > overload resolution was ambiguous > > ..\libs\utility\swap\test\std_bitset.cpp(21) : error C2440 See http://www.boost.org/development/tests/trunk/developer/output/RWVC10-boost-… Do I understand correctly that MSVC 10 does not support implicit conversion from unsigned long to std::bitset<N>? The program "std_bitset.cpp" is at http://svn.boost.org/svn/boost/trunk/libs/utility/swap/test/std_bitset.cpp It does: #include <bitset> int test_main(int, char*[]) { typedef std::bitset<8> bitset_type; const bitset_type initial_value1 = 1ul; // Line 20. const bitset_type initial_value2 = 2ul; // Line 21. // [...] return 0; } Can anyone here reproduce the compile error? If so, would it be helpful to replace line 20 and 21 by using parentheses? As follows: const bitset_type initial_value1(1ul); const bitset_type initial_value2(2ul); Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center

6 22

[range] strings
by Domagoj Saric 09 Mar '10

09 Mar '10

Currently, the following assertion: char const test_string[] = "a test string"; assert( test_string == boost::as_literal( test_string ) ); fails while the following one: assert( test_string == boost::as_literal( test_string ).advance_end( 1 ) ); passes because the left-hand side parameter of operator== is implicitly converted to a boost::iterator_range<> object which _includes_ the trailing zero (because it is treated as any other array) while the boost::iterator_range<> returned by boost::as_literal<>() _excludes_ the trailing zero... I 'know' that there is no 'happy' solution for this because the status quo is 'consistent' across all types but it, on the other hand, creates problems (or unexpected results), like the one outlined above, when strings, char pointers and literals are used...For this reason I would prefer more the other 'less than happy' solution that would treat strings in a special way (by never including the trailing zero)... Another problem is that the conversion, implict or otherwise, from a char container/range whose iterators are not plain char pointers (e.g. std::strings in 'secure STL' implementations) does not work (does not compile). My last post in the [program_options] thread offers a 'fix'. Yet another problem is that the as_literal<>() template function does not use the fact that it was passed an array to implicitly/directly deduce the length but it still calls std::strlen(). The make_range() function it calls for that: make_range( T* const r, bool ) { return iterator_range<T*>( r, r + length(r) ); } is also duplicated by: inline const char* str_end( const char* s, const char* ) { return s + strlen( s ); } ... Yes, some will object that the 'desired' direct deduction of length would be broken for 'typical' local buffers that are not completely filled (if there is no clear way of distinguishing them from literals): void foo() { char buf[ 256 ] = "a small string"; as_literal( buf ).size() == std::strlen( buf ); // in status quo as_literal( buf ).size() == _countof( buf ) - 1; // as proposed } but that could then also be said for the current implict conversion from such a "char buf[ 256 ]" into a boost::iterator_range<char const*>... I'd vote that this be handled with a runtime assertion that if a plain char array is passed it must be 'completely filled' (i.e. strlen( buf ) == _countof( buf ) ) otherwise the range must be explicitly constructed (iterator_range<char const *>( buf, buf + actual length )... Additionaly the above mentioned implementations of make_range() and str_end() add two extra instructions (substraction and addition) because they use strlen() that works with 'indexes'/size which then have to be converted to pointers... Additionaly#2 the boost::range_detail::is_char_ptr() function in as_literal.hpp is a runtime function when it seems it could be a metafunction... -- "What Huxley teaches is that in the age of advanced technology, spiritual devastation is more likely to come from an enemy with a smiling face than from one whose countenance exudes suspicion and hate." Neil Postman

2 4

Syntax colouring for Notepad++
by Paul A. Bristow 09 Mar '10

09 Mar '10

Does anyone have or know of a user defined language plugin for Notepad++ to provide syntax colouring for Quickbook and jamfiles (makefile is reasonable but not perfect)? (or suggestions for syntax colouring other text editors?) Thanks Paul --- Paul A. Bristow Prizet Farmhouse Kendal, UK LA8 8AB +44 1539 561830, mobile +44 7714330204 pbristow(a)hetp.u-net.com

4 3

[SoC] Submission Template
by Andrew Sutton 09 Mar '10

09 Mar '10

I've created a student submission template as part of the SoC application (which I'm currently working on). It's largely reconstructed from last year's template, with a couple of modifications. Can mentors from previous years and prospective mentors for this year please look over the template to see if there's any other information that might be useful? It can be found here: https://svn.boost.org/trac/boost/wiki/SoCSubmissionTemplate Thanks, Andrew Sutton andrew.n.sutton(a)gmail.com

3 3

Re: [boost] [contract] Released Contract Programming Library on SourceForge
by Andrzej Krzemienski 09 Mar '10

09 Mar '10

> I have released on SourceForge a library that implements Contract > Programming (a.k.a. Design by Contract(TM) ) for C++. I am considering > to submit this library to Boost (as Boost.Contract). > > Comments? Hi, As I already said, I am very glad that we can see a good Contract library for C++. I have not used it yet, but I base my first opinion on the documentation; the topics it mentions (sub-contracting, disabling contract checking within contract checks, the "oldof"), and references, proves that you have thoroughly investigated the subject. This is first such library for C++ that I am aware of. I am almost sure I will not use it in my work, in production code. I have trouble convincing my colleagues to use templates, as they are not used to "non-Java" syntax, and they find it suspicious. I am not sure how I would be able to convince anyone to writing: (class)(copyable)(myvector)(inherit)(pushable<T>)(public)(void)(push_back)( (const T&)(element) ) I am not even convinced myself. The IntelliSense will go mad. I understand the constraints you are under, but still... Perhaps if you do require this syntax, you should offer something more in exchange than only contract checking: hooks for IntelliSense, meta-data of contract-checked functions that the user can use like other type traits, etc... On the other hand, I believe the library is a very important step to introducing contract checking into C++ standard. Contracts were labeled as "No active interest today, but open to resubmit in future". Having gained a practical experience with C++ contracts, both implementability and usage, may be a good argument for reconsidering the proposal. C++ is so particular a language that the experience from Eiffel, which is mainly an OO language, usually would not apply; for instance, I could define equality as: bool operator==( MyType const& lhs, MyType const& rhs postcondition( result ) { result == !( lhs != rhs ); }; bool operator!= MyType const& lhs, MyType const& rhs ) postcondition( result ) { result == !( lhs == rhs ); }; or: bool operator==( MyType const& lhs, MyType const& rhs ); template< typename T > bool operator!=( T const& a, T const& b ) { return !(a == b); } // no post-condition required Which solution should I prefer? For an another example, if I am a defensive programmer, should I write: int compute_area() const postcondition( ans ) { ans > 0; }; or: unsigned int compute_area() const postcondition( ans ) { ans != 0; }; or: PositiveInteger compute_area() const; // compile-time checking - even better Similarly, for loop variants, I would be interested to know how it can or cannot or need not be used in more c++ specific loops: for( auto v : setOfValues ) { process(v); } How do I define a variant? Or is a variant needed? Perhaps the sole usage of "for each" guarantees termination? Or this one: std::ofsteam file("input.txt"); std::string text; while( file >> text ) { process(text); } Regards, &rzej

2 1

Re: [boost] [gil] External header files.
by Daniel James 09 Mar '10

09 Mar '10

On 1 March 2010 18:54, Enrique Nieloud <enieloud(a)gertrudisgraphics.com> wrote: > > I just wanted to report that the following two links are broken: > > boost/gil/extension/numeric/sampler.hpp > boost/gil/extension/numeric/resample.hpp > > > In the file: > http://www.boost.org/doc/libs/1_42_0/libs/gil/example/resize.cpp That's a pain. The html file is generated automatically from the source file, which states that it's including files that don't come with boost. It'd be better if they weren't expected to be in the boost file system. Daniel

4 4

[asio] Generating docs from trunk drops reference links
by Mateusz Loskot 09 Mar '10

09 Mar '10

Hi, I'm generating HTML docs for Boost.Asio from sources in SVN trunk (r60372) and I've noticed that all elements in Core -> Free Functions section of the Reference are not linked (Core, second column from left) So, all the links in this box point to HTML docs root directory file:///home/mloskot/dev/boost/_svn/trunk/libs/asio/doc/html/ However, the docs on website for Asio in Boost 1.42 does look correct: http://www.boost.org/doc/libs/1_42_0/doc/html/boost_asio/reference.html While generating, Boostbook (or Quickbook) does report this problem as follows: Error: no ID for constraint linkend: boost_asio.reference.read. Error: no ID for constraint linkend: boost_asio.reference.write. ... I'm generating the docs by executing sequence of two commands: mloskot@dog:~/dev/boost/_svn/trunk/libs/asio/doc$ perl doxy2qbk.pl mloskot@dog:~/dev/boost/_svn/trunk/libs/asio/doc$ bjam --v2 I attached boost-asio-docs-gen-log.txt.zip with .txt file which contains complete output of these two commands. I'm working on Linux Ubuntu 9.10 (64-bit) with the tools of versions: $ doxygen --version 1.6.1 $ bjam --version Boost.Build V2 (Milestone 12) Boost.Jam 03.1.18 $ quickbook --version Quickbook Version 1.5 Am I doing anything wrong or missing any step or Asio docs generator has changed after 1.42? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org

1 0

Re: [boost] [Review] ITL review starts today, February 18th
by Brian Wood 08 Mar '10

08 Mar '10

Joachim Faulhaber writes: >2010/3/7 Brian Wood <woodbrian77(a)gmail.com>: >> I was being blunt in order to let you know where I stand. >> I think the ITL is an interesting library and we may add >> marshalling support for it at some point. ? My suggestion >> is to not use the exact same class names in your library >> as are already used in the standard library. ? With the >> Boost::Intrusive library there is some of that as well. >> However, he has a class called ?rbtree that is an >> alternative to intrusive::(set and multiset). ?That rbtree >> class I support while for the time being I don't support >> the intrusive set or multiset. ? ?I'm not familiar enough >> with your library to know if an itl_rbtree class would be >> workable, but mention it just in case. > > Why not just support the class templates with the names that you like > and just ignoring the rest? I may do that. I was hoping to hear your thoughts on the itl_rbtree idea. Brian Wood http://webEbenezer.net (651) 251-9384

1 0

Boost.Atomic on OSX Leopard, x86-32?
by Josh Faust 08 Mar '10

08 Mar '10

Hey all, I'm having some trouble getting Boost.Atomic working properly on OSX Leopard. After wrangling compilation (all instances of "lock" -> "lock;", and "+r" -> "+q"), I'm hitting what looks like bad generated assembly. The following code, compiled with -O2: #include <boost/atomic.hpp> #include <stdio.h> using namespace boost; int main() { signed char a1, c1; char a2, c2; { atomic<char> a(41); char c = a++; a1 = a.load(); c1 = c; } { atomic<signed char> a(41); signed char c = a++; a2 = a.load(); c2 = c; } printf("%d %d\n", a1, c1); printf("%d %d\n", a2, c2); } produces: Macintosh-2:test josh$ ./simple2 42 41 93 41 Changing the first atomic to be the same type as the second (atomic<signed char>) produces the correct output (42 41 for both). This same problem shows up with int vs. unsigned int as well (have only tested those two). The assembly that produces the correct output: LCFI2: movl $1, %ecx ^^^^^^^^^^^^^^^^ Move 1 into ecx movl %esp, %ebp LCFI3: movl %ecx, %eax ^^^^^^^^^^^^^^^^ And eax subl $72, %esp LCFI4: movl %ebx, -12(%ebp) LCFI5: movl %esi, -8(%ebp) LCFI6: movl %edi, -4(%ebp) LCFI7: call L11 "L00000000001$pb": L11: popl %ebx movb $41, -25(%ebp) lock; xaddb %al, -25(%ebp) ^^^^^^^^^^^^^^^^^ first reference after assignment to eax (through al) movzbl -25(%ebp), %edx lock; addl $0, (%esp) movb $41, -25(%ebp) lock; xaddb %cl, -25(%ebp) ^^^^^^^^^^^^^^^^^ first reference after assignment to ecx (through cl) movl %ecx, %edi movzbl -25(%ebp), %ecx movb %cl, -41(%ebp) lock; addl $0, (%esp) The assembly that produces the incorrect output (when one is atomic<char> and the other is atomic<signed char>): movl $1, %eax ^^^^^^^^^^^^^^^^^ Move 1 into eax movl %esp, %ebp LCFI3: subl $72, %esp LCFI4: movl %ebx, -12(%ebp) LCFI5: movl %esi, -8(%ebp) LCFI6: movl %edi, -4(%ebp) LCFI7: call L11 "L00000000001$pb": L11: popl %ebx movb $41, -25(%ebp) lock; xaddb %al, -25(%ebp) ^^^^^^^^^^^^^^^^^^ First reference after assignment to eax (through al) movzbl -25(%ebp), %edx lock; addl $0, (%esp) movb $41, -25(%ebp) lock; xaddb %cl, -25(%ebp) ^^^^^^^^^^^^^^^^^^ First reference to ecx (through cl), but NO ASSIGNMENT. cl is garbage? movl %ecx, %edi movzbl -25(%ebp), %ecx movb %cl, -41(%ebp) lock; addl $0, (%esp) I am by no means an assembly expert (this has been a huge learning experience in fact) but this doesn't look right. I'm on: gcc version 4.0.1 (Apple Inc. build 5493) OSX 10.5.8, Intel Core 2 Duo (2.16 GHz) Just pulled a git clone of Boost.Atomic from http://git.chaoticmind.net/boost.atomic, rev. 886a675aa982ab5875c7bc98697b2eb26c134d03 (I think... I have no experience with git, just grabbed the top guid from "git log"). building without -O2 yields correct results. Anyone with more knowledge than I have any ideas? Am I being stupid and something else is wrong? Josh

2 4

Re: [boost] [Review] ITL review starts today, February 18th
by Brian Wood 08 Mar '10

08 Mar '10

Joachim Faulhaber writes: >2010/3/7 Brian Wood <woodbrian77(a)gmail.com>: >> Joachim Faulhaber writes: >> > >> If you stick >> with the names of some of the classes that you have today, >> at the very least, I'll put off developing marshalling support for >> the library. > >To give you a little feed back: The sentence above didn't exactly make >me feel in peace with you ;-/ But I'm open for your suggestions. I was being blunt in order to let you know where I stand. I think the ITL is an interesting library and we may add marshalling support for it at some point. My suggestion is to not use the exact same class names in your library as are already used in the standard library. With the Boost::Intrusive library there is some of that as well. However, he has a class called rbtree that is an alternative to intrusive::(set and multiset). That rbtree class I support while for the time being I don't support the intrusive set or multiset. I'm not familiar enough with your library to know if an itl_rbtree class would be workable, but mention it just in case. Regards, Brian Wood http://webEbenezer.net (651) 251-9384

2 1

Re: [boost] [Boost-users] [Review] ITL review starts today, February 18th
by Joachim Faulhaber 08 Mar '10

08 Mar '10

Hi Jeff, thank you for your review of the ITL. You have been supportive in the course of the development at different points giving feed back about shortcomings and helping with code patches and useful suggestions. I am glad to hear that you are actually using the library for real world applications already. 2010/3/8 Jeff Flinn <TriumphSprint2000(a)hotmail.com>: >> Please always state in your review, whether you think the library should >> be >> accepted as a Boost library. > > Yes, I think the library (with the interface improvements brought out during > the review) should be accepted into boost. I've already successfully used > the library with it's existing interface in a commercial product. > >> - What is your evaluation of the design? > > As brought up during the course of the review period my main concerns for > the library's interface are: > > 1) the bloated size of the interval class with it's dynamic bound data > member. This is being addressed by Joachim providing an interface to allow > use of static bound interval classes. > > 2) the fat interface on the interval class. In my view the myriad of > mutators would best be replaced with free functions in terms of the > interval's extents and return a interval passing the calculated extents to > an interval constructor which enforces the interval's invariant(s). There > should also be a method to construct an interval given unordered extents > that effectively does interval(min(arg1, arg2), max(arg1, arg2)). > > 3) better integration of std and user defined data types en lieu of itl's > specific types. Joachim has agreed to improvements in this area. I think we have agreed in the various points involved. > 4) I'd also like to see std::inserter "just work" with the containers. I discovered that it does not just work, because for std::insert_iterator there is an invariant involved that expects the inserted to be a non empty element of the container, that the element is inserted into. This invariant is broken with interval containers because an interval/segment is not an element of an interval container. > I shouldn't have to expect to look for the itl specific adder to do this. This > was the most common usage my applications had for populating interval > containers using std::copy/transform from my applications existing data > structures. > >> - What is your evaluation of the implementation? > > Seems adequate. I was able to port to the portions I needed to CodeWarrior > 9.4 (from 2003?). IIRC, Joachim integrated the changes(simplifications) that > allowed itl to work in this environment. I added all the changes suggested, but I remember that important parts of the code, itl global operators in particular, still did not compile with CW. I tried to set up CW myself, but encountered too many problems and gave up :( > Performance for the scale of problems I've been dealing with were fine, but > as has been discussed scaling to larger sizes of millions of items may > require some specialized containers. I don't see this as a problem, it's > analogous to std::map and std::unordered_map. I share this view. > Hmm, It just occurs to me that for my application I could void the N^2 size > issue of a split_interval_map<int, set<> > with a non_combining_map<int, > data> that allowed me to iterate through all items that overlap with an > arbitrary interval in and ordered fashion. That's not much different from a > std::map<interval, data>, but with some more interval specific wrapping of > the upper/lower_bound/equal_range methods. > >> - What is your evaluation of the documentation? > > I was able to get up and running fairly quickly. As discussed some of the > colorful terminology got in the way rather than helping. Also I had expected > to just be able to populate with std::inserter, and had trouble finding docs > related to this. The example for copy/transform helped, but even during this > review I have trouble finding the docs for itl::adder/inserter. True, escaped my notice. Has to be added. >> - What is your evaluation of the potential usefulness of the library? > > Very, I've come across needs for this capability in 3 different jobs in 3 > very different industries. I've had domain specific solutions and was > looking to create just such a generic library when Joachim submitted his > library. That's interesting. I had the basic ideas and first implementation in 1999 / 2000 and I had the immediate impression that it should be made available to the public domain. But due to other projects and commercial copyright of the first version, I did not have the opportunity to make it open source for years. I always thought someone else would be faster than me ;) >> - Did you try to use the library? With what compiler? Did you have any >> problems? > > Yes, the library is being used in a commercial application built with > CodeWarrior 9.4 on Mac/Windows and with VC8 and XCode 3.x. The library > required some modifications to the template declarations for CodeWarrior. Is it now fully or still only partially compilable with CW? >> - How much effort did you put into your evaluation? A glance? A quick >> reading? In-depth study? > > I read through the documentation, integrated the library with production > code, dug through compilation error messages and headers on CodeWarrior to > port a portion of the library. I've profiled code using itl to understand > performance implications. > >> - Are you knowledgeable about the problem domain? > > Yes, I've designed/implemented/optimized integral open-closed Interval and > IntervalSet classes for use in previous projects. Thanks again for your review and the support that you provided for the ITL library. Cheers, Joachim

1 0