- Boost - lists.boost.org

Architecture Analysis of the boost libraries, e.g. spirit
by Bernhard Merkle 18 Feb '09

18 Feb '09

Hi boost developers, I have a question regarding the architecture of boost libraries. First some (short) background info: I have done some architectural analysis in the past for C++, C and Java projects. It is a static toolbased analysis approach and essentially it enables you to compare the "should"-architecture with the "is"-architecture. Nearly all projects suffer from some architectural decay over time (e.g. unwanted dependencies etc.) So I was interested how well those tools for architectural analysis cope with C++ template code and boost is an ideal candidate. :-) I have already successfully analyzed the boost spirit library. The architecture for spirit is documented under http://www.boost.org/doc/libs/1_38_0/libs/spirit/classic/doc/organization.h… and if that is still the "should"-architecture then i was already able to find some deviations/violations in the "is"-architecture. So my question: should all modules of Core (scanner, primitives, composite, non_terminal) be independent of each other ? other questions: - are there architectural documents for the other libraries ? - which would be good candidates from your point of view ? (I think e.g. analyzing dependencies to the mpl libs is interesting) - is there a common rule which parts are public and which are private ? (I saw some impl directories but am a bit unsure about the API stuff) - is there a document describing the dependencies between the different libs (the "should" architecture). (I know of the bcp tool but this documents the "is"architecture essentially) sorry for the long post, but I think this is really interesting stuff and I am open to contribute in the architectural area :-) kind regards, Berni.

1 0

Re: [boost] Formal Review Request: Boost.String.Convert
by Vladimir.Batov＠wrsa.com.au 18 Feb '09

18 Feb '09

Upgraded to the version 0.10. Added boost::string::is_string<T> SFINAE-based check. That allowed to discriminate the applicability of conversion functions. Now they demand one of the parameters to be a string (in broad sense, like C strings, std::(w)string, chat/wchar_t-based containers) and the other *not* a string. Have straighten up the main boost::string::convert() interface (was quite broken) so that all the tests now run as expected. g++ 4.2.4 (Linux) and Visual Studio 2008 are happy. Thanks, Vladimir.

4 6

[future|interprocess] Could futures live in shared memory and synchronize process?
by vicente.botet 18 Feb '09

18 Feb '09

Hi, I'm working on Boost.Synchro a synchronization library that try to provide generic synchronization mechanism that can be used so synchronize threads or process. As a future is a synchronization mechanism, I was wondering if futures are intrisic of mutil-threaded programs and so they live in the protected process memory or if the concept can be used in a multi-process context and have futures/promises living on shared memory. Ion, what do you think, could it be possible to use futures/promises to synchronize process? Have some one a specific use case for this? Best regards, _____________________ Vicente Juan Botet Escribá

3 5

[alogrithm] compile error with VS2008 in debug build (boost 1.38)
by Hansi 18 Feb '09

18 Feb '09

Hello, I have a strange problem. When I make a debug build from my program which uses minmax_element I get the following compile error: 1>c:\program files\microsoft visual studio 9.0\vc\include\utility(57) : error C2664: 'std::_Vector_iterator<_Ty,_Alloc>::_Vector_iterator(const std::_Vector_iterator<_Ty,_Alloc> &)' : cannot convert parameter 1 from 'int *const ' to 'const std::_Vector_iterator<_Ty,_Alloc> &' 1> with 1> [ 1> _Ty=int, 1> _Alloc=std::allocator<int> 1> ] 1> Reason: cannot convert from 'int *const ' to 'const std::_Vector_iterator<_Ty,_Alloc>' 1> with 1> [ 1> _Ty=int, 1> _Alloc=std::allocator<int> 1> ] 1> No constructor could take the source type, or constructor overload resolution was ambiguous 1> d:\projects\sandbox\boosttests\statistic\statistic.cpp(43) : see reference to function template instantiation 'std::pair<_Ty1,_Ty2>::pair<int*,int*>(const std::pair<int *,int *> &)' being compiled 1> with 1> [ 1> _Ty1=std::_Vector_iterator<int,std::allocator<int>>, 1> _Ty2=std::_Vector_iterator<int,std::allocator<int>> 1> ] 1>c:\program files\microsoft visual studio 9.0\vc\include\utility(57) : error C2664: 'std::_Vector_iterator<_Ty,_Alloc>::_Vector_iterator(const std::_Vector_iterator<_Ty,_Alloc> &)' : cannot convert parameter 1 from 'int *const ' to 'const std::_Vector_iterator<_Ty,_Alloc> &' 1> with 1> [ 1> _Ty=int, 1> _Alloc=std::allocator<int> 1> ] 1> Reason: cannot convert from 'int *const ' to 'const std::_Vector_iterator<_Ty,_Alloc>' 1> with 1> [ 1> _Ty=int, 1> _Alloc=std::allocator<int> 1> ] 1> No constructor could take the source type, or constructor overload resolution was ambiguous Is this a know issue. Is something wrong in my program? Best regards Hansjörg #include <algorithm> #include <vector> #include <iostream> #include <boost/algorithm/minmax_element.hpp> #include <boost/array.hpp> #include <boost/timer.hpp> using namespace boost; using namespace std; typedef array<int,100000000> dataarray; void do_tests(dataarray& data) { { timer t; std::pair< std::vector<int>::iterator, std::vector<int>::iterator > result = boost::minmax_element(data.begin(), data.end()); cout<<"min_max: minmax_element:"<<t.elapsed()<<endl; cout<<"minVal="<<*result.first<<",maxVal="<<*result.second<<endl; } } dataarray data; int main(int argc, char const* const* argv) { cout << "sorted array:" << endl; for(unsigned int i = 0; i< data.size();i++) { data[i] = i; } do_tests(data); cout << "random array:" << endl; std::srand(0); for(unsigned int i = 0; i< data.size();i++) { data[i] = std::rand(); } do_tests(data); return 0; }

4 4

_SECURE_SCL for msvc
by Hansi 18 Feb '09

18 Feb '09

Hello, the problem with _SECURE_SCL define was already discussed a few times on this list. But til now it came never to a end. Is there any interrest to get also compiled libraries for _SECURE_SCL enabled and _SECURE_SCL disabled? I think this would be really important because this compiler switch changes the abi and for that programs can crash. I think that a lot of people disable it already in their own programs, but may be they don't compile the boost libraries with this switch... Any comments? Regards Hansjörg

6 7

Re: [boost] Review Request: Introduction of boost::string namespace and string-conversion functions
by Vladimir.Batov＠wrsa.com.au 18 Feb '09

18 Feb '09

Thank you all who replied so far. It is very much and truly appreciated. Tally for far 1. The idea in principle seems to be largely accepted. Phil Endecott raised a concern if the effort was not a wheel-reinvention due to string/number conversions in N2408. I feel N2408 does not have as broad scope and has serious limitations (no user-type conversions, no handling of any container<char>, etc.) 2. The name of the namespace. People largely seem content with "boost::string". Andrey Semashev expressed a concern that the name was too generic and could clash with std::string (using namespace boost; using namespace std). A fair point. However, I do not feel it is a boost::string "problem" per se but rather the "problem" with using-directives (or rather mis-using-directives). Using-directives beat the whole purpose on a namespace and best avoided (see Stroustrup 8.2.3). From my actual experience it was not an issue. Long time ago I've introduced aux::string in two sizeable projects and honestly did not have one single complain about name clashing. Bo Persson also expressed a concern siting it'll make it "very hard to propose the utilities for inclusion in a future language standard". May be. May be not. When things of that magnitude happen (which seem quite remote at present) components get moved from a namespace to a namespace (several times) anyway. Like some stuff from the "boost" namespace moving to the "tr1" namespace just ultimately to be moved to the "std" namespace. Therefore, unless something major comes up later we are settling on "boost::string". 3. Naming of the conversion functions. The "to/from/is" set seems to sit well with the majority of people. The to_string/from_string was floated around as alternatives. I feel that the "_string" extension indeed serves a mildly useful purpose when the "string" namespace is obfuscated. Like namespace boost::string obfuscated; string str = obfuscated::from(i); // What the...? string str = obfuscated::to_string(i); // Somewhat better but still... When used sensibly string str = boost::string::from(i); or namespace boost::string str; string str = str::from(i); the intention seems clear and the following feels like a tautology: string str = boost::string::to_string(i); Robert Stewart mentioned that "is" is a poor name choice. It doesn't imply "can convert to" and can be expensive to execute. Fair enough. I'll keep the name around as a placeholder for a rainy day. We might not need it at all if we agree on something along the following lines: // No throw, return default on failure, dunno if failed. int i = boost::string::to<int>(str, default_value); // No throw, return default on failure, can check if failed. boost::string::value i = boost::string::to<int>(str, default_value); if (i.good()) successfully converted 4. String-To-Something Conversion Interface. Considerable number of people were not exactly happy with my off the cuff int i = boost::string::to<int>(str)(default_value); Well, I do not like it either... I just like saying/suggesting things that I regret later. :-) I probably got carried away by the functional-chain-ability concept. The main reason (for me) it is not good is that it imposes the default-constructibility requirement. I think people on the original lexical_cast-realted thread were pretty content with int i = boost::string::to<int>(str, -1); syntax. If so, then we won't need int i = to(str).or_default(-1) int i = to(str, default_ = -1) Can we agree on the following interface: template<class T, class String> boost::string::value<T> boost::string::to(String const&, T const& =T()) throw(); The usage is // Does not throw, returns -1 on failure. Don't care if failed int i1 = boost::string::to<int>(str, -1); // Does not throw, returns -1 on failure. Care if failed boost::value<int> i2 = boost::string::to<int>(str, -1); if (i2.good()) successful conversion6. 5. Formatting with manipulators. I've implemented a prototype and it works just fine. string str = "0xFF"; int i1 = boost::string::to<int>(str, -1) >> std::hex; // returns 255 int i2 = boost::string::to<int>(str, -1)(std::hex); // Same as above For the time being I keep both interfaces (via () and >>). 6. Something-To-String Conversion Interface. That did not seem to generate much heat at all. I'll summarize to make sure we see it the same way: template<class T> boost::string::value<std::string> boost::string::from(T const&) throw(); Does not throw. No default value (do we need one?). Returns string() of failure. Usage: std::string s1 = boost::string::from(-1); // 'int' type deduced std::string s2 = boost::string::from<double>(-1); // 'double' type forced std::string s3 = boost::string::from(15) >> std::hex; // returns "0xF" if (s1.empty()) conversion failed boost::string::value<std::string> s4 = boost::string::from(-1); if (s4.good()) conversion succeeded 7. Check-Convertibility Interface. If we agree on the behavior above (using boost::string::value), then the separate boost::string::is does not seem needed. 8. Throw/No-Throw Behavior. You might have noticed that the interface above *never* throws anything on failure. I would like to highlight the fact (as it's different from lexical_cast behavior) and make sure people are happy with it. Those who need an exception thrown could do boost::value<int> i2 = boost::string::to<int>(str, -1); if (!i2.good()) throw something youself; Is it satisfactory? 9. Requested features. a) Handling any container<char> (Phil Endecott). I implemented a rough cut using boost::range and it handles std::(w)string, char/wchar_t const* with ease. To handle any container we might look into extending the interface with something like template<class T, class Range> boost::string::value<T> boost::string::to(Range const&, T const& =T()) throw(); I have not looked into it throughly yet though. b) Integration with Spirit (Hartmut Kaiser). My focus is currently on the interface. Then, we can look at Spirit+boost-string behind it as a separate issue as it requires Joel (and other Spirit developers) involved. c) locale. I have not looked into it at all and I am not sure I am well-qualified. OTOH I hope it'll fit into the proposed interface as string s3 = boost::string::from(15) >> std::hex >> locale-related-functionality; or string s3 = boost::string::from(15)(std::hex)(locale-related-functionality); If so, then we can return to the issue when we get all the above taken care of. Thanks, Vladimir.

10 20

Re: [boost] Formal Review Request: Boost.String.Convert
by Vladimir.Batov＠wrsa.com.au 18 Feb '09

18 Feb '09

I am not sure I can answer all the questions sent so far individually. Some of the questions have been discussed/answered and hopefully this email might be of some help also. RE: convert() and directionality I've decided to stick with Robert's convert() (and his op>> as well. Thank you, Robert) as I agree with his view to leave the door open for possible extensions. That attitude has already proven useful to extend the conversions onto string-to-string (that I did not anticipate). With convert() it'll be easy to extend the existing functionality onto wstring<->u8string, etc. In string-to-string context the directionality issue is mute and I personally find convert() as very much appropriate. Even with string-to/from-type conversions directionality is still present (via types). I agree that with convert() the directionality is somewhat more subtle compared with to/from (or whatever the alternatives). RE: to/from: Yes, I understand quite a few people are not exactly thrilled with to/from. However, it is still here. Apologies. There are two (and a half) reasons for that -- 1) conceptual. Even though I am getting to like convert() more and more, I am still occasionally longing to express explicitly the direction of the conversion with to/from. 2) technical. This to/from-based interface is used in my current project and I am reluctant to needlessly disturb it in any way to avoid code reviews, etc. etc. 2.5) I happen to still like its terseness and directness as my code simply reads "string::to<int>" for string-to-int. I am getting more and more comfortable with convert() though. However, I've been using to/from for about 5 years and it feels like old shoes. Just give me some time to get used to something new. RE: to_string/from_string Somehow I did not like to_string/from_string from the start. I dunno. Just irrational primal dislike. I am sorry. Now it seems I might try putting some smoke-n-mirrors around that by justifying it by the functionality that Hartmut mentioned -- conversion from one symbol/character set to another. I've implemented it (v0.14) and it it like this: string encrypted = boost::string::convert(naked_str) >> my_cypher; string decrypted = boost::string::convert(encrypted) >> my_cypher; That is, we are converting from a string to again a string. In such context I very much like the direction-less nature of convert(). >> My problem is that I can't think of a case when I would be writing >> code that doesn't "know" if it is going "to" or "from" string. Again, string-to-string (or string-from-string) comes to mind. Any directionality seems superfluous and I personally find the code above quite appropriate. Any other suggestions are always welcome as hartmut only brought it up yesterday and I only gave it a cursory thought (can I say a "cursory" thought? it kinda does not feel right). >> I've needed to convert things specifically to std::string plenty of >> times to justify a simple interface where to_string returns >> std::string. I want to be able, in a header file, to just say: >> struct foo; >> std::string to_string( foo const & ); >> std::string to_string( foo const &, fmt ); >> and be done with it. I hope that the suggested interface and implementation allow enough flexibility and simplicity without limiting one to std::string only: namespace bstring = boost::string; std::string s1 = bstring::convert(foo); std::string s1 = bstring::convert(foo) >> std::hex; // add formatting std::Wstring s1 = bstring::convert(foo, std::wtring()); // convert to wide string std::Wstring s1 = bstring::convert<std::wstring>(foo); // same as above RE: convert("5").to<int>(), I like Scott's suggestion of the above. It looks cute. OTOH I am not sure where to stick it into though. Thanks, Vladimir.

4 3

[foreach] HELP NEEDED: intel-vc9-win-11.0
by Eric Niebler 18 Feb '09

18 Feb '09

Boost.Foreach is failing its tests on trunk on the intel-vc9-win-11.0 platform. If there is anyone with access to this platform who would like to run a couple of quick tests, you will be generously rewarded in your next life. Can't beat that. All you have to do is run foreach's tests 4 times with a slightly different config each time. In foreach.hpp, comment out all the config preprocessor gunk (everything between #include <boost/detail/workaround.hpp> and #include <boost/mpl/if.hpp>) and replace it with one of the following: #define BOOST_FOREACH_COMPILE_TIME_CONST_RVALUE_DETECTION or #define BOOST_FOREACH_RUN_TIME_CONST_RVALUE_DETECTION or #define BOOST_FOREACH_NO_CONST_RVALUE_DETECTION or #define BOOST_FOREACH_NO_RVALUE_DETECTION Report the number of test failures each time. Your karmic reward awaits. Thanks in advance, -- Eric Niebler BoostPro Computing http://www.boostpro.com

2 3

Re: [boost] [Boost-commit] svn:boost r51307 - trunk/libs/ptr_container/test
by Juergen Hunold 18 Feb '09

18 Feb '09

Hi Thorsten ! On Tuesday 17 February 2009 23:42:41 nesotto(a)cs.aau.dk wrote: > Author: nesotto > Date: 2009-02-17 17:42:39 EST (Tue, 17 Feb 2009) > New Revision: 51307 > URL: http://svn.boost.org/trac/boost/changeset/51307 > > Log: > updated for nasty erase() bug.. > Text files modified: > trunk/libs/ptr_container/test/Jamfile.v2 | 3 ++- > trunk/libs/ptr_container/test/associative_test_data.hpp | 5 ++++- > trunk/libs/ptr_container/test/ptr_set.cpp | > trunk/libs/ptr_container/test/ptr_unordered_set.cpp +++++++-------------- 5 files changed, 70 insertions(+), > 18 deletions(-) > > Modified: trunk/libs/ptr_container/test/Jamfile.v2 > =========================================================================== >=== --- trunk/libs/ptr_container/test/Jamfile.v2 (original) > +++ trunk/libs/ptr_container/test/Jamfile.v2 2009-02-17 17:42:39 EST (Tue, > 17 Feb 2009) @@ -38,5 +38,6 @@ > [ sc-test ptr_unordered_set ] > [ sc-test ptr_unordered_map ] > [ sc-test ptr_circular_buffer ] > - > + [ sc-test ptr_multi_index_container ] > + It seems you forgot to "svn add ptr_multi_index_container.cpp" . Can you please add it as this completely breaks regression testing... Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

2 1

autolinking
by James Mansion 18 Feb '09

18 Feb '09

I'd like to build a boost subset using my own build system. I'd like to turn off autolinking and control the names of the libraries, but it seems I can't. Is that intentional? I tried to use BOOST_AUTO_LINK_NOMANGLE as a starting point but setting that only helped for the first inclusion of auto_link.hpp, since it undefines it. Can I offer this trivial patch, or at least suggest something similar? Index: include/boost/config/auto_link.hpp =================================================================== --- include/boost/config/auto_link.hpp (.../ref/boost) (revision 758) +++ include/boost/config/auto_link.hpp (.../src/boost) (revision 758) @@ -304,6 +304,9 @@ && defined(BOOST_LIB_RT_OPT) \ && defined(BOOST_LIB_VERSION) +// JGM: provide global disable for autolink of Boost libraries. +#if !defined(BOOST_NO_AUTOLINK) + #ifndef BOOST_AUTO_LINK_NOMANGLE # pragma comment(lib, BOOST_LIB_PREFIX BOOST_STRINGIZE(BOOST_LIB_NAME) "-" BOOST_LIB_TOOLSET BOOST_LIB_THREAD_OPT BOOST_LIB_RT_OPT "-" BOOST_LIB_VERSION ".lib") # ifdef BOOST_LIB_DIAGNOSTIC @@ -316,6 +319,8 @@ # endif #endif +#endif // !BOOST_NO_AUTOLINK + #else # error "some required macros where not defined (internal logic error)." #endif @@ -355,14 +360,3 @@ #if defined(BOOST_AUTO_LINK_NOMANGLE) # undef BOOST_AUTO_LINK_NOMANGLE #endif - - - - - - - - - - -

2 1