- Boost - lists.preview.boost.org

Re: [boost] howto: boost.lambda + stl on VS 2010 (SP1) ?
by Mathias Gaunard 09 May '11

09 May '11

On 05/05/2011 01:37, Raffi Enficiaud wrote: > Hi all, > > Sorry for bothering with this. I recently encountered some problems in using > boost.lambda with Visual 2010 Express, and need some clues for solving the > issue (there are many ways around of course). > I simply want to accumulate the values of a std::map, and I thought using > lambda to access the second member of the map iterator was appropriate. Here > is the piece of code: > > typedef std::map<T1, unsigned short> m_t; > m_t m ; // fill m > double acc(0); > std::for_each(m.begin(), m.end(), var(acc) +=& _1->*& > m_t::value_type::second); > > The last line does not compile on Visual (it does on GCC), I have to add a > typedef: > > typedef typename m_t::value_type aa; > std::for_each(m.begin(), m.end(), var(acc) +=& _1->*& aa::second); > > Which one is "more correct" ? It's one of the annoying MSVC bugs. MSVC doesn't like it when you chain nested names in template contexts.

1 0

[release] Adding more documentation to the release process
by Daniel James 08 May '11

08 May '11

Hi Beman, At the moment the release doesn't include the geometry documentation which is at libs/geometry/doc/html. I've being creating a new file, boost-release-docs.7z which includes both the main documentation and the geometry documentation (it's a new file because it's zipped from the root, rather than from the doc directory). The attached patch should change the script to use that, and fix copying the documentation - this will also allow us to easily add other documentation at a later date. It's copying to the boost root directory. If you'd rather keep things contained it could use repeated calls to xcopy for the relevant directories, although that would require changing the scripts every time some new documentation is added. Does it look okay to you? Daniel

2 1

[multi_index] feature proposal: member keys and typeless specification of keys
by JOAQUIN M. LOPEZ MUÑOZ 08 May '11

08 May '11

Hi all, This is a proposal for inclusion of two new features into Boost.MultiIndex, mem_key and BOOST_MULTI_INDEX_AUTO_KEY. Consider the following: struct foo { int x; int bar(); int baz()const; }; typedef multi_index_container< foo, indexed_by< ordered_unique<member<foo,int,&foo::x> >, ordered_unique<mem_fun<foo,int,&foo::bar> >, ordered_unique<const_mem_fun<foo,int,&foo::baz> > > > multi_t; Note that we have to use member, mem_fun or const_mem_fun depending on the kind of key used. mem_key allows for a uniform specification syntax: typedef multi_index_container< foo, indexed_by< ordered_unique<mem_key<int foo::*,&foo::x> >, ordered_unique<mem_key<int (foo::*)(),&foo::bar> >, ordered_unique<mem_key<int (foo::*)()const,&foo::baz> > > > multi_t; This in itself gains us relatively little; but if we have a C++11 compiler with decltype, BOOST_MULTI_INDEX_AUTO_KEY can use mem_key in a way that dispenses with the need for specifying the type of the key! typedef multi_index_container< foo, indexed_by< ordered_unique<BOOST_MULTI_INDEX_AUTO_KEY(&foo::x)>, ordered_unique<BOOST_MULTI_INDEX_AUTO_KEY(&foo::bar)>, ordered_unique<BOOST_MULTI_INDEX_AUTO_KEY(&foo::baz)> > > multi_t; Some requests and questions: 1. If you're interested in these features, please download the attached mem_key.hpp file, play with it and report on successful/problematic usage. 2. Do you think this is worth including in Boost.MultiIndex? 3. Proposals on the naming scheme? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx

3 6

[provocative] Whom did the SFC pay to list boost developers as a whole in "Current Member Projects"?
by Alexander Terekhov 08 May '11

08 May '11

http://sfconservancy.org/members/current/ (Current Member Projects) "Boost provides free peer-reviewed portable C++ source libraries. Boost emphasizes libraries that work well with the C++ Standard Library. Boost libraries are intended to be widely useful, and usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. Boost aims to establish existing practice and provide reference implementations so that Boost libraries are suitable for eventual standardization. Ten Boost libraries are already included in the C++ Standards Committee's Library Technical Report ( TR1) as a step toward becoming part of a future C++ Standard. More Boost libraries are proposed for the upcoming TR2." The context: (pacer) 03/23/2011 192 ENDORSED LETTER addressed to Judge Shira A. Scheindlin from David Leichtman dated 3/23/2011 re: Requesting that the Reply and Kuhn Declaration be stricken, or in the alternative, that the Court consider Best Buy's responses to these new theories and arguments. ENDORSEMENT: Defendant's request is granted. The Court will consider Best Buy's response to the new issues raised in Plaintiffs' Reply, as set forth in this letter. So Ordered. (Signed by Judge Shira A. Scheindlin on 3/23/2011) (jpo) (Entered: 03/23/2011) 04/14/2011 193 OPINION AND ORDER. For the reasons in this opinion and order, plaintiffs' motion to join WD is denied. The Clerk of the Court is directed to close this motion (Docket No. 133). (Signed by Judge Shira A. Scheindlin on 4/14/2011) (rjm) (Entered: 04/15/2011) 04/26/2011 194 ENDORSED LETTER addressed to Judge Shira A. Scheindlin from Emmett J. McMahon, dated 4/25/2011, re: Counsel for the defendant Best Buy Co., writes to request a pre-motion conference regarding a motion to strike Plaintiffs' claim for "actual damages and any additional profits of [Best Buy] incurred as the result of infringement." ENDORSEMENT: Request granted. A premotion conference will be held on May 6 at 2:30. So Ordered. (Pre-Motion Conference set for 5/6/2011 at 02:30 PM before Judge Shira A. Scheindlin) (Signed by Judge Shira A. Scheindlin on 4/25/2011) (lnl) (Entered: 04/26/2011) (details) http://www.terekhov.de/192.pdf http://www.terekhov.de/194.pdf Suggestion: Please remove boost from http://sfconservancy.org/members TIA. regards, alexander.

9 22

[GSoC] Getting started
by Andrew Sutton 07 May '11

07 May '11

Hello GSoC students and mentors, Students, if you haven't contacted your mentor, now would be the time do so. Mentors, if you haven't heard from your students, you need to try to get in touch with them. If anybody is having trouble getting a hold of their student or mentor, please let me know. During the "Getting to Know You Phase", you should be doing two things: 1. Defining goals and expectations for the summer and 2. Starting to get up to speed with Boost's development environment Remember, that there is a midterm review. It is usually a good idea to set concrete midterm goals in order to ensure that your project is moving forward. Also, the source code of your project MUST be available for review by both your mentor and the community at large. Basically, this means you need to have it publicly hosted. The obvious solution is to house the project in the Boost Sandbox (http://svn.boost.org/svn/boost/sandbox/SOC/2011/) You will probably need to request write access from the Boost owners (boost-owner(a)lists.boost.org) Send them an email. If your project is already hosted online (independently or as part of another project), then we need to know where it is. Please send an email to the list describing how we can check out the source code of your work. I will add the addresses of these projects to the Boost-GSoC wiki page so other interested parties can find them. That's it for now. Good luck! Andrew

3 2

[Review] Boost.Convert, review manager analysis
by Edward Diener 07 May '11

07 May '11

As previously stated Vladimir Batov decided to withdraw his library at the end of the review period from consideration for inclusion into Boost and I had announced this and the fact that because of this the library would not be accepted. Nonetheless I want to give my analysis of the reviews and the issues both pro and con of the reviewers. I also want to give some of my own thinking on these issues. There were few reviews of the library but much late discussion in the final day of the review period and just afterward. There were 2 reviews which voted to accept Convert ( Artyom Bellis, Alfredo Correa ), 3 reviews which voted not to accept Convert ( Jeroen Habraken, Thomas Heller, Hartmut Kaiser ), 1 review which would have accepted Convert but qualified that only if lexical_cast could not be extended instead ( Rob Stewart ), 1 review which would have accepted Convert with large scale changes ( Gordon Woodhull ), and one mention, not a formal review, of acceptance until something else came along but with perhaps a later change of mind ( Paul Bristow ). There was also one review sent to me personally by Barend Gehrels, after Vladimir Batov withdrew his library, which voted not to accept Convert. There were also a number of people who raised doubts and objections to Convert in various ways without giving a formal review. It is all these issues raised by reviewers and commenters I want to discuss next. Vladimir Batov was responsive to nearly all of those issues but I want to enumerate them and give my own thoughts about them as I read reviews and comments. A number of people wanted lexical_cast to be extended instead of a new library. This certainly is a valid viewpoint. But I believe that the lexical_cast library is set as it is until someone takes it over from its original author and is willing to change it. I think it is better to review the library under discussion rather than to hope that something else can be changed in the future. There was an issue of the basic syntax which many people did not like. Instead of the syntax of 'convert<dest>::from(source)' there were a number of people who wanted to see 'convert<dest>(source)' instead, largely becaused it matched the 'lexical_cast<dest>(source)' syntax. Vladimir Batov explained why he used the syntax he did. I think in this case it is reasonable. Again this is an issue in relation to lexical_cast, and I saw no real significant difference between the syntaxes on a basis of practical use. The main issue brought out by many people is whether a single function can encompass successfully all of the functionality which Convert wished to encompass and whether this functionality both worked smoothly with everything others wished to do with the functionality. Here there were many valid objections and I will attempt to enumerate them: 1) The return value of the convert function is really many different returns, and this is done through implicit conversions of the actual return type. This was mentioned most eloquently by Thomas Heller. It is quite natural to assume that the return value of a successful call to 'convert<dest>::from(source)' would be a 'dest' object but instead it is a value which has an implicit conversion to 'dest'. This works when passing the value to ordinary functions but does not when passing the value to template functions. As Vladimir Batov mentioned one can use the 'value()' member function of the return value, and presumably also one can use a 'static_cast<dest>' also, to force the exact 'dest' object to be passed, but I also viewed this as a negative way to work, and a very valid objection to the way Convert was designed. To me it was not just a matter of confusion to the end-user but of a naturalness of use. A convert-type interface should have some function where, if the convert is successful, the actual result of the conversion is returned, and not some intermediate value with an implicit conversion. 2) The Convert library uses a stream-based method to do conversions but wanted to leave the door open for other methods. Part of the extended syntax of the library works with stream manipulators and locales. A very valid point was brought up, again by Thomas Heller, that it is not clear how the extended syntax is supposed to work with and affect non-stream based specializations of the basic convert template. Even the method of extending the library in this way, rather than just providing stream-based operators for a given type, is open to much doubt as valid C++ and largely left unexplained in the documentation. 3) The syntax for the stream-based and locale additions to the library's functionality was found odd by many people. The term 'wacky' was often used and Vladimir Batov did defend his choice about it well. Nonetheless it is a valid issue to consider whether the extended syntax is easy for a person to use. I found the syntax for using iostream manipulators quite natural, and the syntax for locales and other functionality such as throwing behavior less natural. Again I do not want to get too caught up in syntactical issues but I did understand the issues brought up by others regarding this. 4) The method of using the convert function in algorithms was criticized. Some people expressed their wish that a placeholder syntax, as used by other Boost libraries, be used. I actually found the way Convert does this as pretty elegant, there were two syntaxes which worked, but could understand others liking for the placeholder syntax. 5) The use of a default value, the issue of a default constructor, and the differing results when a conversion fails or not, received much discussion, especially at the official end of the review period and afterward, and I appreciate reading all of the discussions. I do not want to specifically go into each one, other than to say that I think this has basically to do with the issue of having a single function do everything which could not easily cover all the different scenarios mentioned for actual use. There were other valid concerns which are related to just a need for more complete documentation. Vladimir Batov responded to most of them. Here I will enumerate them: 1) Rob Stewart in his review mentioned many documentation corrections related to grammar, spelling etc. 2) What locale is being used by default is not explained. 3) The reference is very incomplete. 4) The section for extending the library is unclear and incomplete. Finally there were valid concerns relating to getting Convert to work properly. Some of these related Convert and lexical_cast and noted the differences. A few others mentioned things which just did not work properly in the actual conversion and again Vladimir Batov said he would look at these issues. Barend Gehrels sent me a late review, which he did not want to post to the mailing list because Vladimir Batov had already withdrawn is library, in which he said that he had some technical problems adapting a Boost.Geometry type to work with Convert. I think these are all technical issues which can be resolved. Many other people had specific incisive remarks during the review period but I can not list them all. That does not mean those remarks were ignored by me in any way, as I read and attempted to digest what everyone had to say. Final remarks: I would like to bring some clarity to the issues which may have forced Vladimir Batov to essentially withdraw his library at the end of the review period from consideration and which led to much comment and criticism about the library. This is my purely personal take on the library, but it is based on my technical understanding of the issues involved. The main issue with the library is that the 'single function fits all scenarios' works much less well in practical use than the author supposed, even as I understood the reason for simplicity which caused him to pursue this path. There really needs to be a function that simple returns the converted value upon success. Overloaded versions of that function, or differently named functions, can return other specific things. Where there is a great attraction to a return value which can be implicitly converted to other values, I think this attraction given practical use is somewhat illusory. While I did not enjoy some of the harsher remarks made by Thomas Heller in his review of the library about the design of Convert ( and I do not think he really meant them as harshly as they may have sounded ) he did rightly point out that the 'overloaded' return value is an impediment to a cleaner design which would allow one to use the right convert function given the possibilities which the library wants to accomplish. I know there has been many subsequent discussions about a set of functions that can replace the single function in Convert depending on how Convert can be used, and I do not myself want to get in the middle of this debate, but once there is an understanding of what needs to be done, I really think the library can be designed to appeal to end-users in a better way. The second issue in my mind is that the library attempts to do too much given the way it was designed. If the focus is simply a library which does stream-based conversion between strings and objects ( both ways ) I personally think it would be much better. Once you look for non-stream based conversions you have to consider more carefully how the stream-based syntax and locales should be integrated with the library. Once you look for type to type conversions rather than string to type and type to string conversions you have to design a good general facility for specifying how this is done within the functions you provide. This is a much bigger job of thinking about design, unless you are simply providing a very generalized shell with little real functionality built-in. I am not saying the author of the library has not thought about these issues, but my impression is that they have not been addressed carefully. Just in case anyone wanted to know, and also so that Vladimir Batov does not feel so bad about withdrawing the library from consideration at the end of the review period, I would have rejected the library for inclusion into Boost given the reviews and comments of others and my own perceptions of the issues involved. But I think the author has still done a fine job and is close to having a library which could be included as a part of Boost. Although it is hard work, it has been a pleasure to be a review manager of this library and I thank everyone involved and especially the author of the Convert library himself. Edward Diener

2 1

[Block Pointer] Docs
by Phil Bouchard 06 May '11

06 May '11

Hi, Sorry for the repetitive emails and thanks to Gregory Crosswhite regarding it but I have improved the user-friendliness of the utility: https://svn.boost.org/svn/boost/sandbox/block_ptr/libs/smart_ptr/doc/overvi… Please let me know if there's anything unclear. Thanks, -Phil

2 6

[PBGL] Distributed adyacency_list memory allocation
by Cosimo Calabrese 06 May '11

06 May '11

Hi to all, I'm working on WinXP, VS2010, boost 1.46.1. I've writed this short program: //---------------------------------- #include <boost/graph/use_mpi.hpp> #include <boost/graph/distributed/mpi_process_group.hpp> #include <boost/graph/distributed/adjacency_list.hpp> using boost::graph::distributed::mpi_process_group; typedef boost::property<boost::vertex_distance_t, long, boost::property<boost::vertex_name_t, std::string > > vertex_prop; typedef boost::property<boost::edge_weight_t, long > edge_prop; typedef boost::adjacency_list< boost::vecS, boost::distributedS<mpi_process_group, boost::vecS>, boost::directedS, vertex_prop, edge_prop > Graph; typedef boost::graph_traits<Graph>::edge_descriptor EdgeDescriptor; typedef boost::graph_traits<Graph>::vertex_descriptor VertexDescriptor; int main(int argc, char* argv[]) { boost::mpi::environment env(argc,argv); Graph g( 10 ); return 0; } //---------------------------------- When I launch it, every process allocates about 1 GB of memory. Why it allocates all that memory? Is it normal? Is there any tuning to the PBGL framework that I must made? I use it on a 2-core machine, and the command that I use is: mpiexec -n 2 .\test.exe I've tried with openMPI 1.4.3 and Microsoft HPC Pack 2008, but it seems irrilevant. Thanks in advance, Cosimo Calabrese.

2 1

Extending multi_index_container hash tables
by Vladimir Voznesensky 06 May '11

06 May '11

Hello there. Current implementation of hashed index has, at least, two issues, preventing me from re-using it in some places. First, the time for unlink operation in multi_index/detail/hash_index_node.hpp is O(m) where m is a occupancy of the given bucket. I'ts usually ok for unique index, but seems to hit performance of removing item in a non-unique index. It's all because of using single-linked list instead of double-linked one. Second, there is no possibility to use internal order of the records in the bucket, i.e. operations like popping the last element in the bucket's list. Such feature could be useful for, for example, priority queues. It could be realized by using such double-linked (or extra pointers in a bucket structure). Sure, I could get the current realization and write my own index, but it seems wiser to extend the current implementation to support custom bucket container or custom node as a template parameter. Thanks in advance. VV

2 1

Re: [boost] [review] string convert
by Vicente BOTET 06 May '11

06 May '11

Hi, are we discussing here a generic interface from type-to-type or one that uses an intermediary stream to make the conversion? If it is the first I could accept names as convert_cast or convert_to. If it is the second, I don't think it is appropriated to use this generic form and something in the name must recall this feature. lexical_cast is used for exactly this purpose and the name is appropriated. How could we rename the Boost.Convert library? Boost.StreamConvert? and the operations? Best, vicente

4 9

[autoindex] Rationale Question
by Artyom 06 May '11

06 May '11

Hello, It is not a review but rather questions about this tool rationale. Form the very brief look into AutoIndex documentation I see. > ... AutoIndex will automatically scan one or > more C/C++ header files and extract all the > function, class, macro and typedef names that > are defined by those headers, and then insert > the <indexterm>s into the Docbook XML document for you. > However, there is a tool Doxygen that already does this. Doxygen is fully capable system for indexing source files and providing references for them. For example: http://cppcms.sourceforge.net/boost_locale/html/namespacemembers.html http://cppcms.sourceforge.net/boost_locale/html/namespacemembers_func.html So there is a well debugged, tested, supported indexing tool (Doxygen) that as far as I know works fine and is already used by Boost. So the question are 1. How does it differs from Doxygen indexing? I'm not talking about the integration with various pars of Boost documentation toolchain but rather what it does differently. 2. Why have you decided to develop entirely new tool instead of using existing one. I probably miss some points but I rather see a great tool Doxygen that already does many things and does them well but still Boost creates its own tools (and this does not happen first time) Thanks, Artyom

3 2

[xint] Formal Review Result
by Vladimir Prus 06 May '11

06 May '11

I apologize for the delay in producing the final summary and result of the Boost.Xint review, but here it is. Votes ===== YES: - Christian Henning - Steven Watanabe - Jarrad Waterloo - Edward Diener - Paul A. Bristow NO : - Mathias Gaunard - Joel Falcou - Anders Dalvander - Joachim Faulhaber - Phil Endecott - Domagoj Saric - Gordon Woodhull ("fraction of a vote") I might have missed somebody inside the 454 messages I have as result of the review, but the overall picture is clear -- the votes are split. High-level issues ================= - The claim that the library is "fast" is not necessary true. Phil has did some checking against hand-written assembler that don't look too good. - It is not clear whether the design allows for improving performance of fixed-size integers using specialization (again, see Phil's comments) - There were concerns about COW. In particular, it was very clearly stated that if COW is used, it should work fine in multi-threaded programs. - It was suggested to use ET. - Some folks suggested better separation between algorithms and data representation. Specific issues =============== - It was pointed out that "a + b + c" creates a pile of temporaries, and this can be improved without using ET. - Joachim's review raised a lot of valid points. Section 3 of his reviews in something that should be addressed, more or less entirely. Note that while we normally don't force specific coding style, some of formatting pointed out is simply unacceptable if this code is to be read by anybody. - 'Secure' flag is probably not so much of it. Future directions ================= I think that reviews by Phil and Joachim are most important in specying evolutionary directions for Boost.XInt. Chad made several comments about what he plans to do, in particular: - http://article.gmane.org/gmane.comp.lib.boost.devel/216935 Conclusion ========== I think there's no doubt that (i) this domain is important and (ii) Chad has put a lot of work into this library, producing several iterations. It was pointed out that we have many arbitrary-precision libraries skeletons all around Boost, and providing such a solid offering for review is a significant accomplishment. And it everybody learned a lot during the review. There was a couple of important meta-points raised during review -- whether review should focus on external interface only, and what is the scope of the library. Some reviewers argued that only external interface matters. However, it seems to me (as review manager), that concerns about internal design are valid, and may not be rejected offhand. After all, external interface of an integer library is more or less defined by mathematics, and internal design plays a key role in successfull evolution of the library. There was also heated discussion about the scope of the library, in particular support for fixed-width integers. I think that it's abstractly OK for this library to treat fixed-width integers as second-class citizens. However, I am having hard time determining the intended scope of the library. If I'm doing cryptography, would I really want to implement cryptography algorithms from the books with Boost.XInt, only to introduce bugs that are probably fixed in existing implementations (often, included in the OS). And if I'm really intent on doing that, I probably want raw performance, including a way to plug in optimized backends using SSE 2011, CUDA, and whatever fancy technology is there. If I'm doing general programming, then I'm most likely interested in not too big integers. They might be fixed-width 128-bit integers, or they might be something larger-than-64, but not necessary fixed. However, such integers are not the scope of the library, and they were found to have suboptimal performance. It is certainly possible to refine/define the scope, optimize everything for that scope, accomodate the proposals made during review, and obtain an excellent Boost library. However, there are some many suggestions, and so many planned redesigns and changes, that we need a second look at the library. Further, because of the global nature of the changes, it would be very hard to identify a specific subset that must be improved and then go through mini-review. For that reason, I've arrived at the the following result: Boost.Xint library is not accepted at this time. We'll be happy to have another full review of the library when the next version is ready. Thanks to Chad for the submission and for everybody who participated in the review! - Volodya -- Vladimir Prus Mentor Graphics +7 (812) 677-68-40

10 17

FW: Registration Available
by Hartmut Kaiser 06 May '11

06 May '11

FYI... Regards Hartmut --------------- http://boost-spirit.com > -----Original Message----- > From: boostcon-plan(a)googlegroups.com [mailto:boostcon- > plan(a)googlegroups.com] On Behalf Of Marshall Clow > Sent: Friday, May 06, 2011 11:25 AM > To: boostcon-plan(a)googlegroups.com > Subject: Registration Available > > Oliver Mueller <oliver.mueller(a)gmail.com> has discovered that he will not > be able to attend BoostCon. > Unfortunately for him, it is well past the refund deadline (which was > 4./14), so he's looking for someone to use his registration. > > If you know someone who could take advantage of a deal on admission, they > should get in touch with Oliver and work something out. > > -- Marshall > > Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> > > A.D. 1517: Martin Luther nails his 95 Theses to the church door and is > promptly moderated down to (-1, Flamebait). > -- Yu Suzuki

1 0

Re: [boost] [Boost-users] [Boost.Spirit] RFC: bin_float parser
by Vitaly Budovski 06 May '11

06 May '11

On 6 May 2011 10:33, Joel de Guzman <joel(a)boost-consulting.com> wrote: > On 5/5/2011 9:08 PM, Vitaly Budovski wrote: >> Greetings, >> >> On 28 April 2011 12:09, Hartmut Kaiser <hartmut.kaiser(a)gmail.com> wrote: >>> Thanks for this! >> >> Apologies for the long delay in replying. >> >>> >>> A couple of comments: >>> >>> 1) Is there a reason why you created separate components instead of simply extending the existing set of binary parsers/generators? >> >> It seemed like it would be a lot more work. I'm guessing I would need >> to add a new template parameter or maybe use the preprocessor, since >> the classes have a few integer<> types inside. Can you suggest a >> better way? >> >>> >>> 2) What's the rationale for not using/extending the endian classes in Spirit, but providing your own set of independent endian types? >> >> See response above :) Another thing I wasn't too happy with was the >> fact that they are in the integer namespace. Perhaps they should be >> moved out of there, since endianness doesn't apply only to integers. >> >>> >>> 3) If this is to be included into Spirit we'd need the corresponding docs as well. >> >> A few more test cases couldn't hurt either. I discovered I missed an >> asterisk in the generate_to line of bin_float_generator. >> Is there a guide for adding docs to boost? > > Boost Spirit uses quickbook. Please check out the Spirit docs. > Here's a link to quickbook: > http://www.boost.org/doc/libs/1_46_1/doc/html/quickbook.html > > Vitaly, the proper forum for this is the Spirit general or devel mailing list: > See Boost.Spirit lists here: http://www.boost.org/community/groups.html > Can we please move the discussions there? > > Regards, > -- > Joel de Guzman > http://www.boostpro.com > http://boost-spirit.com > Thanks Joel. Moving conversation to more appropriate location. Cheers, Vitaly

1 0

next version dates
by Andy Tompkins 05 May '11

05 May '11

Hi, Has it been decided the dates relevant to the next version? I have only looked here (http://www.boost.org/development/index.html) and didn't see anything. I'm not trying to change / hurry or delay anything. I just want to start moving some changes from trunk to release, but I work slowly and want to start closer to the beginning of a release, not closer to the end of one. Regards, Andy Tompkins.

6 12

[foreach] Warning with gcc-4.6.0 and -Wconversion
by Philipp Reh 05 May '11

05 May '11

gcc-4.6.0 made Boost.foreach unusable in 1.46.1 because the rvalue detection no longer works. Now, there is a fix in trunk for it but it has a nasty side effect, namely a warning that is emitted whenever foreach is used with an rvalue and -Wconversion is turned on. Sadly, this warning cannot be ignored by including Boost with -isystem because the code is generated by a macro, obviously. Here is a simple program to reprdouce this: #include <boost/foreach.hpp> #include <iostream> #include <ostream> #include <vector> typedef std::vector< int > int_vector; int_vector const test() { int_vector ret(2, 2); return ret; } int main() { BOOST_FOREACH( int_vector::const_reference ref, test() ) std::cout << ref << '\n'; } This prints the following warning: test.cpp:21:2: warning: choosing ‘boost::foreach_detail_::rvalue_probe<T>::operator boost::foreach_detail_::rvalue_probe<T>::value_type() [with T = const std::vector<int>, boost::foreach_detail_::rvalue_probe<T>::value_type = const std::vector<int>]’ over ‘boost::foreach_detail_::rvalue_probe<T>::operator T&() const [with T = const std::vector<int>]’ [-Wconversion] test.cpp:21:2: warning: for conversion from ‘boost::foreach_detail_::rvalue_probe<const std::vector<int> >’ to ‘const int_vector’ [-Wconversion] test.cpp:21:2: note: because conversion sequence for the argument is better I would be glad if this could be fixed somehow because -Wconversion is a crucial warning option to me.

3 3

Boost.Locale and the standard "message" facet
by Vicente BOTET 05 May '11

05 May '11

Hi, I was wondering how Boost.Locale is related to the standard message facet which is used to translate messages. Note that the facet interface work with integer identifiers avoiding all the issues raised by the get_text/translate functions provided by Boost.Locale. Is there any reason Boost.Locale could not follow the standard design? What are the advantages of the Boost.Locale design? Best, Vicente

4 6

[config] Macro BOOST_NO_NOEXCEPT is required
by Takaya Saito (SubaruG) 05 May '11

05 May '11

http://thread.gmane.org/gmane.comp.lib.boost.devel/214978 I think the macro BOOST_NO_NOEXCEPT ( or BOOST_NO_0X_NOEXCEPT ) is required soon. How's the status now?

5 7

result_of overloaded member function?
by Arno Schödl 05 May '11

05 May '11

Hello, is there a way to get the result type of an overloaded member function? Something like: template< class T, class A > typename boost::result_of< T::func(A) >::type invoke( T& t, A& a ) { return t.func(a); } Thanks for help, Arno -- Dr. Arno Schödl | aschoedl(a)think-cell.com Technical Director think-cell Software GmbH | Chausseestr. 8/E | 10115 Berlin | Germany http://www.think-cell.com | phone +49 30 666473-10 | US phone +1 800 891 8091 Amtsgericht Berlin-Charlottenburg, HRB 85229 | European Union VAT Id DE813474306 Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl

3 3

[Convert] Not a review
by Phil Endecott 05 May '11

05 May '11

Dear All, I've not looked at this library in anything like enough detail to write a proper review, though I have followed a fair amount of the discussion both during the review and during previous discussions of a "better lexical_cast". My view comes down to this: there are zillions of different ways of doing this (both syntax and semantics) and no solution can keep everyone happy (as evidenced particularly by the previous discussions). But that doesn't matter, because every single C++ programmer is capable of writing their own conversion functions that work exactly how they want them to work, if they have the right building blocks. The building blocks are things like C's strto*(), etc. Personally, I prefer thin wrappers like these ones: template <typename ITER> long int strtol(ITER begin, ITER end) { ... } template <int N> long int strtol(const char (&s) [N]) { return strtol(&s[0],&s[N]); } inline long int strtol(std::string s) { return strtol(s.begin(),s.end()); } For variations on error policy I add words like "try", "must" or "maybe" to the function name; similarly for hex and other variations. But I don't suggest that these are going to suit other people. Why should we try to find a "one size fits all" solution to this problem? In my humble opinion, Boost does not need this functionality. Perhaps some of the lower-level "building blocks" would be useful, though - if things like strto*() are deficient. Regards, Phil.

3 4

Re: [boost] howto: boost.lambda + stl on VS 2010 (SP1) ?
by Peter Dimov 05 May '11

05 May '11

Raffi Enficiaud wrote: > To this point, I thought that using accumulate would be cleaner: > std::accumulate(m.begin(), m.end(), double(0), & _1->*&aa::second); std::accumulate takes a binary function. It doesn't do s += f(*i) as you seem to think, it does s = f(s, *i). So you should probably pass _1 + &_2->*&aa::second to it.

1 0

howto: boost.lambda + stl on VS 2010 (SP1) ?
by Raffi Enficiaud 04 May '11

04 May '11

Hi all, Sorry for bothering with this. I recently encountered some problems in using boost.lambda with Visual 2010 Express, and need some clues for solving the issue (there are many ways around of course). I simply want to accumulate the values of a std::map, and I thought using lambda to access the second member of the map iterator was appropriate. Here is the piece of code: typedef std::map<T1, unsigned short> m_t; m_t m ; // fill m double acc(0); std::for_each(m.begin(), m.end(), var(acc) += & _1->*& m_t::value_type::second); The last line does not compile on Visual (it does on GCC), I have to add a typedef: typedef typename m_t::value_type aa; std::for_each(m.begin(), m.end(), var(acc) += & _1->*& aa::second); Which one is "more correct" ? To this point, I thought that using accumulate would be cleaner: std::accumulate(m.begin(), m.end(), double(0), & _1->*&aa::second); But I have several compilation errors, and on the top of it: 1>(..)/boost-1_46_1\boost/lambda/detail/member_ptr.hpp(512): error C2296: '->*' : illegal, left operand has type 'const rt0 ' 1> boost/lambda/detail/member_ptr.hpp(622) : see reference to function template instantiation 'RET boost::lambda::detail::member_pointer_action_helper<true,false>::apply<RET,A ,B>(A &,B &)' being compiled 1> with 1> [ 1> RET=unsigned short &, 1> A=rt0, 1> B=rt1 1> ] I do not really understand what rt0/rt1 are. The former should be the iterator::value_type and the latter the pointer to member. Most of all, the call with accumulate looks very similar to the for_each one to me. So, is the problem between the keyboard and the chair ? Best, Raffi

1 0

[Block Pointer] make_block
by Phil Bouchard 04 May '11

04 May '11

Hi, I just disabled the constructor and the assignment operator having a raw pointers as a parameter and I added the make_block factory function. We can see it in action in the following example: https://svn.boost.org/svn/boost/sandbox/block_ptr/libs/smart_ptr/example/bl… Is it time for a review? -Phil

7 23

[Spirit Karma] Mutable references formed by pass_container in Karma "repeat" tests
by Doug Gregor 04 May '11

04 May '11

There are a few Karma failures using the latest Clang due to the pass_container detail class forming mutable references: http://www.boost.org/development/tests/release/developer/output/dgregor2-bo… I know that at least some compilers (e.g., GCC) don't diagnose mutable references, but this code is ill-formed account to the standard. Someone want to take a shot at eliminating or factoring out the mutability to avoid these mutable references? - Doug

2 1

[Review] Boost.Convert library, last day
by Edward Diener 04 May '11

04 May '11

This is a reminder that formal review of the Boost.Convert library by Vladimir Batov ends today, May 2. There have only been a few reviews of the library so the library welcomes reviews. If you are one of the people who have been dissatisfied by the perceived limitations of Boost lexical_cast, or have discussed such limitations on Boost mailing lists in the past, please look at the library and give a review of it, as its intent is to offer a greatly enhanced version of lexical_cast as a new library. *************** * Its Purpose * *************** The library builds on the past boost::lexical_cast experience, then takes those conversion-related ideas further to suit better today's applications and programing needs. It still offers simple, minimal interface, familiar conversion behavior and additionally provides: * throwing and non-throwing conversion-failure behavior; * support for the default/fallback value to be returned when conversion fails; * two types of the conversion-failure check - basic/simple and better/safe; * formatting support based on the standard std::streams and std::stream-based manipulators (like std::hex, std::scientific, etc.); * support for different locales; * support for boost::range-compliant char and wchar_t-based containers; * no DefaultConstructibility requirement for the Target/Destination type; * consistent framework to uniformly incorporate any type-to-type conversions, extensibility and additional room to grow. With its present support for string-to-type and type-to-string conversions it is an essential tool for applications making extensive use of configuration or MS-Windows-Registry-style files or having to process/prepare considerable amounts of data in, say, XML, etc. More so, it is easily extendable to accommodate, specialize and uniformly deploy new user-defined type-to-type conversions. ******************* * Where to get it * ******************* The Boost Vault is accesible again after being down for most of the week, so you can get the library from the Boost Vault at http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost-… You can also get the library, using Subversion, from https://svn.boost.org/svn/boost/sandbox/convert. The HTML documentation is part of the distribution and can be found at libs/convert/index.html in the distribution above. ******************** * Writing a review * ******************** The reviews and all comments should be submitted to the developers list, and the email should have "[convert] Review" at the beginning of the subject line to make sure it's not missed. Please explicitly state in your review whether the library should be accepted. The general review checklist: - 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. Edward Diener, Review Manager

10 17

Re: [boost] Boost.Locale and the standard "message" facet
by Vicente BOTET 04 May '11

04 May '11

Hi, > Message du 30/04/11 15:48 > De : "Artyom" > A : boost(a)lists.boost.org > Copie à : > Objet : Re: [boost] Boost.Locale and the standard "message" facet > > > Subject: [boost] Boost.Locale and the standard "message" facet > > > > Hi, > > > > I was wondering how Boost.Locale is related > > to the standard message facet which is used > > to translate messages. > > > The standard message catalogs allow to extract > messages by integer identifiers but may use string > identifiers and it is implementation defined > > It is undefined how to load message facets Well implementation defined doesn't mean undefined. > or format them and so on. The formatting can always be done on top of this facet, isn't it? > It does not support plural forms and context. I'm not an expert, but doesn't catalogs and the set parameter can be used for your domain an context? Respect to plural forms, how Boost.Locale manages with locales that have 3 or 4 forms of plurals (If I understood your private mail, Hebrew is an example of this)? I've the impression that Boost.Locale manage simple plurals but not all kind of plurals? BTW, what is the criteria in Boost.Locale to identify a plural form? How your library manage plurals for message that have several parameters? For example translate("%1 hours, %2 minutes, %3 seconds") % h % m % s > It is the most unless facet around. What do you mean? That the scope is reduced? > > Note that the facet > > interface work with integer identifiers > > avoiding all the issues raised by the > > get_text/translate functions > > provided by Boost.Locale. > > > > Use of integer identifiers is the best > way to screw the localization in the software. > > What does 3456 means? Do you really think > it is good to write translate(MY_MESSAGE_OPENING_FILE) Why not? Note that we can also write translate(MyMessage::OpeningFile) if this seems clearer to you > No, never - never - never - never - never > use such "constant" or "integer" identifiers. I understand that some as you can find that the use of integers scale worst than the use of strings as we need to maintain constants unique on a given context, but this can be checked on debug mode. Some time ago when I had to write a localization application, we used integer identifier to log internationalizable messages. This reduced drastically the size of the log. I guess only this advantage was enough to take integers instead of strings, for us of course. An advantage I see is that you need to concentrate all the message id of a set/context in a single file so no need to have tools that parse your code to get the strings to translate. BTW, how do you recover message translation from a domain with your underlying implementation, copy/paste or is there a possibility to have specific files for specific domains, or there is a single translation file by locale? I've not take a look at your implementation yet. Please could you tell me when the translation file is read? Is the file parsed only once and the translations stored on a cache? > Always use natural text. I think your natural language interface lets the user to have the impression that anything is possible, when a lot of limitations seem to be there as other have already commented in this ML. > > Is there any reason Boost.Locale > > could not follow the standard design? > > The standard message catalogs to weak I would like to here the rationale of the standard message design by someone that is aware of it (some pointers will be welcome also). > > What are the advantages of the Boost.Locale design? > > > > 1. Defined way to load and format catalogs You could provide a defined way on top of this facet, isn't it? > 2. Support of pural forms Plural forms can be designed on top of the message facet? > 3. Support of message-context As I said, I suspect that the set parameter is interpreted as your context. > 4. Using natural language identifiers as keys See below. This is not always an advantage, and as far as I see adds some constraints on the interface so the tool can take care to automatically extract the strings to translate. > 5. Convenense interface What do you mean? Could you compare both? > More? Well, I think that it would be great if you can add a complete comparison of the interfaces and a rationale why you think your design is superior on the documentation. Best, Vicente

2 7

[range] as_literal always returning iterator_range
by Tobias Germer 04 May '11

04 May '11

Hi all, I think there is a problem with the behavior of boost::as_literal. If I got it right, it is supposed to create an iterator_range from null-terminated strings, which is fine. However, it also creates iterator_ranges from exisiting ranges, i.e., it converts general ranges to iterator_ranges. I think as_literal should fall back to identity (i.e., just return its argument) if its argument is already a range. With the current behavior, the type information of the range is lost. This is a problem if I write generic code and want to dispatch several cases based on the type of the range. Consider the following example: ------------------------------- template<class Rng> void f( Rng const& r ) {...} template<class T> void f( iterator_range<T*> const& r ) {...} void f( std::string const& s ) {...} void f( std::vector const& v ) {...} template<class Rng> void g( Rng const& r ) { f(as_literal(r)); ... } ------------------------------- Function g() accepts general ranges as well as zero-terminated strings. It dispatches its argument using the type of the range and the overloads of f(), in order to execute special code for some ranges like strings and vectors. (In my particular case, I have special treatment for ranges of contiguous memory.) This is not possible anymore after calling as_literal, because it always returns an iterator_range. Wouldn't it be better to return the original range, for example like this: template< class Rng > typename enable_if< has_range_const_iterator<Rng>, Rng &>::type as_literal (Rng& r ) { return r; } Regards, Tobias -- Dr. Tobias Germer | tgermer(a)think-cell.com Software Engineer think-cell Software GmbH | Chausseestr. 8/E | 10115 Berlin | Germany http://www.think-cell.com | phone +49 30 666473-10 | US phone +1 800 891 8091 Amtsgericht Berlin-Charlottenburg, HRB 85229 | European Union VAT Id DE813474306 Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl

3 2

Boost announce mailing list messages
by Edward Diener 04 May '11

04 May '11

My messages to the Boost announce mailing list, despite being the review manager for the Boost.Convert library, are being ignored. Why is this ? I was able to post an initial announcement on the Boost announce mailing list when the review of the Boost.Convert library started, but my message to that mailing list, when the Boost vault was down and I wanted to alert uses to the subversion URL I had created for the Boost.Convert library, never got posted on the Boost announce mailing list. Now that I have sent another message to the Boost announce mailing list, signalling the result of the Boost.Convert library review, it is again being ignored.

2 1

boost in linux repository
by Krzysztof 04 May '11

04 May '11

When the newer version of boost library is expected to be in linux repository? Now, it has version 1.42. -- Regards Krzysztof J.

3 3

[atomic] Status?
by vicente.botet 04 May '11

04 May '11

Hi, There are some libraries that would prefer to be reviewed after Boost.Atomic is reviewed, otherwise them should move the library as an internal detail of the implementation. Could the people working on Boost.Atomic tell us what is the state of the library? Which platforms have been handled? Which part of the standard has been implemented? Could others having knowledge in assembler participate in this project? When we can expect the library to be ready for review? Best, Vicente

10 20

Re: [boost] [asio] Randomly having problems reading from the socket
by Torben Wiggerich 04 May '11

04 May '11

Hi Jinqiang, thanks for your answer. What I forgot to mention was that I'm using the localhost for the socket connection. So there shouldn't be any errors caused by the physical network, I guess. I changed the code to evaluate the 'ignored error'. But an error never occurs there . It just falls asleep for 5 seconds. Kind regards Torben > > > -------- Original-Nachricht -------- > Betreff: Re: [boost] [asio] Randomly having problems reading from the > socket > Datum: Tue, 3 May 2011 08:57:27 +1000 > Von: Jinqiang Zhang <jasonzha(a)gmail.com> <mailto:jasonzha@gmail.com> > Antwort an: boost(a)lists.boost.org <mailto:boost@lists.boost.org> > An: boost(a)lists.boost.org <mailto:boost@lists.boost.org> > > > > Hi Torben, > > Firstly I claim I always use async way of asio, so I don't get the same > problem as yours. But for your code, I might suggest, because you are > transferring big chunk of data, if network condition is bad, you might get > some error, so maybe you want to see the 'error' while not use 'ignored > error' ? > > cheers, > Jinqiang > > On Mon, May 2, 2011 at 10:28 PM, Torben Wiggerich<torben.wiggerich(a)nisys.de > > <mailto:torben.wiggerich@nisys.de> wrote: > > > Hi all, > > > > I have some problems using the boost.asio.read for a TCP-socket. So far it > > works fine, but it randomly stops the transfer for at least 5 seconds. > > To resolve the error I used a simple synchronous server and client from the > > boost examples and modified it too send a larger amount of data. (307400 > > Bytes; this size comes from the program I'm trying to get run). On the > > client side I also changed the reading from the socket to read the complete > > data with boost.asio.read and transfer_all as argument. > > > > Both, server and client, measure the time for sending and reading to the > > socket and will give an error if it needs more than 1 second. > > > > Here is the sourcecode for the server: > > > > #include<iostream> > > #include<string> > > #include<boost/asio.hpp> > > #include<boost/date_time/posix_time/posix_time.hpp> > > > > using boost::asio::ip::tcp; > > using namespace boost::posix_time; > > > > int main() > > { > > try > > { > > boost::asio::io_service io_service; > > > > tcp::acceptor acceptor(io_service, tcp::endpoint(tcp::v4(), 8002)); > > > > tcp::socket socket(io_service); > > acceptor.accept(socket); > > > > unsigned char * array = new unsigned char[307400]; > > > > for (;;) > > { > > boost::system::error_code ignored_error; > > > > ptime startTime = microsec_clock::universal_time(); > > > > boost::asio::write(socket, boost::asio::buffer( array, 307400 ), > > boost::asio::transfer_all(), ignored_error); > > > > time_duration neededTime = microsec_clock::universal_time() - > > startTime; > > > > if ( neededTime.total_milliseconds()> 1000 ) { > > std::cout<< "ERROR needed too much time: "<< > > neededTime.total_milliseconds()<< "ms"<< std::endl; > > } > > } > > } > > catch (std::exception& e) > > { > > std::cerr<< e.what()<< std::endl; > > } > > > > return 0; > > } > > > > > > My client sourcecode: > > > > #include<iostream> > > #include<boost/array.hpp> > > #include<boost/asio.hpp> > > #include<boost/date_time/posix_time/posix_time.hpp> > > > > using boost::asio::ip::tcp; > > using namespace boost::posix_time; > > > > int main(int argc, char* argv[]) > > { > > try > > { > > if (argc != 2) > > { > > std::cerr<< "Usage: client<host>"<< std::endl; > > return 1; > > } > > > > boost::asio::io_service io_service; > > boost::asio::ip::tcp::endpoint endpoint( > > boost::asio::ip::address::from_string( argv[1] ), 8002 ); > > > > tcp::socket socket(io_service); > > boost::system::error_code error = boost::asio::error::host_not_found; > > socket.connect( endpoint, error ); > > if (error) > > throw boost::system::system_error(error); > > > > int counter = 0; > > unsigned char* array = new unsigned char[307400]; > > for (;;) > > { > > boost::system::error_code error; > > > > ptime startTime = microsec_clock::universal_time(); > > size_t len = boost::asio::read( socket, > > boost::asio::buffer( array, 307400 ), > > boost::asio::transfer_all(), > > error ); > > time_duration neededTime = microsec_clock::universal_time() - > > startTime; > > > > if ( error ) { > > printf( "body read error %s\n", error.message().c_str() ); > > } > > > > if ( counter % 5000 == 0 ) { > > std::cout<< "passed: "<< counter<< "\r"; > > } > > ++counter; > > > > if ( neededTime.total_milliseconds()> 1000 ) { > > std::cout<< "ERROR needed too much time: "<< > > neededTime.total_milliseconds()<< "ms"<< std::endl; > > } > > } > > } > > catch (std::exception& e) > > { > > std::cerr<< e.what()<< std::endl; > > } > > > > return 0; > > } > > > > To reproduce the error just let it run for a while. It can take up to 30 > > minutes or even more... > > After a while it will produce the line: "ERROR needed too much time: > > 5007ms". Maybe with slightly different times, but all around 5 seconds. > > I tested it on different machines with Windows Vista and Seven. > > > > So am I'm doing sth. wrong? Is the reading from the socket correct? > > > > I'm using boost version 1.44. > > > > Kind regards > > Torben Wiggerich > > > > _______________________________________________ > > Unsubscribe& other changes: > > http://lists.boost.org/mailman/listinfo.cgi/boost > > > _______________________________________________ > Unsubscribe& other changes:http://lists.boost.org/mailman/listinfo.cgi/boost > > > ----- > eMail ist virenfrei. > Von AVG uberpruft -www.avg.de <http://www.avg.de> > Version: 10.0.1209 / Virendatenbank: 1500/3610 - Ausgabedatum: 02.05.2011 >

1 0

[config] Regression tests and warnings
by Edward Diener 04 May '11

04 May '11

It appears that the config regression tests treat all warnings as errors. Where is this specified in the jamfiles for config ? I need to run the config regression tests where -Wno-variadic-macros is defined for gcc, so that the warnings for using variadic macros are turned off and therefore no errors occur. What is the best way of modifying the config regression tests to do this ?

2 3

Porting boost::lexical_cast tests to boost::convert
by Jeroen Habraken 03 May '11

03 May '11

Hi, Since boost::convert is promoting itself as an alternative to boost::lexical_cast I decided to port the boost::lexical_cast test suite (which can be found in BOOST_ROOT/libs/conversion/lexical_cast_test.cpp) to boost::convert. I've simply replaced lexical_cast<T>(U) with convert<T>::from(U) and bad_lexical_cast with std::invalid_argument, whether this is a valid approach I'm not sure. To actually get the test suite to compile for boost::convert I had to comment out a lot of them and even then there are quite a few failures. This needs to be looked at (I've attached the code), what are actual boost::convert failures (both at compile- and runtime) and what is caused by my porting? Regards, Jeroen

2 1

[Review] Boost.Convert library has ended
by Edward Diener 03 May '11

03 May '11

The review period for the Boost.Convert library has officially ended. I will continue to read posts about the library while I make my review decision, so please do not stop discussing the library as appropriate because the review period has ended. I have received one personal request for a late review, and I am willing to accept any other requests for a late review to be made through Wednesday and posted to the mailing list, but I will not consider any other late review in my decision unless someone requests it of me personally. I know this is a fine line between an official review and just comments about what others have said before, but I need to make my decision based on some finite set of reviews and their subsequent discussion. I would like to thank everyone who has officially reviewed Boost.Convert as well as all who have made subsequent comments. The more input received, the easier it becomes for me as a reviewer to make a final decision. I would also like to thank the implementer of the Boost.Convert library, Vladimir Batov, for his willingness to address issues, answer criticism, and engage in discussion about his library. My review decision should be made and posted to the mailing list no later than by the end of Sunday, May 8.

4 3

[Review] Boost.Convert library, new subversion URL
by Edward Diener 03 May '11

03 May '11

This is a reminder that formal review of the Boost.Convert library by Vladimir Batov starts today, April 23, and is scheduled to last through May 2. *************** * Its Purpose * *************** The library builds on the past boost::lexical_cast experience, then takes those conversion-related ideas further to suit better today's applications and programing needs. It still offers simple, minimal interface, familiar conversion behavior and additionally provides: * throwing and non-throwing conversion-failure behavior; * support for the default/fallback value to be returned when conversion fails; * two types of the conversion-failure check - basic/simple and better/safe; * formatting support based on the standard std::streams and std::stream-based manipulators (like std::hex, std::scientific, etc.); * support for different locales; * support for boost::range-compliant char and wchar_t-based containers; * no DefaultConstructibility requirement for the Target/Destination type; * consistent framework to uniformly incorporate any type-to-type conversions, extensibility and additional room to grow. With its present support for string-to-type and type-to-string conversions it is an essential tool for applications making extensive use of configuration or MS-Windows-Registry-style files or having to process/prepare considerable amounts of data in, say, XML, etc. More so, it is easily extendable to accommodate, specialize and uniformly deploy new user-defined type-to-type conversions. ******************* * Where to get it * ******************* Normally you can find Boost.Convert here: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost-… However because the boostpro web site is having problems and will likely be down for the weekend, I have put the library into the Boost sandbox temporarily, since the Boost sandbox is up. So you can get the library, using Subversion, from https://svn.boost.org/svn/boost/sandbox/convert. This is exactly the same as the vault with the files unzipped. The HTML documentation is part of the distribution and can be found at libs/convert/index.html in the distribution above. ******************** * Writing a review * ******************** The reviews and all comments should be submitted to the developers list, and the email should have "[convert] Review" at the beginning of the subject line to make sure it's not missed. Please explicitly state in your review whether the library should be accepted. The general review checklist: - 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. Edward Diener, Review Manager

12 19

[Block Pointer] Review Request
by Phil Bouchard 03 May '11

03 May '11

Hi, I made the requested corrections to the Block Pointer, I've added automated tests and its corresponding Jamfile. The tests can be found here: https://svn.boost.org/svn/boost/sandbox/block_ptr/libs/smart_ptr/test/block… https://svn.boost.org/svn/boost/sandbox/block_ptr/libs/smart_ptr/test/block… Once again the documentation can be found here: https://svn.boost.org/svn/boost/sandbox/block_ptr/libs/smart_ptr/doc/tutori… Now I'm pretty sure I haven't forgotten anything and I am requesting a review. Thanks, -Phil

5 31

Re: [boost] [BOOST CORE C++ Feature] the super or base keyword for C++
by tymofey 03 May '11

03 May '11

>>I was wondering if it makes sense to add the well known super or base keyword to the C++ language in a generic way. C++ has multiple inheritance, while java and C# do not, so super would be ambigous.

8 14

Re: [boost] [BOOST CORE C++ Feature] the super or base keyword for C++
by tymofey 03 May '11

03 May '11

>>Mathias Gaunard 01 May 2011 21:25:53 >>You'd have to use SFINAE to tell whether B1::j exists and use B2::j otherwise. Seems like an unneeded complication to me. Why not just always use B2::j ?

2 1

Checking interest: reflectable types
by Noah Roberts 03 May '11

03 May '11

In my work I've developed a sort of reflection library for C++. There are still many problems to solve before it could near real reflection but I don't believe they are insoluble. It works much like fusion maps except that you can extend them through inheritance. In fact, my current implementation uses fusion to do its thing and with some minor changes to fusion::map it could provide the base. There is a boost.reflection proposal out there that is meant to work with boost.extension. This one is a bit different in that you're not additionally defining data; instead you declare your reflection as you declare your reflectable type through the instantiation of and inheritance from template metafunctions. It's primarily a static/compile-time kind of reflection but can be extended into runtime simply by making your field types a little smarter. Fields describe the data and provide access identifiers. Since they are general types that simply have to have an internal typedef you can attach whatever information is useful. We've done such things as attach valid value ranges, labels, etc... I currently use it do auto-construct property trees for user editing. I plan to use it for scripting/extension. I've had a look at boost.python and it looks like it would be possible, without too much difficulty, to automate python exposure of these types. A coworker with 0 experience in metaprogramming found it fairly easy to feed the types into a structure meant for a report design and printing library. This isn't a promise to actually do anything. I'm just gauging how much, if any interest there is to decide if I want to go to the trouble of hobby developing a publicly available and usable version.

4 11

Proposed date-time patch [ Refs #2475 ]
by Marshall Clow 03 May '11

03 May '11

Here's a proposed patch for ticket #2475. https://svn.boost.org/trac/boost/ticket/2475 Anyone love it? Hate it? Index: ../../../boost/date_time/tz_db_base.hpp =================================================================== --- ../../../boost/date_time/tz_db_base.hpp (revision 71667) +++ ../../../boost/date_time/tz_db_base.hpp (working copy) @@ -166,22 +166,26 @@ //! Constructs an empty database tz_db_base() {} + //! Process csv data stream, may throw exceptions + /*! May throw bad_field_count exceptions */ + void load_from_stream(std::ifstream &ifs) + { + std::string buff; + while( std::getline(ifs, buff)) + parse_string(buff); + } + //! Process csv data file, may throw exceptions /*! May throw data_not_accessible, or bad_field_count exceptions */ void load_from_file(const std::string& pathspec) { - string_type in_str; - std::string buff; - std::ifstream ifs(pathspec.c_str()); - if(!ifs){ + if(!ifs) boost::throw_exception(data_not_accessible(pathspec)); - } + + std::string buff; std::getline(ifs, buff); // first line is column headings - - while( std::getline(ifs, buff)) { - parse_string(buff); - } + load_from_stream(ifs); } //! returns true if record successfully added to map -- Marshall

2 2

[website] Suggestions
by Stephan T. Lavavej 02 May '11

02 May '11

It would be wonderful if: 1. On the main page, there was a direct link to the current version's documentation. Currently, you have to click Documentation, then "1.46.1 - Current Release". (Actually, I just noticed that a direct link does exist - Libraries under Welcome. I was hoping for a big blue button saying GET DOCS.) 2. There was a terse list of links to each library's documentation. The master list currently mentions 6 additional pieces of information for each library (Summary, Authors, First Release, Standard, Build, and Categories). That's nice, but it makes finding library X's documentation significantly more tedious than it has to be (I count 105 libraries in 1.46.1 - that's a lot of scrolling!). I suspect that even beginners don't need information other than the Summary 99% of the time. The current info should be preserved somewhere, but clicking on a release's documentation should bring up a terse list first. http://cid-e66e02dc83efb165.office.live.com/self.aspx/docs/boost.html is a horribly ugly preview of what I'm suggesting (because some libraries have long summaries, I've arbitrarily truncated them; ideally, each library would have a single-line summary at reasonable browser widths). 3. http://boost.org didn't redirect to http://www.boost.org . Even better, if the reverse happened ("Class B", according to http://no-www.org/faq.php ). Clearly, this is the most important issue of all. :-> Stephan T. Lavavej Visual C++ Libraries Developer

5 4

[locale] Review results for Boost.Locale library
by Chad Nelson 02 May '11

02 May '11

The formal review of Artyom Beilis' Boost.Locale library, originally scheduled to run from April 7th through the 16th and extended through the 22nd, is now finished. Fifteen people cast votes on it, ten for acceptance and five against. Though not overwhelming, the two-to-one majority clearly indicates the consensus of the list. As such: The Boost.Locale library IS ACCEPTED into Boost. The details follow, starting with the voters in favor, in the order their reviews were received: * John Bytheway * Steven Watanabe * Sebastian Redl * Fabio Fracassi ("possibly conditional") * Noah Roberts * Steve Bush * Volker Lukas * Paul A. Bristow * Matus Chochlik * Gevorg Voskanyan Those opposed: * Ryou Ezoe * Phil Endecott (but "borderline") * Edward Diener * Mathias Gaunard * Vincente BOTET ("count my vote as 1/2 or 1/4 vote") There was also an early off-list review from Darren Cook which did not include a vote, only listing issues. There was a great deal of discussion around the library, and a number of issues detailed. The major ones (and some less major ones that were repeated by several reviewers) are summarized below, along with the initials of the reviewer(s) who brought them up and Artyom's responses. Note that although I followed the discussions closely, these are only the issues brought up in the formal reviews themselves. * Issue: date_time interface uses enums for periods, which is error prone and inconsistent with other date/time libraries. (JB) * Response: Will be addressed. * Issue: Reference documentation needs more detail or some things not clear; some terms used in the documentation are not defined or are defined too briefly; can't find headers that items are defined in from the documentation. (JB, SW, FF, PE, ED, MC) * Response: Will be addressed. * Issue: There are no prev/next links in the documentation, or tutorial can't easily be navigated. (DC, JB, SR, FF, MC) * Response: Looking into it. * Issue: Few examples include output. (JB) * Response: Will be addressed. * Issue: No examples in Asian languages; the library may have design flaws that are not apparent without them. (DC) * Response: [Artyom has indicated to me (privately) that he's adding such examples. -- CN] * Issue: The translation system requires narrow-character tags, making it English-centric. (RE, ED) * Response: The library implements the most popular and most widely used message-catalog format. It is not perfect, but it is the best system currently available. There may be a work-around if you really must use wide-character languages under Windows. * Issue: Support for wchar_t/UTF-16 is unclear. (RE, ED) * Response: Wide characters are fully supported. * Issue: Doesn't support Win32 API as a backend. (RE) * Response: Misunderstanding, Win32 API backend is fully supported. * Issue: boost::locale::format is not compatible with boost::format. (FF, NR) * Response: boost::format is too limited for use in localization, and throws on any error, which means that a translator error could crash the program. * Issue: boost::locale::date_time is not compatible with boost::date_time. (FF) * Response: An unavoidable consequence of the differences between them, which are necessary due to support for locale independence and non-Gregorian calendars. * Issue: Boundary analysis is only available when using ICU. (FF) * Response: At present, only the ICU backend supports proper boundary analysis. * Issue: Little documentation on the toolchain needed to extract strings and translate them, or the versions required. (FF, NR) * Response: Will be addressed. * Issue: Concerns about relying on GPL/LGPL-licensed tools, or their availability on all platforms, or recommendations to write a Boost version of these tools. (NR) * Response: Reimplementing these is non-trivial and unnecessary; the licensing for these tools does not affect the programs developed with them. All are available for all platforms; will add explicit instructions for getting the latest versions for Windows. * Issue: Use of strings instead of symbols for language and encoding makes run-time errors that could be compile-time errors. The most common ones should be symbols. (PE) * Response: There are dozens of character encodings, and even more locales, and no way to determine which ones are the most common. Not all encodings are supported by all backends or OS configurations. Names ignore case and non-alphanumeric characters, which should minimize errors that could be generated from them. utf_to_utf transcoding will be added. * Issue: Error handling (in conversions) is very basic. (PE) * Response: An unavoidable limitation of the backends. * Issue: Code could use more commenting. (PE, VL) * Response: Noted, will be addressed in the future. * Issue: Some documentation phrasing is confusing, or could use a native English speaker's input. (SR, VL) * Response: Will be addressed as discovered. * Issue: There are no lists of valid language, country, encoding, or variant strings. (ED) * Response: Listed in standards ISO-639 and ISO-3166, which are referenced in the library's documentation. These standards are updated occasionally, and should be referred to directly for the latest information. * Issue: Only works on contiguous, entirely-in-memory strings. (MG) * Response: All current backends require this, and it satisfies the vast majority of use-cases. * Issue: Boundary analysis goes through the entire string and returns a vector of positions. (MG) * Response: Not perfect, but given the limitations of the existing backends, it is reasonable. * Issue: The library's interface is not generic enough, or independent enough of the libraries that it wraps. (VB) * Response: The interface is similar to that of every other i18n library, and should make as few assumptions as possible. It should not be changed. * Issue: The date-time code should be merged into Boost.DateTime. (VB) * Response: Date-time code is locale-dependent by its nature, and is more natural in Boost.Locale. Updating Boost.DateTime to do everything that Boost.Locale's library does would require a lot of work, and in all the time it has existed, only the Gregorian calendar has been implemented. There are Boost libraries that overlap others, so this is not a novelty. -- Chad Nelson Oak Circle Software, Inc. * * *

18 71

[BOOST CORE C++ Feature] The super or base keyword for C++
by Max Hölzer 02 May '11

02 May '11

Hello, i was wondering if it makes sens to add the well known super or base keyword to the C++ language in a generic way. Here I have a simple example on how it would make inherited base or super class overloaded function calls easier. Example 1: class A { public: virtual void print() { std::cout << "A" << std::endl; } }; class B : public A { public: virtual void print() { std::cout << "B" << std::endl; std::cout << "super call "; A::print(); } }; class C : public B { public: virtual void print() { std::cout << "C" << std::endl; std::cout << "super call "; B::print(); } }; int main(int argc, char* argv[]) { A a; B b; C c; a.print(); // Prints A b.print(); // Prints B and super call A c.print(); // Prints C and super call B super call A return 0; } Adding a template class superable would avoid one to write the explicit base or super class name. Example 2: namespace boost { template<typename T> class superable : public T { public: typedef T super; // C++ and java style typedef T base; // C# style }; } class A { public: virtual void print() { std::cout << "A" << std::endl; } }; class B : boost::superable<A> { public: virtual void print() { std::cout << "B" << std::endl; std::cout << "super call "; super::print(); // C++ and java style call } }; class C : boost::superable<B> { public: virtual void print() { std::cout << "C" << std::endl; std::cout << "super call "; base::print(); // C# style call } }; int main(int argc, char* argv[]) { A a; B b; C c; a.print(); // Prints A b.print(); // Prints B and super call A c.print(); // Prints C and super call B super call A return 0; } If somebody could add this to the core boost library, that would be great. Sincerely yours, Max

2 1

[Boost.Log] compilation on msvc 2010 fail.
by Kim Kuen Tang 02 May '11

02 May '11

Hi all, i try to compile Boost.Log for msvc 2010. But it somehow fails. Please see the errors below. Is the msvc-10.0 compiler supported? Thanks for any comments Regards, Kim compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\event_log_backend.obj event_log_backend.cpp .\boost/log/detail/universal_path.hpp(46) : error C2039: 'external_string_type' : is not a member of 'boost::filesystem3::path' .\boost/filesystem/v3/path.hpp(54) : see declaration of 'boost::filesyst em3::path' .\boost/log/detail/universal_path.hpp(46) : error C2065: 'external_string_type' : undeclared identifier .\boost/log/detail/universal_path.hpp(49) : error C3203: 'is_same' : unspecializ ed class template can't be used as a template argument for template parameter 'T 1', expected a real type .\boost/log/detail/universal_path.hpp(49) : error C2955: 'boost::is_same' : use of class template requires template argument list .\boost/type_traits/is_same.hpp(37) : see declaration of 'boost::is_same ' .\boost/log/detail/universal_path.hpp(49) : error C2955: 'boost::mpl::if_' : use of class template requires template argument list .\boost/mpl/if.hpp(56) : see declaration of 'boost::mpl::if_' .\boost/log/detail/universal_path.hpp(53) : error C2039: 'basic_path' : is not a member of 'boost::filesystem' .\boost/log/detail/universal_path.hpp(53) : error C2065: 'basic_path' : undeclar ed identifier .\boost/log/detail/universal_path.hpp(53) : error C2988: unrecognizable template declaration/definition .\boost/log/detail/universal_path.hpp(53) : error C2059: syntax error : 'const' .\boost/log/detail/universal_path.hpp(64) : error C2143: syntax error : missing ';' before '<' .\boost/log/detail/universal_path.hpp(64) : error C2913: explicit specialization ; 'boost::log_mt_nt5::aux::make_path' is not a specialization of a class templat e .\boost/log/detail/universal_path.hpp(64) : error C2059: syntax error : '<' .\boost/log/detail/universal_path.hpp(65) : error C2143: syntax error : missing ';' before '{' .\boost/log/detail/universal_path.hpp(65) : error C2447: '{' : missing function header (old-style formal list?) .\boost/log/detail/universal_path.hpp(74) : error C2913: explicit specialization ; 'boost::log_mt_nt5::aux::make_path' is not a specialization of a class templat e .\boost/log/sinks/event_log_backend.hpp(963) : error C2061: syntax error : ident ifier 'basic_path' .\boost/log/sinks/event_log_backend.hpp(1048) : see reference to class t emplate instantiation 'boost::log_mt_nt5::sinks::basic_event_log_backend<CharT>' being compiled .\boost/log/sinks/event_log_backend.hpp(1042) : warning C4346: 'boost::log_mt_nt 5::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type .\boost/log/sinks/event_log_backend.hpp(1042) : error C2061: syntax error : iden tifier 'universal_path' libs\log\src\event_log_backend.cpp(494) : error C2275: 'boost::log_mt_nt5::aux:: universal_path' : illegal use of this type as an expression libs\log\src\event_log_backend.cpp(494) : warning C4346: 'boost::log_mt_nt5::aux ::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type libs\log\src\event_log_backend.cpp(494) : error C2143: syntax error : missing ') ' before 'const' libs\log\src\event_log_backend.cpp(494) : error C2182: 'construct' : illegal use of type 'void' libs\log\src\event_log_backend.cpp(494) : error C2350: 'boost::log_mt_nt5::sinks ::basic_event_log_backend<CharT>::construct' is not a static member libs\log\src\event_log_backend.cpp(498) : error C2059: syntax error : ')' libs\log\src\event_log_backend.cpp(532) : error C2143: syntax error : missing '; ' before '{' libs\log\src\event_log_backend.cpp(532) : error C2447: '{' : missing function he ader (old-style formal list?) ..\boost/log/sinks/event_log_backend.hpp(963) : error C2039: 'basic_path' : is no t a member of 'boost::filesystem' libs\log\src\event_log_backend.cpp(612) : see reference to class templat e instantiation 'boost::log_mt_nt5::sinks::basic_event_log_backend<CharT>' being compiled with [ CharT=char ] ..\boost/log/sinks/event_log_backend.hpp(963) : error C2039: 'basic_path' : is no t a member of 'boost::filesystem' ..\boost/log/sinks/event_log_backend.hpp(963) : error C2061: syntax error : ident ifier 'basic_path' ..\boost/log/sinks/event_log_backend.hpp(963) : error C2039: 'basic_path' : is no t a member of 'boost::filesystem' libs\log\src\event_log_backend.cpp(616) : see reference to class templat e instantiation 'boost::log_mt_nt5::sinks::basic_event_log_backend<CharT>' being compiled with [ CharT=wchar_t ] ..\boost/log/sinks/event_log_backend.hpp(963) : error C2039: 'basic_path' : is no t a member of 'boost::filesystem' ..\boost/log/sinks/event_log_backend.hpp(963) : error C2061: syntax error : ident ifier 'basic_path' call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime- link-static\threading-multi\event_log_backend.obj.rsp" ....failed compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runt ime-link-static\threading-multi\event_log_backend.obj... compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\nt6_event_log_backend.obj nt6_event_log_backend.cpp compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\debug_output_backend.obj debug_output_backend.cpp ....skipped <pbin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-st atic\threading-multi>libboost_log-vc100-mt-s-1_46_1.lib for lack of <pbin.v2\lib s\log\build\msvc-10.0\release\link-static\runtime-link-static\threading-multi>te xt_file_backend.obj... ....skipped <pstage\lib>libboost_log-vc100-mt-s-1_46_1.lib for lack of <pbin.v2\l ibs\log\build\msvc-10.0\release\link-static\runtime-link-static\threading-multi> libboost_log-vc100-mt-s-1_46_1.lib... compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\parser_utils.obj parser_utils.cpp compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\init_from_stream.obj init_from_stream.cpp compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\init_from_settings.obj init_from_settings.cpp ..\boost/log/detail/universal_path.hpp(46) : error C2039: 'external_string_type' : is not a member of 'boost::filesystem3::path' .\boost/filesystem/v3/path.hpp(54) : see declaration of 'boost::filesyst em3::path' ..\boost/log/detail/universal_path.hpp(46) : error C2065: 'external_string_type' : undeclared identifier ..\boost/log/detail/universal_path.hpp(49) : error C3203: 'is_same' : unspecializ ed class template can't be used as a template argument for template parameter 'T 1', expected a real type ..\boost/log/detail/universal_path.hpp(49) : error C2955: 'boost::is_same' : use of class template requires template argument list .\boost/type_traits/is_same.hpp(37) : see declaration of 'boost::is_same ' ..\boost/log/detail/universal_path.hpp(49) : error C2955: 'boost::mpl::if_' : use of class template requires template argument list .\boost/mpl/if.hpp(56) : see declaration of 'boost::mpl::if_' ..\boost/log/detail/universal_path.hpp(53) : error C2039: 'basic_path' : is not a member of 'boost::filesystem' ..\boost/log/detail/universal_path.hpp(53) : error C2065: 'basic_path' : undeclar ed identifier ..\boost/log/detail/universal_path.hpp(53) : error C2988: unrecognizable template declaration/definition ..\boost/log/detail/universal_path.hpp(53) : error C2059: syntax error : 'const' ..\boost/log/detail/universal_path.hpp(64) : error C2143: syntax error : missing ';' before '<' ..\boost/log/detail/universal_path.hpp(64) : error C2913: explicit specialization ; 'boost::log_mt_nt5::aux::make_path' is not a specialization of a class templat e ..\boost/log/detail/universal_path.hpp(64) : error C2059: syntax error : '<' ..\boost/log/detail/universal_path.hpp(65) : error C2143: syntax error : missing ';' before '{' ..\boost/log/detail/universal_path.hpp(65) : error C2447: '{' : missing function header (old-style formal list?) ..\boost/log/detail/universal_path.hpp(74) : error C2913: explicit specialization ; 'boost::log_mt_nt5::aux::make_path' is not a specialization of a class templat e ..\boost/log/sinks/text_file_backend.hpp(338) : warning C4346: 'boost::log_mt_nt5 ::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type .\boost/log/sinks/text_file_backend.hpp(524) : see reference to class te mplate instantiation 'boost::log_mt_nt5::sinks::basic_text_file_backend<CharT>' being compiled ..\boost/log/sinks/text_file_backend.hpp(338) : error C2146: syntax error : missi ng ';' before identifier 'path_type' ..\boost/log/sinks/text_file_backend.hpp(338) : error C2838: 'universal_path' : i llegal qualified name in member declaration ..\boost/log/sinks/text_file_backend.hpp(338) : error C4430: missing type specifi er - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_file_backend.hpp(509) : error C2061: syntax error : ident ifier 'path_type' ..\boost/log/sinks/text_file_backend.hpp(519) : error C2061: syntax error : ident ifier 'path_type' ..\boost/log/sinks/text_multifile_backend.hpp(62) : warning C4346: 'boost::log_mt _nt5::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type .\boost/log/sinks/text_multifile_backend.hpp(137) : see reference to cla ss template instantiation 'boost::log_mt_nt5::sinks::file::file_name_composer_ad apter<FormatterT>' being compiled ..\boost/log/sinks/text_multifile_backend.hpp(62) : error C2146: syntax error : m issing ';' before identifier 'result_type' ..\boost/log/sinks/text_multifile_backend.hpp(62) : error C2838: 'universal_path' : illegal qualified name in member declaration ..\boost/log/sinks/text_multifile_backend.hpp(62) : error C4430: missing type spe cifier - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_multifile_backend.hpp(74) : error C2653: 'result_type' : is not a class or namespace name ..\boost/log/sinks/text_multifile_backend.hpp(74) : error C2065: 'value_type' : u ndeclared identifier ..\boost/log/sinks/text_multifile_backend.hpp(77) : error C3203: 'is_same' : unsp ecialized class template can't be used as a template argument for template param eter 'T1', expected a real type ..\boost/log/sinks/text_multifile_backend.hpp(77) : error C2955: 'boost::is_same' : use of class template requires template argument list .\boost/type_traits/is_same.hpp(37) : see declaration of 'boost::is_same ' ..\boost/log/sinks/text_multifile_backend.hpp(85) : error C2653: 'result_type' : is not a class or namespace name ..\boost/log/sinks/text_multifile_backend.hpp(126) : error C2143: syntax error : missing ';' before '(' ..\boost/log/sinks/text_multifile_backend.hpp(126) : error C4430: missing type sp ecifier - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_multifile_backend.hpp(127) : error C4430: missing type sp ecifier - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_multifile_backend.hpp(177) : warning C4346: 'boost::log_m t_nt5::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type .\boost/log/sinks/text_multifile_backend.hpp(233) : see reference to cla ss template instantiation 'boost::log_mt_nt5::sinks::basic_text_multifile_backen d<CharT>' being compiled ..\boost/log/sinks/text_multifile_backend.hpp(177) : error C2146: syntax error : missing ';' before identifier 'path_type' ..\boost/log/sinks/text_multifile_backend.hpp(177) : error C2838: 'universal_path ' : illegal qualified name in member declaration ..\boost/log/sinks/text_multifile_backend.hpp(177) : error C4430: missing type sp ecifier - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_multifile_backend.hpp(180) : error C2065: 'path_type' : u ndeclared identifier ..\boost/log/sinks/event_log_backend.hpp(963) : error C2061: syntax error : ident ifier 'basic_path' .\boost/log/sinks/event_log_backend.hpp(1048) : see reference to class t emplate instantiation 'boost::log_mt_nt5::sinks::basic_event_log_backend<CharT>' being compiled ..\boost/log/sinks/event_log_backend.hpp(1042) : warning C4346: 'boost::log_mt_nt 5::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type ..\boost/log/sinks/event_log_backend.hpp(1042) : error C2061: syntax error : iden tifier 'universal_path' libs\log\src\init_from_settings.cpp(105) : warning C4346: 'boost::log_mt_nt5::au x::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type libs\log\src\init_from_settings.cpp(105) : error C2146: syntax error : missing ' ;' before identifier 'any_cast_to_path' libs\log\src\init_from_settings.cpp(105) : error C2433: 'boost::log_mt_nt5::aux: :universal_path' : 'inline' not permitted on data declarations libs\log\src\init_from_settings.cpp(105) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int libs\log\src\init_from_settings.cpp(105) : error C2377: 'boost::log_mt_nt5::aux: :universal_path' : redefinition; typedef cannot be overloaded with any other sym bol .\boost/log/detail/universal_path.hpp(49) : see declaration of 'boost::l og_mt_nt5::aux::universal_path' libs\log\src\init_from_settings.cpp(105) : error C2888: 'if_c<T1::value,T2,T3>:: type boost::log_mt_nt5::aux::universal_path' : symbol cannot be defined within n amespace 'anonymous-namespace' libs\log\src\init_from_settings.cpp(105) : error C2888: 'int boost::log_mt_nt5:: aux::universal_path' : symbol cannot be defined within namespace 'anonymous-name space' libs\log\src\init_from_settings.cpp(105) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int libs\log\src\init_from_settings.cpp(105) : error C2143: syntax error : missing ' ,' before '*' call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime- link-static\threading-multi\init_from_settings.obj.rsp" ....failed compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runt ime-link-static\threading-multi\init_from_settings.obj... compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\filter_parser.obj filter_parser.cpp

2 4

[lambda] Diff with Boost.Phoenix (for lambdas)
by lcaminiti 02 May '11

02 May '11

Hello all, Recently I used both Boost.Lambda and Boost.Phoenix to implement lambda functions. Why does Boost have two libraries that implement lambda functions? In my (limited) experience, Boost.Phoenix is more powerful than Boost.Lambda (and it has comparable run-times even if it has larger compile-times) plus Boost.Phoenix can do much more than "just" lambdas. * Is there anything that Boost.Lambda can do more than Boost.Phoenix? * Is there any application domain where using Boost.Lambda makes more sense than using Boost.Phoenix? Thank you. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-lambda-Diff-with-Boost-Phoenix-for… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

[filesystem] Decomposition of filenames beginning with period?
by Beman Dawes 01 May '11

01 May '11

Boost.Filesystem class path views filenames as being made up of a stem and an extension. My Windows Users directory includes files ".gitconfig" and ".netrc". The current class path implementation views these as having extensions of ".gitconfig" and ".netrc", respectively, and empty stems. To me, that's a bit counter intuitive. I guess I view filenames as always having stems, but extensions being optional. But I don't view that as a strong enough argument to change anything. Does anyone have a stronger argument than intuition for changing or retaining the current behavior? --Beman

13 20

Re : [Block Pointer] make_block
by Pierre Morcello 01 May '11

01 May '11

Hi Phil, >>> Phil Bouchard <philippe(a)fornux.com> wrote : >>> We can see it in action >>> in the following example: >>> https://svn.boost.org/svn/boost/sandbox/block_ptr/libs/smart_ptr/example/bl… A detail : I think you could improve your sample by replacing __FUNCTION__ by BOOST_CURRENT_FUNCTION (which is more portable), or by writing directly the name of the function. >>>Is it time for a review? I looked for automated tests in the sandbox directory (not examples) and I did not find any. Instead of doing "cout", you could use a class like that : class ForTests { static int counter; // incremented at each construction int id; // id = current value of the counter in the constructor static std::vector<int> destructionOrder; }; Each destruction pushes the id in the destructionOrder vector. Then at the end of the program you just need to compare the content of destructionOrder with what you should expect (and return 1 or 0). Also the same might be done for construction. Good job BTW, and good luck for the review, Pierre Morcello

2 4

Re: [boost] [Review] Type Traits Extension by Frederic Bron - Review summary and decision
by Ivan Le Lann 30 Apr '11

30 Apr '11

----- "Joachim Faulhaber" <afojgo(a)googlemail.com> a écrit : > Hi Frédéric, list, (snip) > > To save you some time, I have inserted my proposal as column D into > the Wiki at > https://svn.boost.org/trac/boost/wiki/GuideLines/Naming/OperatorTraitNames > I like those names, except "has_negate". I would have kept "has_unary_minus", in line with proposed "has_unary_plus". I also wonder if "has_negate" could be mistaken for "!" by some people. Regards, Ivan

4 4

[naming] standard: bitwise operations in the new standard (20.8.7)
by Joachim Faulhaber 30 Apr '11

30 Apr '11

Dear list, this posting is addressed specifically to those people who are involved in the standardisation process for c++. As far as I know Beman, Howard, Dave, Doug, ... On occasion of the Boost.TypeTraits extension we were discussing names for operators and operator call traits. As an important aspect, naming consistency with the standard and across boost libraries has been discussed. We have found that functors on bitwise operators // 20.8.7, bitwise operations: template <class T> struct bit_and; template <class T> struct bit_or; template <class T> struct bit_xor; are new in the upcoming standard and are named using prefix bit_ In contrast to that, within boost, entities referring to bitwise operators are almost consistently named using prefix bitwise_ This is done specifically in Boost.Proto but also Boost.MPI (boost/mpi/operations.hpp). bitwise_and, bitwise_or, bitwise_xor are declared and used at 95 lines in Boost Libraries currently. Since 20.8.7, bitwise operations are *new* in the standard and naming consistency would be great for users, do you think there is a chance that those 3 names can be changed to bitwise_and, bitwise_or, bitwise_xor ? If so, is there anything that can be done to help the process. I'd volunteer to write a paper, if necessary. This might be a tiny issue, but since operators are at the core of any language, a consistent naming around them might be of great value on the long run. Best regards, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de

4 4

[Review] Boost.Convert library last 3 days
by Edward Diener 30 Apr '11

30 Apr '11

This is a reminder that formal review of the Boost.Convert library by Vladimir Batov has 3 more days and ends on May 2. There have only been a small number of reviews and this is the last weekend to review the library. I am hoping that programmers who may have been busy during the week in their work will find time this weekend for a review. The review period ends on Monday at midnight, so please get your review in before the review period ends. If you intend to do a review of the library but feel you would be late in doing so, please contact me about it. *************** * Its Purpose * *************** The library builds on the past boost::lexical_cast experience, then takes those conversion-related ideas further to suit better today's applications and programing needs. It still offers simple, minimal interface, familiar conversion behavior and additionally provides: * throwing and non-throwing conversion-failure behavior; * support for the default/fallback value to be returned when conversion fails; * two types of the conversion-failure check - basic/simple and better/safe; * formatting support based on the standard std::streams and std::stream-based manipulators (like std::hex, std::scientific, etc.); * support for different locales; * support for boost::range-compliant char and wchar_t-based containers; * no DefaultConstructibility requirement for the Target/Destination type; * consistent framework to uniformly incorporate any type-to-type conversions, extensibility and additional room to grow. With its present support for string-to-type and type-to-string conversions it is an essential tool for applications making extensive use of configuration or MS-Windows-Registry-style files or having to process/prepare considerable amounts of data in, say, XML, etc. More so, it is easily extendable to accommodate, specialize and uniformly deploy new user-defined type-to-type conversions. ******************* * Where to get it * ******************* You can get the library, using Subversion, from https://svn.boost.org/svn/boost/sandbox/convert. The HTML documentation is part of the distribution and can be found at libs/convert/index.html in the distribution above. ******************** * Writing a review * ******************** The reviews and all comments should be submitted to the developers list, and the email should have "[convert] Review" at the beginning of the subject line to make sure it's not missed. Please explicitly state in your review whether the library should be accepted. The general review checklist: - 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. Edward Diener, Review Manager

1 0

Re: [boost] boost] BoostLog: how to write log files into different folders named under Year/Month/Day
by edger 30 Apr '11

30 Apr '11

I have no experience with Boost.Log. But it seems the character "/" is reserved for the file system, thus not acceptable in file names. In you case, you are asking Boost,Log to creat 3 nested folders %Y, %m and %d, and then a file xxx_%N.log. Boost.Log may not support this as this function is supposed to be in Boost.Filesystem. HTH. 2011/4/29 <boost-request(a)lists.boost.org> > > Date: Fri, 29 Apr 2011 18:43:35 +1000 > From: Jinqiang Zhang <jasonzha(a)gmail.com> > Subject: [boost] BoostLog: how to write log files into different > folders named under Year/Month/Day > > e.g. like "%Y/%m/%d/xxx_%N.log" > > when I tried it, it created folder named %Y, ... but what I what is '2011' > instead. > > any idea ? > > Jinqiang >

1 0

[convert] Review
by Thomas Heller 29 Apr '11

29 Apr '11

Hi, Following is my review of the convert library proposed by Vladimir Batov. > - What is your evaluation of the design? I think the design is not good. After having read through the documentation, I think that the API is too convoluted. The use of operator>> feels misplaced. From the documentation it is not really clear what the relation between the target type, the nested result and the converter function object is. Additionally, the rational behind the non-throwing version isn't very clear to me. It feels like a step backwards: Weren't explicitly returned error codes obsoleted by exceptions? Moreover, I don't get how the design really is superior to boost::lexical_cast, and why it couldn't been implemented as an extension to that library. The use of this converter function object looks like a nice concept at first sight but, as mentioned above, in the end, probably adds more confusion and problems than anything else. I don't think that having everything hidden behind this static from function is wise and should be rethought. Different functions, for different purposes would be better suited. > - What is your evaluation of the implementation? Didn't take a look at the implementation. > - What is your evaluation of the documentation? The overall documentation is Okayish. There are some minor typos and misplaced words. Proofreading it again should fix this. What is std::u8string? The reference section feels like a bad joke. It is incomplete and doesn't really add value. After reading through the documentation I got the feeling that the library is incomplete and not really finished yet. Almost any feature is experimental. One feature is mentioned but not really documented: The extension of the converter. > - What is your evaluation of the potential usefulness of the library? There is no doubt that the features implemented in the library are useful. > - Did you try to use the library? With what compiler? Did you have any > problems? Didn't try to use it. > - How much effort did you put into your evaluation? A glance? A quick > reading? In-depth study? Read through the documentation. > - Are you knowledgeable about the problem domain? No. > And finally: > Do you think the library should be accepted as a Boost library? No. I second that it feels more like a extension to boost::lexical_cast than anything else. Best regards, Thomas

2 4

[locale] Support of non US-ASCII character set for messages keys
by Artyom 29 Apr '11

29 Apr '11

Hello, After reviewing all the discussion I've decided to do following changes in the interface to provide better support for non-US-ASCII keys. The actual thing that convinced me is a requirement to be able to include chars like © into the text... Currently there are following classes: template<typename CharType> class message_format : public std::locale::facet { public: ... typedef CharType char_type; virtual char_type const *get(int domain_id,char const *context,char const *id) const = 0; ... }; class message { public: ... explicit message(char const *id); ... // convert message to localized message template<typename CharType> std::basic_string<CharType> str(std::locale const &locale) const; }; ... inline message translate(char const *id); inline std::string gettext(char const *id,std::locale const &loc=std::locale()); inline std::wstring wgettext(char const *id,std::locale const &loc=std::locale()); ... Basically message is created using narrow id only and can be converted to multiple output formats narrow, wide and so on. std::cout << translate("Hello") << std::endl std::wcout << translate("Hello") << std::endl; And you could call: message msg = translate("Hello"); std::string hello = msg.str<char>(); std::wstring whello = msg.str<wchar_t>(); Work together. I'll change it in following way: template<typename CharType> class message_format : public std::locale::facet { public: ... typedef CharType char_type; virtual char_type const *get(int domain_id,char_type const *context,char_type const *id) const = 0; ... }; template<typename CharType> class basic_message { public: typedef CharType char_type; typedef std::basic_string<char_type> string_type; ... explicit message(char_type const *id); ... // convert message to localized message string_type str(std::locale const &locale) const; }; typedef basic_message<char> message; typedef basic_message<wchar_t> wmessage; typedef basic_message<char16_t> u16message; typedef basic_message<char32_t> u32message; ... inline message translate(char const *id); inline wmessage translate(wchar_t const *id); inline std::string gettext(char const *id,std::locale const &loc=std::locale()); inline std::wstring wgettext(wchar_t const *id,std::locale const &loc=std::locale()); ... Now you would have to: std::cout << translate("Hello") << std::endl std::wcout << translate(L"Hello") << std::endl; And you should call: message msg = translate("Hello"); wmessage wmsg = translate(L"Hello"); std::string hello = msg.str(); std::wstring whello = msg.str(); Additionally you would be able to specify the encoding of the source strings when adding domain. boost::locale::generator gen; gen.add_messages_domain("myprogram","windows-936"); While the default would always be UTF-8. So if you write in the program: std::cout << translate("平和") << std::cout Under GCC using UTF-8 sources you have anythig to do. If you are using MSVC then you'll have to provide a charset name as shown above or use u8"平和" Of course this would break the API for users who currently use Boost.Locale (and I know at least several project who will suffer). But this would probably bring it so some logical point and prevent rising these questions. If course you should remember that untranslated non-US-ASCII strings would be converted in the run-time to current locale's encoding. Regards, Artyom Beilis P.S.: Of course the documentation will still discourage programmers from using non-US-ASCII keys as they may not be displayed properly in local character sets and may confuse users.

2 3

BoostLog: how to write log files into different folders named under Year/Month/Day
by Jinqiang Zhang 29 Apr '11

29 Apr '11

e.g. like "%Y/%m/%d/xxx_%N.log" when I tried it, it created folder named %Y, ... but what I what is '2011' instead. any idea ? Jinqiang

1 0

Re: [boost] [MSM] Interrupt anonymous transitions or blocking process_events?
by Christophe Henry 28 Apr '11

28 Apr '11

>> You can make a circular buffer of, say, boost::function<void()>, this >> allows you to anonymize functors, for example this can be assigned >> into this boost::function: >> template<class Fsm, class Event> >> struct process_some_event >> { >> process_some_event(Fsm* fsm): fsm_(fsm){} >> void operator()() >> { >> fsm_->process_event(Event()); >> } >> Fsm* fsm_; >> }; >> >> Or as a variant, you can make a boost::function<void(my_fsm&)> with >> the corresponding operator(). Whatever fits better in your case. > > Yes, that could be a good solution. I haven't had time to try that way > yet but I will as soon as I can. > > This discussion and similar stuff should go into the docs or some > examples file. Perhaps it would help more people? It has certainly been > of great help to me. Actually I plan to do even better and offer a more general library solution for this. It's one of the big items on my list, and a pretty high one. Cheers, Christophe

1 0

[Trac] Version + milestone
by Daniel James 28 Apr '11

28 Apr '11

Hi, Please can someone change the default version on trac tickets to 1.46.1 (it's currently 1.47.0 which hasn't been released) and I think the milestone for 1.46.0 should be removed from the options. thanks, Daniel

1 0

Proposed Boost.Detect library
by Bryce Lelbach 28 Apr '11

28 Apr '11

It's been mentioned in the past that Boost.Config is not intended as a library for external use (e.g. it's for use inside of Boost). Thus, I was motivated to write the following awhile back: https://github.com/brycelelbach/detect Unlike Boost.Config, it also detects underlying system architecture. Enjoy. -- Bryce Lelbach aka wash boost-spirit.com px.cct.lsu.edu github.com/lll-project

3 2

[accumulators] regression tests and MingW/gcc-4.5.2
by Edward Diener 28 Apr '11

28 Apr '11

Attempting to run regression tests for accumulators from Boost trunk using MingW/gcc-4.5.2 leads to Vista popping up with messages that cc1plus.exe ( gcc's compiler ) has stopped working. Any ideas why this is happening. For other versions of MingW/gcc the accumulators regression tests work normally.

4 8

[numeric] Is there interest in detecting precision loss?
by Antony Polukhin 28 Apr '11

28 Apr '11

There have been some requests for detecting precision loss during conversion from float types to integral types. But the current numeric converter just rounds the float number. This proposal provides two classes, that can be used as a Float2IntRounder in boost::numeric::converter. One of them determinates, is there any precision loss, the second class determinates is there precision loss before user supported sign in decimal part. On precision loss an exception boost::numeric::precision_loss_error is thrown. The proposal can be found at https://docs.google.com/document/d/1IsA40cq9kYF31jDM_tyIvVNnvC5-uI9-5ez52pz… Tests (and usage examples) can be found at https://docs.google.com/document/d/1cbYYDcL1t0jbZ7hUFqXODu3VKoWe4_A5IMdXHN5… Is there interest in this for Boost? If there is, shall I add documentation?

1 0

[Mutual Pointer] Docs
by Phil Bouchard 28 Apr '11

28 Apr '11

Hi, I renamed the pointer once more to mutual_ptr and I added a caveat to the documentation. It is accessible here: https://svn.boost.org/svn/boost/sandbox/mutual_ptr/libs/smart_ptr/doc/tutor… -Phil

2 3

[review] boost::convert
by Jeroen Habraken 28 Apr '11

28 Apr '11

Hi, My review: -- What is your evaluation of the design? The overall design is very flexible, there are a few points though: - Although this might be a matter of taste I find the choice of operator >> to add modifiers rather odd, it smells a bit like operator abuse. Also, it forces you to use braces in std::cout << (boost::convert<int>::from("12") >> std::hex) << "\n"; for example, maybe using a member function is an option. - In might be nice to add a way to return a default-constructed object to the non-throwing interface. This is useful in combination with boost::optional: boost::convert<boost::optional<int> >::from_default("XXX") returning an boost::optional<int>() instead of having to write boost::convert<boost::optional<int> >::from("XXX", boost::optional<int>());. -- What is your evaluation of the implementation? Had a quick read through the code, it looks fine except that names containing "__" are reserved (used in the include guards). -- What is your evaluation of the documentation? The documentation covers all aspects of the library quite nicely. This in contrast to the reference which seems mostly empty, in my opinion it doesn't add much and can simply be removed. Since the behaviour of convert seems to be different to lexical_cast (see below) it might be useful to add a section listing these differences. Lastly the documentation contains a couple of examples, it would be nice to have these as separate files in libs/convert/example. -- What is your evaluation of the potential usefulness of the library? The library is very flexible and the extra features are nice, however there is a rather large problem, in my opinion. This is the domain of boost::lexical_cast, a library that has matured over the years and is in heavy use. It can not be deprecated or worse, removed. Even though it has problems (mostly missing functionality, which boost::convert has implemented) I do not believe adding a second library is a proper solution. Instead this functionality should be added to boost::lexical_cast itself (and patches to do so have been proposed over the years). -- Did you try to use the library? With what compiler? Did you have any problems? Yes, on Mac OS X with both gcc 4.2.1 (the default shipped by Apple) and 4.5.2. Problems: - boost::convert<int>::from("-123.2") behaves differently from boost::lexical_cast<int>("-123.2"), the former returns -123 whilst the latter throws. Whilst I'm not saying one is better than the other, the differences should be documented for people switching. - boost::convert<int>::from('1') results in a rather long error message (http://codepad.org/YgoR8H2t) if the conversion from X to Y isn't possibly this should be made clear in a more user-friendly way. -- How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I've read the documentation, had a quick glance at the source code and tried the basic functionality of the library. -- Are you knowledgeable about the problem domain? As the author of boost::coerce I'm familiar with the conversion domain, however I'm less familiar with the locale domain. -- Do you think the library should be accepted as a Boost library? No it should not, instead the extra functionality should be added to boost::lexical_cast. Kind regards, Jeroen Habraken

3 5

[Review] Boost.Convert library is ongoing
by Edward Diener 27 Apr '11

27 Apr '11

Since there have been no reviews of this library yet, this is another reminder that formal review of the Boost.Convert library by Vladimir Batov is ongoing and ends on May 2. If you have felt that lexical_cast is not flexible enough for use, please take a look at this library and review it. *************** * Its Purpose * *************** The library builds on the past boost::lexical_cast experience, then takes those conversion-related ideas further to suit better today's applications and programing needs. It still offers simple, minimal interface, familiar conversion behavior and additionally provides: * throwing and non-throwing conversion-failure behavior; * support for the default/fallback value to be returned when conversion fails; * two types of the conversion-failure check - basic/simple and better/safe; * formatting support based on the standard std::streams and std::stream-based manipulators (like std::hex, std::scientific, etc.); * support for different locales; * support for boost::range-compliant char and wchar_t-based containers; * no DefaultConstructibility requirement for the Target/Destination type; * consistent framework to uniformly incorporate any type-to-type conversions, extensibility and additional room to grow. With its present support for string-to-type and type-to-string conversions it is an essential tool for applications making extensive use of configuration or MS-Windows-Registry-style files or having to process/prepare considerable amounts of data in, say, XML, etc. More so, it is easily extendable to accommodate, specialize and uniformly deploy new user-defined type-to-type conversions. ******************* * Where to get it * ******************* You can get the library, using Subversion, from https://svn.boost.org/svn/boost/sandbox/convert. The HTML documentation is part of the distribution and can be found at libs/convert/index.html in the distribution above. ******************** * Writing a review * ******************** The reviews and all comments should be submitted to the developers list, and the email should have "[convert] Review" at the beginning of the subject line to make sure it's not missed. Please explicitly state in your review whether the library should be accepted. The general review checklist: - 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. Edward Diener, Review Manager

3 2

[msm] need to increase the fusion set and map size to 30
by Kim Kuen Tang 27 Apr '11

27 Apr '11

Hi all, i defined a transition table with more than 20 transitions. After that the compiler complained that a fusion set is only defined up to 10 elements. So i added the following statement in the file as indicated by the doc. #define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS #define BOOST_MPL_LIMIT_VECTOR_SIZE 30 //or whatever you need #define BOOST_MPL_LIMIT_MAP_SIZE 30 //or whatever you need However this does not solve the problem, since it is fusion who is complaining. So i added these two statements at the beginning, and this solved the problem. # define FUSION_MAX_SET_SIZE 30 # define FUSION_MAX_VECTOR_SIZE 30 Perhaps we can add this somewhere in the doc. Kind regards , Kim

1 0

[TR1] tr1 functional compile time looks strange
by falcou 27 Apr '11

27 Apr '11

An empty file including only boost/tr1/functional.hpp seems to compile in 3s ... Does any of the latest patches botched something here ?

3 5

[Memory Managed Pointer] Review Request
by Phil Bouchard 27 Apr '11

27 Apr '11

Greetings, I apologize for all the confusion but I renamed once more the memory manager to mm_ptr. Its documentation is accessible at: https://svn.boost.org/svn/boost/sandbox/mm_ptr/libs/smart_ptr/doc/index.html Regards, -Phil

8 21

accurate sum accumulator (kahan)
by Gaetano Mendola 27 Apr '11

27 Apr '11

Hi all, I had to implement in terms of boost accumulators the Kahan summation algorithm. I will paste at the end of this message the accumulator, the feature and the extractor source code. This accumulator reduces the numerical error obtained with standard sequential sum, as example the sum of 1e6f elements equal to 1e-6f should give 1.0f, this is the results obtained with sum and sum_kahan: tag::sum: 1.009038925 tag::sum_kahan: 1.000000000 I'm not sure if that sum_kahan is worth to be inserted in the accumulators provided with boost, I'm not an expert of boost:accumulators (I just followed the guide to make this new accumulator) so not sure if you prefer to have a fast_sum and an accurate_sum instead of sum and sum_kahan. Regards Gaetano Mendola // File kahan_sum.hpp #ifndef KAHAN_SUM #define KAHAN_SUM #include <boost/accumulators/framework/accumulator_base.hpp> #include <boost/accumulators/framework/parameters/sample.hpp> #include <boost/numeric/conversion/cast.hpp> namespace boost { namespace accumulators { namespace impl { template<typename Sample> struct sum_kahan_accumulator : accumulator_base { typedef Sample result_type; template<typename Args> sum_kahan_accumulator(Args const & args) : sum(args[sample | Sample()]), compensation(boost::numeric_cast<Sample>(0.0)) { } template<typename Args> void operator ()(Args const & args) { const Sample myTemp1 = args[sample] - this->compensation; const Sample myTemp2 = this->sum + myTemp1; this->compensation = (myTemp2 - this->sum) - myTemp1; this->sum = myTemp2; } result_type result(dont_care) const { return this->sum; } private: Sample sum; Sample compensation; }; }}} namespace boost { namespace accumulators { namespace tag { struct sum_kahan : depends_on< > { typedef impl::sum_kahan_accumulator< mpl::_1 > impl; }; }}} namespace boost { namespace accumulators { namespace extract { extractor< tag::sum_kahan > const sum_kahan = {}; } using extract::sum_kahan; }} #endif

21 68

[Config] A proposal to Boost.Config.
by Kohei Takahashi 27 Apr '11

27 Apr '11

Hi, Boost.Config provides BOOST_PLATFORM macro (it will expand to strings). However, it cannot use to switch including header like followings. #include <boost/config.hpp> #include "somedir/" BOOST_PLATFORM "/someheader.hpp" So, I propose a new macro BOOST_PLATFORM_LABEL (change to more suitable name). That provide not stringized platform name like this. #define BOOST_PLATFORM_LABEL linux By using such macro, will be able to switch including header. #include <boost/config.hpp> #include <boost/preprocessor/stringize.hpp> #include BOOST_PP_STRINGIZE( somedir/BOOST_PLATFORM_LABEL/someheader.hpp ) However, such macro has a problem. For example, it fail including when *linux* (or another label) defined to other symbol. #include <boost/config.hpp> #include <boost/preprocessor/stringize.hpp> #define linux others #include BOOST_PP_STRINGIZE( somedir/BOOST_PLATFORM_LABEL/someheader.hpp ) // Oops! Expand to somedir/others/someheader.hpp in linux. How do you feel this macro? Thanks. -- TAKAHASHI Kohei College of Information Science, University of Tsukuba private mail: flast(a)flast.jp others: flast(a)ac-room.org s0911476(a)coins.tsukuba.ac.jp

2 2

[vault] Boost Vault is down
by Edward Diener 27 Apr '11

27 Apr '11

It appears the link to the Boost vault is down. Attempting http://www.boostpro.com/vault/index.php gives the "Server not found" message. Can this be fixed fairly ASAP ? The distribution for the next review, starting tomorrow, is in the vault ( no surprise there ), and since I am the review manager I have already gotten an e-mail pointing out that the distribution can not be accessed.

4 4

[GSoC] Results
by Andrew Sutton 26 Apr '11

26 Apr '11

All, I'd like to thank all of the students who submitted proposals this year. We had a number of excellent proposals, many more than last year. Ultimately, we were only able to accept 10 proposals and so some deserving proposals could not be accepted. If your proposal was not accepted, and you would like to know why, please send me an email. I will be more than happy to discuss the results with you. For the students whose proposals were accepted, tomorrow starts the "Getting to know you" phase of GSoC. Assuming that you will be done with exams soon, you should be getting started with the Boost infrastructure, build system, and documentation tools. Questions about any of the above can be directed to your mentors or the mailing list --- hopefully both. I will send out some instructions this week for getting started with the Boost SVN repository. I'd also like to thank all of the mentors who contributed to the reviewing process. The reviewing seems to have gone (more or less) smoothly, and the quality of the reviews was excellent. Thanks again, Andrew

1 0

Re: [boost] [MSM] Interrupt anonymous transitions or blocking process_events?
by Christophe Henry 26 Apr '11

26 Apr '11

>> Depending on how you use it, yes. I'm a bit worried with race >> conditions in case your state machine is also used in another thread, >> which would also call process_event. > > Yes, I protect every call to process_event with a mutex. Since I don't > have that many events I have created a member function that wraps and > protects the process_event call. (One member function per event.) Usually, the destructor gets tricky. Not only, but this one is hard to get right. >> Alternatively (if you want to avoid locking/deadlocking/rc), you could >> also move the worker thread out of the fsm and have both communicate >> with synchronized message queues. You might want to have a look at >> boost::circular_buffer, which provides an example >> (http://www.boost.org/doc/libs/1_46_1/libs/circular_buffer/doc/circular_buff…) > > Yes, that is an interesting idea. But how do you solve the problem with > passing events on to the message queue? The events are all of different > types. Do you mean that there should be some parsing of strings or some > other identifier? You can make a circular buffer of, say, boost::function<void()>, this allows you to anonymize functors, for example this can be assigned into this boost::function: template <class Fsm, class Event> struct process_some_event { process_some_event(Fsm* fsm): fsm_(fsm){} void operator()() { fsm_->process_event(Event()); } Fsm* fsm_; }; Or as a variant, you can make a boost::function<void(my_fsm&)> with the corresponding operator(). Whatever fits better in your case. Regards, Christophe

2 1

Darwin Clang help needed
by John Maddock 26 Apr '11

26 Apr '11

There are some strange failures in Boost.Math for Clang on Darwin, for example: boost::math::binomial_coefficient<long double>(42, 15); Appears to be returning zero. The code is pretty simple, so is anyone able to step through it and see what's going wrong (it seems to be working OK for type double BTW). Thanks, John.

2 2

[asio] [date_time] boost::asio::deadline_timer performance
by Isidor Zeuner 25 Apr '11

25 Apr '11

Hi all, while profiling a boost::asio-based application with heavy use of timers, I noticed many CPU cycles being burnt inside a gregorian::date::date constructor, which I traced down as being called from asio::deadline_timer::expires_from_now. As asio::deadline_timer just specializes asio::basic_deadline_timer using posix_time::ptime, I assume this can be tuned by using another time implementation. Is there a particular implementation targeted at low overhead, ideally with high accuracy? Are there other ways of tuning timer performance? Best regards, Isidor -- Isidor Zeuner http://quidecco.de/cms/blog/

1 0

[accumulators]
by Edward Diener 25 Apr '11

25 Apr '11

Attempting to run the accumulators regression test on the trunk, using 'bjam toolset=gcc-4.5.2' ( MingW/gcc-4.5.2 ) is giving me a number of pop-up Windows in Vista saying that "cc1plus.exe has stopped working". Cc1plus.exe is the gcc compiler under MingW. In the output there are a number of failures. Does anybody know why this is occuring ?

1 0

[Pack Pointer] Review Request
by Phil Bouchard 25 Apr '11

25 Apr '11

Greetings, I've followed what users were dissatisfied with and I turned out renaming Shifted Pointer to Pack Pointer. Furthermore I've added a small tutorial that can be found at: https://svn.boost.org/svn/boost/sandbox/pack_ptr/libs/smart_ptr/doc/tutoria… Once again the main documentation is at: https://svn.boost.org/svn/boost/sandbox/pack_ptr/libs/smart_ptr/doc/index.h… I still need cleaning up some code but it works well with complex examples and I would like queuing the library up for a review if possible. Regards, -Phil

2 2

[build] bjam library path on gcc
by Lorenzo Caminiti 25 Apr '11

25 Apr '11

Hello all, How do I setup gcc library path (LD_LIBRARY_PATH) for bjam? For example I get this error when using bjam: lcaminiti@lcaminiti-PORTEGE-R700:~/sandbox/boost-sandbox-local/libs/local/example$ bjam -q profile_boost_local toolset=gcc ...patience... ...found 790 targets... ...updating 2 targets... gcc.compile.c++ bin/gcc-4.5.1/debug/profile_boost_local.o gcc.link bin/gcc-4.5.1/debug/profile_boost_local bin/gcc-4.5.1/debug/profile_boost_local.o: In function `main': /home/lcaminiti/sandbox/boost-sandbox-local/libs/local/example/profile_boost_local.cpp:17: undefined reference to `boost::chrono::system_clock::now()' /home/lcaminiti/sandbox/boost-sandbox-local/libs/local/example/profile_boost_local.cpp:23: undefined reference to `boost::chrono::system_clock::now()' /home/lcaminiti/sandbox/boost-sandbox-local/libs/local/example/profile_boost_local.cpp:31: undefined reference to `boost::chrono::system_clock::now()' /home/lcaminiti/sandbox/boost-sandbox-local/libs/local/example/profile_boost_local.cpp:33: undefined reference to `boost::chrono::system_clock::now()' bin/gcc-4.5.1/debug/profile_boost_local.o: In function `__static_initialization_and_destruction_0': /home/lcaminiti/sandbox/boost-trunk/boost/system/error_code.hpp:214: undefined reference to `boost::system::generic_category()' /home/lcaminiti/sandbox/boost-trunk/boost/system/error_code.hpp:215: undefined reference to `boost::system::generic_category()' /home/lcaminiti/sandbox/boost-trunk/boost/system/error_code.hpp:216: undefined reference to `boost::system::system_category()' collect2: ld returned 1 exit status "g++" -o "bin/gcc-4.5.1/debug/profile_boost_local" -Wl,--start-group "bin/gcc-4.5.1/debug/profile_boost_local.o" -Wl,-Bstatic -Wl,-Bdynamic -Wl,--end-group -g ...failed gcc.link bin/gcc-4.5.1/debug/profile_boost_local... ...failed updating 1 target... ...updated 1 target... But I can tell bjam to add -L and -l options as in the following it would work: lcaminiti@lcaminiti-PORTEGE-R700:~/sandbox/boost-sandbox-local/libs/local/example$ g++ -o "bin/gcc-4.5.1/debug/profile_boost_local" -Wl,--start-group "bin/gcc-4.5.1/debug/profile_boost_local.o" -Wl,-Bstatic -Wl,-Bdynamic -Wl,--end-group -g -L/home/lcaminiti/sandbox/boost-trunk/stage/lib -lboost_chrono -lboost_system Thank you. -- Lorenzo

2 1

How to use ASIO without SSLv2?
by Steve M. Robbins 25 Apr '11

25 Apr '11

Hi, Debian just turned off SSL v2 support in openssl due to security concerns [1]. Unfortunately, this broke compilation of several ASIO-using programs such as pion-net [2] and witty [3]. These programs all fail to compile with the following diagnostics: > In file included from /usr/include/boost/asio/ssl/context_service.hpp:30:0, > from /usr/include/boost/asio/ssl/context.hpp:22, > from /usr/include/boost/asio/ssl.hpp:19, > from /build/user-witty_3.1.8-2-amd64-wHJ4Kv/witty-3.1.8/src/http/Server.h:22, > from /build/user-witty_3.1.8-2-amd64-wHJ4Kv/witty-3.1.8/src/http/HTTPStream.C:12: > /usr/include/boost/asio/ssl/detail/openssl_context_service.hpp: In member function 'void boost::asio::ssl::detail::openssl_context_service::create(SSL_CTX*&, boost::asio::ssl::context_base::method)': > /usr/include/boost/asio/ssl/detail/openssl_context_service.hpp:73:28: error: '::SSLv2_method' has not been declared > /usr/include/boost/asio/ssl/detail/openssl_context_service.hpp:76:28: error: '::SSLv2_client_method' has not been declared > /usr/include/boost/asio/ssl/detail/openssl_context_service.hpp:79:28: error: '::SSLv2_server_method' has not been declared What does one have to do in order to use ASIO without SSLv2 support? One suggestion [3] is to simply enclose the related code within #ifndef OPENSSL_NO_SSL2. In the cse of openssl_context_service::create(), however, placing this around the affected switch cases would result in executing the default case default: impl = ::SSL_CTX_new(0); break; Would this be safe to do? Are there other places in the code that need to be addressed? Thanks, -Steve [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589706 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621402 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622070

1 0

Re: [boost] [locale] Formal review of Boost.Locale library -- final days
by Artyom 24 Apr '11

24 Apr '11

> From: Gevorg Voskanyan <v_gevorg(a)yahoo.com> > Points I don't like most: > > - The boundary interface isn't attractive (in my opinion, shared by some other > > > reviewers) As it was common request that was shared by several reviewers I'll take a look on it. And I'll also take a look on regex like interface that may actually be relevant for this case. > - Operator overloading is sometimes used in unintuitive ways. For example > operator/ used to get the value for a specific period type > I'll also update a little date_time the interface to be consistent with other boost libraries, for example to get year(t) t=year(1990); In addition or instead of t = year * 1990 t / year > [snip] > > I noticed lack of exception safety in some places and places where RAII > should have been used. The implementation might benefit from a careful > examination intended to find and fix such kind of problems. I've seen several places that were pointed by reviewers and I had seem some problems with copy constructors in the code so I'll review them. > I also think that > dynamic memory management is used too freely - in many cases their usage is > unavoidable but in some cases they are. Having said that I appreciate that >some > > efforts have already been put in that direction: I noticed several places >where > > fixed-size buffers were used if data is small enough and dynamic allocation if > > > it's larger. > > More details at http://permalink.gmane.org/gmane.comp.lib.boost.devel/218352 > Noted. > > - What is your evaluation of the documentation? > > The documentation structure is good. It enables a new user to get started with > > > the library quickly. The well-organized references help to find documentation > for a specific facility in almost no time. I would however like to see more > links within the text of the pages. There are many spelling and grammar issues > > > in the documentation. Many of them have been already addressed to some extent >by > > me and other reviewers, but it feels like there are still more of them left > there. I agree that the documentation should be thoroughly scanned for such > language issues by a native English speaker. > I also think there should be more examples. > > More details at http://permalink.gmane.org/gmane.comp.lib.boost.devel/218117 >and > > http://permalink.gmane.org/gmane.comp.lib.boost.devel/218343 > I'll do my best, hopefully after third language review you did it would be much better. > > - What is your evaluation of the potential usefulness of the library? > > Very useful. > > > - Did you try to use the library? With what compiler? Did you have any > > problems? > > I have played with the library using number/ordinal formatting, date >formatting, > > currency formatting, spellout, case conversion and boundary analysis features. > >I > > have not used encoding conversion, normalization, timezone/calendar, (message) > > > formatting and collation features. I have used ICU backend only. > > Environment: > FreeBSD 8.0 > g++ 4.5.0 in C++03 mode > ICU 3.8.1 system-wide installation > > What I used was intuitive and easy, except for boundary analysis as noted >above. > > I had some incorrect results most of which I believe are ICU issues. > Some which I'm not so sure about though: > - output of as::local_time was wrong by 2 hours; as::gmt was correct. >Moreover, > > as::date printed the yesterday's date when the local time was 2:24 AM ! > /bin/date shows correct local time, so I believe my system time zone settings > are fine. This is problem with older ICU versions. ICU had included several bugs in the local time zone detection. I assume that the test test_icu_of_os_timezone fails. I've seen things things on FreeBSD: http://art-blog.no-ip.info/files/nightly-build-report.html (Even it is not tested under Boost namespace it still catches the problems) What you need is latest ICU. It had several fixes of timezone detection in 4.6 and this version works fine and passes all the tests. So I recommend you to use it with ICU 4.6 on FreeBSD. There is a some workaround I implemented for Linux for other problem of detecting timezone as "localtime" but it seems that on FreeBSD it is other issue as it has little bit different timezone handling. > - "Note: not all locales provide rules for spelling numbers. In such a case >the > > number would be displayed in decimal format." This was not the case: > std::cout << as::spellout << 117 << std::endl; printed "one hundred and > seventeen" under hy_AM.UTF-8 locale. I'll take a look on this, it may be either CLDR issue or ICU mis-detecting hy_AM locale. > > There were loads of "comma at end of enumerator list" warnings. > > > - How much effort did you put into your evaluation? A glance? A quick > > reading? In-depth study? > > Closer to in-depth study with more than 25 hours invested. > > > - Are you knowledgeable about the problem domain? > > I am well aware of localization problems and approaches that can be used to > tackle them. I have developed in-house solutions to address some localization > needs on as-necessary basis. > > > And finally, every review should answer this question: > > > > - Do you think the library should be accepted as a Boost library? > > Yes. Thank you very much for the review. Artyom

2 1

Re: [boost] [locale] Review results for Boost.Locale library
by Brent Spillner 24 Apr '11

24 Apr '11

On 24 Apr 2011 14:06 Ryou Ezoe wrote: >Believe me, There are so many Boost users who don't know English at all. >They are good at using Boost library because there are enough translations. And why would this library, designed to support international users, be any different? >This English-dependent library cannot be used by these users. >They CAN use English identifier in the source file. like name of >functions, classes, variables etc(badly If you ask me) >But text is written in their language. >There is no way they use English text. >The text in software is not just written by programmer alone. >Non-programmers also write text. >So this library requires English for anybody. What are you proposing, a library where the identifiers and keys are all in Japanese? Esperanto? Perhaps all comments should be replicated in the ~20 most commonly-used languages so that non-English speakers can not just use the library, but also contribute? Artyom has created an internationalization library, not the magic translator box from Star Trek. >That means, if everybody can use this English-dependent library, the >purpose of this library, the localization, is unnecessary. If non-English speakers can't use English-centric internationalization tools, where are the competitors for gettext and ICU? >Blaming people for not to use English doesn't work. They don't care. >Just like you don't care their language. For someone who purportedly doesn't care about non-English speakers, Artyom certainly went to a lot of trouble to create an internationalization library. I'm sure we'd all agree that it's unfortunate that some familiarity with English is a requirement to use almost any programming language, library, or toolchain, which is an additional burden for the millions of non-native-English-speaking programmers and aspiring programmers out there. But that's due to a confluence of historical, economic, and compatibility reasons, and has nothing to do with this library. In fact, by making internationalization easier, Boost.Locale will over time likely /increase/ the number of software tools that people can use in their native languages. Your criticism is entirely misplaced. Brent

1 0

[gil new_io] tiff alpha channel support
by Erik Hvatum 24 Apr '11

24 Apr '11

Briefly: gil new_io does not support tiff alpha channel. Is support planned? If not, I'll attempt to add it and submit a patch if successful. Details: I am using the latest code from the gil-contributions googlecode SVN repository. The following causes a crash when "tifffile.tif" is interleaved 32-bit rgba (ie 8*4 bits, including the alpha channel): argb8_image_t image; read_and_convert_image("tifffile.tif", image, tiff_tag()); If "tifffile.tif" is planar instead of interleaved, no crash occurs. However, the image is not loaded correctly - all channels are filled with the same values, causing the image to apparently be grayscale. "tifffile.tif" stored without an alpha channel loads correctly, but the alpha channel is essential for my application. Around line 237 of io_new/formats/tiff/read.hpp, I see that we are reading into an rgb8_view_t for 8 bit per sample images, so we're obviously not going to retain alpha channel data even if it is read correctly. Additionally, TIFFTAG_SAMPLES_PER_PIXEL is read but not respected. To avoid crashes for tiff images with extra channels, row_buffer_helper must be aware of TIFFTAG_SAMPLES_PER_PIXEL. So that the alpha channel is retained for RGBA images, in the PHOTOMETRIC_RGB case near line 237, if TIFFTAG_SAMPLES_PER_PIXEL is 4, we should read into an rgba*_view_t.

3 4

[FunctionTypes] Can FunctionTypes be extended to work with Boost.Function?
by Mostafa 23 Apr '11

23 Apr '11

This is a request to have FunctionTypes extended to work with Boost.Function. According the current documentation, it does not handle the latter. Rationale: I have a template parameter that can be either a function type or a boost::function, and I would like a uniform method to decompose their signature and return type. Note: an alternative does exist where one to specialize on boost::function and carry out around its underlying signature, but that's just an annoying hassle, and, more importantly, it doesn't work if old style syntax for boost::function is used. Thanks, Mostafa

1 0

[locale] Review of the proposed Boost.Locale library
by Matus Chochlik 23 Apr '11

23 Apr '11

Hi all, this is my review of the proposed Boost.Locale library: DISCLAIMER: I'm pretty familiar with the issues of application localization for the Central/East European region mainly with Slavic languages, mostly those using Latin characters, (Slovak, Czech, Polish), also a little bit with languages using some variant of Cyrillic characters (Russian, Bulgarian) and with West European languages like German, i.e. languages having somewhat different capitalization and collation rules than English has, some of which have also multiple plural forms in certain inflection cases. But I have no experience whatsoever with localization in other environments: Middle-East, Asian, etc. so I might have missed some important issues arising in such cases. - Please explicitly state in your review whether the library should be accepted. Yes, it should be accepted. The general review checklist: - What is your evaluation of the design? Straightforward and easy to use, similar to other localization libraries I've worked with. - What is your evaluation of the implementation? Since most of the problems I've spotted (and many more) were already addressed in Steven's very thorough review of the code and in other reviews I'm not going to reiterate them. AFAIK the Boost Coding Guidelines require max 80 characters per line in the source code. The sources of Boost.Locale do not follow this guideline which makes them slightly less readable, one needs to scroll a lot horizontally. Otherwise I leave the quality of the implementation to be judged by more competent people on this list. Concerning the external dependencies, ICU, tools from GNU gettext (msgfmt, ...), etc.: I don't think that it would be a good idea to re-implement them. A lot of effort has been put into their development, they are well supported, maintained and available for every major platform so I don't see any advantage in reinventing the wheel. - What is your evaluation of the documentation? The documentation is readable and clear to someone familiar with l10n/i18n however things like collation, capitalization, case folding, etc. should be better explained for users who are not familiar with them. The previous/next page links are missing which is little inconvenient. In the Message Formatting/Message Translation section there is a typo: ------------------------------------------------------------------------------ std::cout << boost::locale::tanslate("Hello World!") << std::endl; ------------------------------------------------------------------------------ In the examples and code snippets in the docs I think that "using namespace std;" should be removed and instead of "using namespace boost::locale;" there should be something like "namespace bl = boost::locale;" which would make much clearer which parts of the sample code are referring to Boost.Locale's code and which to std library; Also (but I might be mistaken here since I'm not a native German speaker) the example in the "Conversions" section names a variable 'gruben' (this variable stores the word "grüßen") a German would probably call this variable 'grussen' since 'ß' != 'b'. - What is your evaluation of the potential usefulness of the library? This library is very useful for people working on portable applications that are to be localized for non-English environments. - Did you try to use the library? With what compiler? Did you have any problems? Yes (I built the library), - on Debian Linux (64bit) with ICU 4.6 - using cmake - with GCC 4.6.0 non-C++0x mode: no problems - with GCC 4.6.0 C++0x mode: auto_ptr - related warnings - using bjam (Boost 1.46.1) - with GCC 4.6.0 non-C++0x mode: no problems - on Windows Vista Basic (32-bit) + cygwin + ICU 4.5 - using bjam (Boost 1.46.1) - with GCC 4.3.4: no problems - on Windows Vista (32-bit) + ICU 4.6 (bin package for Win32) - using bjam (Boost 1.46.1) - with MSVC 9: the library built, but for some reason bjam didn't use ICU even with -sICU_PATH specified, and I didn't have the time to investigate why. Also I've built and linked the examples and several small apps of my own trying out some features of the library (message translation, collation), on Debian 64-bit + GCC. - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I've read the documentation, some parts of the discussion and some of the other reviews on this list, built the library and examples (see above) + written several toy applications, I've had only a quick glance at the sources. Put together probably somewhere around 12 hours. - Are you knowledgeable about the problem domain? I've worked on several projects with some kind of l10n/i18n using several different utilities (GNU gettext, wxWidgets, an in-house solution). But I certainly don't consider myself an expert on localization for the reasons stated above. Best regards, Matus Chochlik

5 6

[Shifted Pointer] Review Request
by Phil Bouchard 23 Apr '11

23 Apr '11

Greetings, I would like to request a review of the Shifted Pointer utility. I am happy to say that I've corrected some bugs within the library itself and now it seems to be working well with all test files. As pointed out by John Maddock, some pool functions such as ordered_free() can still be optimized in speed or replaced but for now I would like to keep the interface as it is until perhaps some changes to the pool can be proposed. Once again to compile the test executables (with gcc): $ svn co http://svn.boost.org/svn/boost/sandbox/shifted_ptr $ cd shifted_ptr/libs/smart_ptr/example $ make shifted_ptr_test3 And its documentation can be found here: http://fornux.com/personal/philippe/devel/shifted_ptr/libs/smart_ptr/doc/ Regards, -Phil

8 24

Re: [boost] [locale] Formal review of Boost.Locale library -- final days
by Gevorg Voskanyan 23 Apr '11

23 Apr '11

Here's my formal review of the Boost.Locale library. > 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 > (me). > > Here are some questions you might want to answer in your review: > > - What is your evaluation of the design? I find this library mostly well-designed for localization needs. Points I like most: - Being designed around std::locale system - Great integration with I/O streams - Concentrating mostly on ICU - Yet having backend architecture to account for new possible backends as having them becomes reasonable - Supporting char, wchar_t, char16_t and char32_t - Using (and lobbying for) UTF-8 as default encoding Points I don't like most: - The boundary interface isn't attractive (in my opinion, shared by some other reviewers) - Operator overloading is sometimes used in unintuitive ways. For example operator/ used to get the value for a specific period type Observations: The interface sometimes doesn't meet the expectations a Boost user could have from a Boost library. E.g. not accepting arbitrary ranges as arguments. The overall design of the library takes into account ABI compatibility and ability to switch backends at runtime. Such concerns are not typical for Boost libraries so they have more freedom in some design decisions where Boost.Locale has no much choice. Which I personally don't find to be much of a problem and IMO shouldn't prevent acceptance into Boost. The author goes long ways to make Boost.Locale usable not only for regular Boost users but also for people who write *nix packages (including himself - CppCMS). This might see Boost.Locale gain more popularity, which can only have positive effect on the library and its evolution. > - What is your evaluation of the implementation? I glanced over the sources but didn't give it the thorough examination it deserves. I generally find the implementation reasonable given the constraints above. I noticed lack of exception safety in some places and places where RAII should have been used. The implementation might benefit from a careful examination intended to find and fix such kind of problems. I also think that dynamic memory management is used too freely - in many cases their usage is unavoidable but in some cases they are. Having said that I appreciate that some efforts have already been put in that direction: I noticed several places where fixed-size buffers were used if data is small enough and dynamic allocation if it's larger. More details at http://permalink.gmane.org/gmane.comp.lib.boost.devel/218352 > - What is your evaluation of the documentation? The documentation structure is good. It enables a new user to get started with the library quickly. The well-organized references help to find documentation for a specific facility in almost no time. I would however like to see more links within the text of the pages. There are many spelling and grammar issues in the documentation. Many of them have been already addressed to some extent by me and other reviewers, but it feels like there are still more of them left there. I agree that the documentation should be thoroughly scanned for such language issues by a native English speaker. I also think there should be more examples. More details at http://permalink.gmane.org/gmane.comp.lib.boost.devel/218117 and http://permalink.gmane.org/gmane.comp.lib.boost.devel/218343 > - What is your evaluation of the potential usefulness of the library? Very useful. > - Did you try to use the library? With what compiler? Did you have any > problems? I have played with the library using number/ordinal formatting, date formatting, currency formatting, spellout, case conversion and boundary analysis features. I have not used encoding conversion, normalization, timezone/calendar, (message) formatting and collation features. I have used ICU backend only. Environment: FreeBSD 8.0 g++ 4.5.0 in C++03 mode ICU 3.8.1 system-wide installation What I used was intuitive and easy, except for boundary analysis as noted above. I had some incorrect results most of which I believe are ICU issues. Some which I'm not so sure about though: - output of as::local_time was wrong by 2 hours; as::gmt was correct. Moreover, as::date printed the yesterday's date when the local time was 2:24 AM ! /bin/date shows correct local time, so I believe my system time zone settings are fine. - "Note: not all locales provide rules for spelling numbers. In such a case the number would be displayed in decimal format." This was not the case: std::cout << as::spellout << 117 << std::endl; printed "one hundred and seventeen" under hy_AM.UTF-8 locale. There were loads of "comma at end of enumerator list" warnings. > - How much effort did you put into your evaluation? A glance? A quick > reading? In-depth study? Closer to in-depth study with more than 25 hours invested. > - Are you knowledgeable about the problem domain? I am well aware of localization problems and approaches that can be used to tackle them. I have developed in-house solutions to address some localization needs on as-necessary basis. > And finally, every review should answer this question: > > - Do you think the library should be accepted as a Boost library? Yes. > Be sure to say this explicitly so that your other comments don't > obscure your overall opinion. > -- > Chad Nelson > Oak Circle Software, Inc. Gevorg

1 0

[locale] Review: Design and Implementation
by Gevorg Voskanyan 22 Apr '11

22 Apr '11

I briefly skimmed over the sources and noticed some things I'd like to get addressed. Unfortunately this is far from being a real comprehensive review as I would like it to be, due to time constraints. operator= should return non-const reference. I don't really like date_time::operator/() as a syntactic sugar for date_time::get() when the involved period is not period::year, but e.g. period::day_of_week_local. It raises eyebrows when first seeing it, forcing one to look at the documentation to find out what that overloaded operator means. BOOST_LOCALE_DECL needs to be defined in terms of BOOST_SYMBOL_EXPORT and BOOST_SYMBOL_IMPORT. Also the exception classes need to be attributed with BOOST_SYMBOL_VISIBLE (I assume all member functions of exception classes are defined inline, which appears to be the case). Many constructors should be explicit but aren't. Existence of standard C++11 features should be checked with BOOST_NO_XXX macros instead of BOOST_HAS_XXX. E.g. !defined BOOST_NO_CHAR16_T rather than defined BOOST_HAS_CHAR16_T. Boundary interface should seriously be reconsidered. I would like to see it be very much like that of regex_iterator and regex_token_iterator. Please replace throw with BOOST_THROW_EXCEPTION. For classes having a swap member function there should also be a free swap function found by ADL. 'int unused' parameters for post-in/decrement operators will trigger warnings, the parameter name better be removed. Functions using Boost.Locale facets under the hood (e.g. boost::locale::fold_case) should be documented as might throw std::bad_cast. boundary.hpp: line 311: s/continious/contiguous/ line 319: e-b might not be well-formed, use std::distance(b, e) line 338: s/collsion/collision/ date_time.hpp: line 936: t.time(v); should not be called unless in >> v; succeeded format.hpp: line 104: s/get_posision/get_position/ Also, shouldn't this be const? formatting.hpp: line 229: this is not exception-safe localization_backend.hpp: line 145: why not boost::scoped_ptr? shared/formatting.cpp: line 45: this is not exception-safe. Why not use copy-and-swap idiom? (it has no swap() currently, but I see no reason why there couldn't be) shared/mo_lambda.cpp: line 239: s/tockenizer/tokenizer/ encoding/codepage.cpp: Why are converter objects allocated on free store and not stack? icu/all_generator.hpp: What do //ok comments signify? posix/codecvt.cpp: lines 82, 85: needs changed to use RAII posix/converter.cpp: line 159: s/impl_std/impl_posix/ std/std_backend.cpp: line 229: s/impl icu/impl_std/ (noticed cases like this in some other files as well, not necessarily in std/) Gevorg P.S. I plan to submit my final review with vote in 7-8 hours time from now. I hope that is OK.

2 1

[locale] Review: Reference documentation
by Gevorg Voskanyan 22 Apr '11

22 Apr '11

group__boundary.html: s/like and sentence boundaries/line and sentence boundaries/ s/alalisys/analysis/ s/Find a positions/Find positions/ s/like break is required/line break is required/ s/possible followed by/possibly followed by/ "Either first or second sentence break type;." redundant ; "word_any Any word including numbers, 0 is special flag, equivalent to 15." What has 0 to do with word_any that it's being mentioned here? Isn't 15 the value for word_none? s/Maximal used mask/All types of words mask/ maybe? structboost_1_1locale_1_1boundary_1_1break__info.html: s/begging/beginning/ classboost_1_1locale_1_1boundary_1_1boundary__indexing_3_01char_01_4.html: s/analisys/analysis/ classboost_1_1locale_1_1boundary_1_1mapping.html: s/Class the holds/Class that holds/ "When the object is created in creates index" s/in/it/ ? "it is used mostly together ..." capitalize the first letter s/vise versa/vice versa/ many occurrences "you can set the mask value sentence_term" sentence_term should be a link. In general the whole documentation should be scanned to add links where appropriate. "would not be compatible with old ones" add a period classboost_1_1locale_1_1boundary_1_1token__iterator.html: s/white spaces punctuation/white spaces, punctuation/ s/Opposite of ===/Negation of ==/ classboost_1_1locale_1_1boundary_1_1break__iterator.html: "Return the mark that token iterator points at." Shouldn't be break iterator? group__collation.html: "This module that introduces collation related classes" Rephrasing needed classboost_1_1locale_1_1collator__base.html: s/a base class that included/a base class that includes/ What about providing synonyms for collation levels like base_letters = primary, letters_accents = secondary, etc. classboost_1_1locale_1_1collator.html: s/stc::collate/std::collate/ s/two strings in rage/two strings in range/ Strings in rage can be harmful :D It isn't specified what values compare functions return. E.g. is it < 0, 0, > 0 or -1, 0, 1. Needs to be explained what kind of value is returned in which case. group__convert.html: s/various function/various functions/ s/It does not takes/It does not take/ many occurrences group__date__time.html: s/a enum/an enum/ s/perood/period/ date_time now(time(0),hebrew_calendar) cout << "Year:" t / perood::year <<" Full Date:"<< as::date_time << t; Should be: date_time now(time(0),hebrew_calendar); cout << "Year:" << t / period::year <<" Full Date:"<< as::date_time << t; classboost_1_1locale_1_1date__time__period__set.html: Why are the operations not commutative? s/should be in range [0,size)/should be in range [0,size())/ classboost_1_1locale_1_1calendar.html: s/Get grates possible/Get greatest possible/ classboost_1_1locale_1_1date__time.html: s/opject/object/ many occurrences s/perios/period/ "Check if the current time is in daylight saving time" Current time or the time represented by *this? In all other places, references to "current time" need to be checked. s/ingnores/ignores/ many occurrences s/substract/subtract/ many occurrences s/valrious/various/ s/gettimeofdat/gettimeofday/ namespaceboost_1_1locale_1_1period.html: "hour_12 12 clock hour [0..11]" AFAIU the range of hours in AM/PM notation is [1..12], no? s/withing/within/ s/First day if week/First day of week/ s/convers period_type/convert period_type/ namespaceboost_1_1locale_1_1time__zone.html: "namespace that holds function for operating global time zone identifier" Needs rephrasing, perhaps "namespace that holds functions for operating with global time zone" I don't think BOOST_LOCALE_DECL needs to be in documentation. s/returing/returning/ classboost_1_1locale_1_1basic__format.html: s/curl brackets/curly braces/ s/hight/height/ "sci or `scientific` -- display in scientific format" why is scientific in backticks and sci not? "per or percent -- format percent value." What happens when a value out of range [0..1] is passed in? "locale -- with parameter -- switch locale for current operation. This command generates locale with formatting facets giving more fine grained control of formatting. For example: " Where is the example? What are the requirements for Formattible? group__format.html: s/Definiton/Definition/ 2 occurrences s/It use locale and of \a out stream/It uses locale of \a out stream/ group__manipulators.html: s/is treaded as/is treated as/ many occurrences namespaceboost_1_1locale.html: s/namespae/namespace/ s/independed/independent/ multiple occurrences s/typr/type/ "Generate codepage conversion facets" Isn't "encoding" more appropriate? namespaceboost_1_1locale_1_1util.html: s/the codecvt faced/the codecvt facet/ s/it know/it knows/ s/can can/can/ two occurrences classboost_1_1locale_1_1calendar__facet.html: s/Locale id (for work with std::locale/Locale id (needed to work with std::locale)/ classboost_1_1locale_1_1generator.html: s/protable/portable/ s/if it deals with/if dealing with/ classboost_1_1locale_1_1hold__ptr.html: s/transfered/transferred/ two occurrences classboost_1_1locale_1_1info.html: s/Is underlying encoding is UTF-8/True if the underlying encoding is UTF-8/ classboost_1_1locale_1_1localization__backend.html: s/swithc/switch/ s/differnt/different/ s/priority/priotiry/ classboost_1_1locale_1_1localization__backend__manager.html: s/avalible/available/ s/combing/combining/ classboost_1_1locale_1_1message__format.html: "Default constructor" Not exactly, can be called with a size_t argument as well structboost_1_1locale_1_1message.html: "Message class can be explicitly converter to string class" converted s/defailt/default/ \ a --> \a for doxygen, 3 occurrences operator<< not mentioned but should be as it is part of the message class interface A link to group__message.html would be helpful here structboost_1_1locale_1_1gnu__gettext_1_1messages__info.html: s/sturcture/structure/ s/this structure not useful/this structure is not useful/ s/Igronred/Ignored/ s/for narror/For narrow/ s/seach/search/ Inconsistent documentation for data members here: some are documented in Member Data Documentation, the other in the introduction. "Locale category, is set by default LC_MESSAGES, but ma." Incomplete? General remarks: Sometimes qualified ids make it harder to read. For example in group__boundary.html the boost::locale::boundary:: qualifiers make it really hard for me to read the important part here - the individual names. Gevorg

2 2

Re: [boost] [MSM] Interrupt anonymous transitions or blocking process_events?
by Christophe Henry 22 Apr '11

22 Apr '11

Hi Mathias, > Hi Christophe, > > Thank you for the helpful reply! You're welcome :) > That helped me alot doing it that way. Thank you! It was a struggle > before I realized how to call a process_event(...) from within a member > function. I hope I am doing it the right way :-) > > I also tried adding > > boost::signals2::signal<void ()> sig; > > to the statemachine but my compiler did not like that at all > (noncopyable errors). So I stayed with a mutex and a condition variable. > The way I did it can be improved I am sure... > > Anyway, you can see an outline below of how I did this. Perhaps this is > an ok way doing it? <snip> Depending on how you use it, yes. I'm a bit worried with race conditions in case your state machine is also used in another thread, which would also call process_event. Alternatively (if you want to avoid locking/deadlocking/rc), you could also move the worker thread out of the fsm and have both communicate with synchronized message queues. You might want to have a look at boost::circular_buffer, which provides an example (http://www.boost.org/doc/libs/1_46_1/libs/circular_buffer/doc/circular_buff…) Regards, Christophe

2 1

Re: [boost] [Foreach] Supporting range adaptors for temporary containers
by Ivan Le Lann 22 Apr '11

22 Apr '11

----- "Michel MORIN" <mimomorin(a)gmail.com> a écrit : > Sometimes it is convenient to apply range adaptors to a temporary > container > and iterate over it: > > // `using namespace boost::adaptors;` is assumed > BOOST_FOREACH(auto x, std::string("Hello, world!") | reversed) > {...} > > However, the lifetime of the temporary container ends before the loop > body > begins. This problem also exists in C++0x range-based for. > To solve this, I'd like to propose an extension of BOOST_FOREACH > macro: > IIUC, the line below is broken: auto const & broken_range = std::string("Hello, world!") | reversed; So it seems you're proposing to adapt BOOST_FOREACH to solve a problem in adaptors. How do you intend to fix C++11 builtin foreach? In C++11, I think this could be fixed with rvalue refs detection. Shouldn't any function relying on the fact that its arguments still exist after the call do that check? So either delete the &&-function or ... [disclaimer: ugly but funny] make it move the range inside the adaptor somehow. Ivan

4 4

[locale] Formal review of Boost.Locale library -- final days
by Chad Nelson 22 Apr '11

22 Apr '11

The final day of the Boost.Locale formal review is tomorrow, April 22nd. If you're planning to submit a review but haven't, now is the time. I'll accept reviews up until I complete the report on Saturday morning. 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 (me). 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. -- Chad Nelson Oak Circle Software, Inc. * * *

6 7

Re: [boost] Boost statechart viewer
by Christophe Henry 22 Apr '11

22 Apr '11

> I have no plan about Boost::MSM library in next two months. From the > first point of view I think that it shouldn't be difficult to update > the program to be able to work with Boost::MSM. So maybe after or > during summer holidays. > > If I do anything I will let you know. Hi Petr, If you decide to support MSM, I'll be happy to provide help if you need. Regards, Christophe

1 0

Fwd: Submission for Google Summer of Code 2011
by Suriya Singh 22 Apr '11

22 Apr '11

Project proposal: A lightweight platform independent library for graphics for Android. Start Date: 10 june 2011 Start Coding 10 june 2011 Documentation 1 August 2011 Testing: 25 July 2011 End date: 10 August 2011

1 0

[Foreach] Supporting range adaptors for temporary containers
by Michel MORIN 22 Apr '11

22 Apr '11

Sometimes it is convenient to apply range adaptors to a temporary container and iterate over it: // `using namespace boost::adaptors;` is assumed BOOST_FOREACH(auto x, std::string("Hello, world!") | reversed) {...} However, the lifetime of the temporary container ends before the loop body begins. This problem also exists in C++0x range-based for. To solve this, I'd like to propose an extension of BOOST_FOREACH macro: BOOST_ADAPTED_FOREACH(VARIABLE, RANGE, ADAPTORS) { // do something } which is conceptually equivalent to { auto const& rng = RANGE; // if RANGE is an lvalue, use `auto& rng = RANGE` BOOST_FOREACH(VARIABLE, rng | ADAPTORS) { // do something } } A temporary range, RANGE, is bound to a const reference and its lifetime is extended. (To do this, compiler support of rvalue references and `auto`/ `decltype` is needed. In C++03, a temporary range needs to be copied.) Then we can do the following without worry about the lifetime problem. BOOST_ADAPTED_FOREACH( char ch , std::string("Hello, world!") , reversed | replaced('e', 'a')) { std::cout << ch; } To bind a temporary range, we can also use (non-const) rvalue reference. But I choose to use const lvalue reference. The rationale is * In the pipe operator, a temporary range is captured as a const reference. So if we use rvalue reference binding, the mutability of the resulting range (`auto&& rng = RANGE; rng | ADAPTORS`) and `RANGE | ADAPTORS` would be different. For example, `std::list<int>(3) | reversed` is a const range, but `auto&& rng = std::list<int>(3); rng | reversed` is a mutable range. To be consistent with `RANGE | ADAPTORS`, using const lvalue reference (`auto const& rng = RANGE; rng | ADAPTORS`) is better. * Mutable iteration over temporary ranges makes little sense. Note that, BOOST_ADAPTED_FOREACH works fine if an input range is a temporary containers, but it does not work properly if an input is a range-proxy (such as `iterator_range`) of a temporary container. In this case, only the lifetime of range-proxies is extended and dangling reference to the temporary range occurs: BOOST_ADAPTED_FOREACH( int i , boost::equal_range(std::multiset<int>(...), 1) , reversed) { // Oops, dangling reference! // Input is an `iterator_range` of the temporary multiset<int>(...) } BOOST_ADAPTED_FOREACH( int i , boost::assign::list_of(1)(2)(3)(4)(5) , reversed) { // Oops, dangling reference! // Input is a reference to the temporary `list_of(1)` } Header file and sample code attached. (Though I omitted the C-string support for simplicity, it is easy to add the support.) If there are some interests about this proposal, I will create a trac ticket. Comments? Regards, Michel

3 5

[locale] Review
by Mathias Gaunard 21 Apr '11

21 Apr '11

Let us start with my decision: I vote against inclusion of Boost.Locale into Boost in its current state, but strongly encourage the author to reconsider resubmitting it after some design issues have been reconsidered. In which case, I would be in favour of putting it on the fast-track for a mini-review. Since I am the author of another Unicode library that I'd like to see included in Boost, I hope that my review will not be considered biased. I believe Boost.Locale is a valuable and useful library, and I believe both libraries can coexist. The main reason for my decision is the interface that the library provides: albeit it aims at abstracting the backend used to implement the facilities, it exposes too much of how those facilities are implemented, which prevents benefiting from future backends that may not have the same limitations as the current backends do. Indeed, the Boost.Locale rationale clearly says that it only takes std::basic_string and const char* as input because that's what the backend libraries expect anyway. Yet there are various scenarios where this is useful: - I might want to apply some operation to data in a file without putting it all to memory first; Boost.Locale could copy that memory by chunks to apply that operation for backends that have no native support for this. Copying the whole file to memory is a good enough approximation for a first version. - The input I have may not be directly available in the form of a contiguous buffer, but I wouldn't mind if Boost.Locale copied it. If we consider the functions from_utf, to_utf and between, they can either take a const char*, two const char*, or a std::basic_string. Clearly this would be better if those functions took a range, which covers all three of these cases. It's not just a matter of being generic, it makes the library easier to use since the range is defined by a single argument which can be anything I want, I do not need to convert to what the library needs. If the library needs to do conversion behind the scenes, it can do it just like that, behind the scenes. Taking a range causes the problem however of what the return type should be: I think there should be two variants, one which returns a string, and one which appends to a container (like Boost.StringAlgo) or write to an output iterator (like STL algorithms). Obviously, the former would be defined in terms of the latter. This causes however a big problem: all backends would not be interchangeable with a stable unique ABI. Maybe some template specializations could be injected at link-time, but they would have to be full concrete specializations. Maybe the idea of backends being interchangeable at the ABI level needs to be rethought. After all, isn't being interchangeable at the API level enough, since you can easily mangle the configuration in a symbol to cause an error if linking with the non-matching backend? Still talking about conversion between encodings, I would like it if it was possible to statically choose the encodings we're converting between, as some backends could directly expose a specialized and optimized some_encoding_to_some_other_encoding function. Note the remarks about conversion between encodings also applies to case folding, collation etc. Being able to specify statically the normalization form you're normalizing to and things like that could be useful just as for the character encodings. Perhaps not made clear from the docs, but Boost.Locale embeds another mechanism than the functions in the conv namespace to convert between character encodings: using the classes derived from boost::locale::util::base_converter. This is the only interface that can be passed incomplete data, as obtained through buffering. That interface was designed to implement codecvt facets, and unfortunately, it's not much better. The library implements its own UTF-8/UTF-16/UTF-32 conversion logic there regardless of which backend is used; it is a shame it cannot reuse the to_utf or from_utf functions in all cases. This implementation is also quite tricky since the state management prevents the code from being simple and self-contained. That interface does not allow optimized conversion functions to be used. Compatibility with codecvt facets is a nice feature, but it shouldn't impair the interface of the component that could have other usages. Furthermore, I do not find the boundary analysis interface satisfying at all. It is not made clear in the docs that doing boundary analysis actually goes through the whole string and returns a vector of positions corresponding to the boundaries. You can use that vector to adapt any range into a range of strings. Each dereferencing copies the subrange defined by the vector into a new temporary string. This is pretty terrible. I want to be able to find the boundaries as I advance through a string, or be able to find the closest boundary from an arbitrary position without having to process the whole string. I do not want to have to copy my whole input range into little strings for no reason. Usage of this feature is also unnecessarily verbose. It should not be more than a function call to turn a range of characters into a range of tagged ranges of characters. This part of the library is the one that needs the more work. Ironically enough, it's also the only one that deals a bit with iterators and ranges, and I just asked for more iterators and ranges at the beginning of this review ;). Finally, I will not comment on the implementation too much, since I think other Boosters already did that (though I did not read all of it). There is some unnecessary or non-optimal code, some code more complicated than it should be, some compile-time values tested at runtime, some things that could have reused existing utilities from Boost, and some inappropriate use of reinterpret_cast. While most of the backends are separated, it is not the case for encoding/codepage.cpp, which is shared by all backends and contains ifdefs. This is not a very nice extension point. I'm also a bit concerned about the generalized usage of virtual functions anywhere; it seems unnecessary in quite a few places, please prefer using templates when dynamic binding is not required. A lot of new and vectors too, I'd prefer if ideally the library never allocated anything. I hope my review will be well received and that you will consider all of my "feature requests". Your library is practical and can get things done for sure, but maybe it's not quite as good as it could be in terms of interface yet. Also, if I want Boost.Unicode to ever be a possible backend, Boost.Locale needs to be able to make the most of it ;).

8 18

[Review] Formal review of Boost.Convert library starts Saturday
by Edward Diener 21 Apr '11

21 Apr '11

This is a reminder that formal review of the Boost.Convert library by Vladimir Batov starts on Saturday, April 23, and is scheduled to last through May 2. *************** * Its Purpose * *************** From the introduction: Boost.Convert builds on the boost::lexical_cast experience and still offers a simple, minimal interface, familiar conversion behavior and more: * throwing and non-throwing behavior when conversion fails; * support for the default/fallback value to be returned when conversion fails; * two types of the conversion-failure check - basic/simple and better/safe; * formatting support based on the standard std::streams and std::stream-based manipulators (like std::hex, std::scientific, etc.); * support for different locales; * support for boost::range-compliant char and wchar_t-based string containers (std::string, std::wstring, char const*, wchar_t const*, char array[], etc.); * no DefaultConstructibility requirement for the Target/Destination type; * extendibility and additional room to grow. ******************* * Where to get it * ******************* You can find the Boost.Convert here: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost-… The HTML documentation is part of the distribution and can be found at libs/convert/index.html in the distribution above. ******************** * Writing a review * ******************** The reviews and all comments should be submitted to the developers list, and the email should have "[convert] Review" at the beginning of the subject line to make sure it's not missed. Please explicitly state in your review whether the library should be accepted. The general review checklist: - 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. Edward Diener, Review Manager

1 0

GSoC 2011
by mahbubul hasan 21 Apr '11

21 Apr '11

Hi, I am Mahbub. I am a CSE graduate. I just saw you had a proposal regarding queue and heap in GSoC 2010. In my undergraduate I did thesis on heaps. In that time I learned soft heap, it might be interesting to you. Here is the short description of soft heap<http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.85.3258&rep=rep1&t…>.( http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.85.3258&rep=rep1&t…) Soft heap is a heap like data structure but with some uncertainty. This data structure supports insert, delete, merge, findmin. It does every work in amortized constant time except insert operation which takes O( log 1/e ) where 0<e=<.5. Here e is error rate. The data structure will never contain more than en corrupted elements. There are two versions of soft heap. 1. By Binomial Tree 2. By forest of binary tree There is one more thing that might interesting to you. That is, in my undergraduate I improved the running time of heap sort by significant amount by applying pairing technique. The paper is submitted to International Journal of Computer Mathematics and it is under review now. It mainly improves Carlsson's variant of heapsort. It also improves the deletion method proposed by Gonnet and Munro (Heaps on Heaps). [The heap is inplace, that means no additional space is required] It also improves the Weak Heapsort. WeakHeapsort is a sorting method which requires O(n) additional bit to sort. However applying the pairing technique it can be reduced to O(n/2) additional bit. It is known that weakheap is the theoretically best known algorithm. [Best considering number of comparisons] So I am just curious if you are interested in these types of algorithms. I saw no possible proposal category where these fits in, but I thought you might be interested. Please let me know what do you think about this. Mahbub

2 6

[locale] Formal review of Boost.Locale library EXTENDED
by Chad Nelson 21 Apr '11

21 Apr '11

(This message made it to the announcements list, but the copy intended for the developers list didn't make it and I hadn't noticed. I apologize if this inconvenienced anyone.) There have been only a handful of reviews of the proposed Boost.Locale library to date, and several people have requested more time to provide theirs, so the formal review of the Boost.Locale library has been extended. The deadline for reviews is now 11:59pm UTC on Friday, April 22nd. For those in the Western hemisphere, remember that that's earlier than it might seem -- 7:59pm in New York, 4:59 in Los Angeles. I'll accept late reviews until I complete the report on Saturday morning, but please try to get yours in earlier. You can find the "boost_locale_for_review" version here: https://sourceforge.net/projects/cppcms/files/boost_locale/ The HTML documentation can also be seen at: http://cppcms.sourceforge.net/boost_locale/html/index.html 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 (me). 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. -- Chad Nelson Oak Circle Software, Inc. * * *

11 34

review needed
by Xu Sun 20 Apr '11

20 Apr '11

Hi, I've posted my proposal on 04/05 but still didn't receive any reply including email or comment. I will be very appreciated if any one can give me any feedback about my proposal. The link is here: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/sunbow/1 Sorry to bother others. Thanks, Xu Sun

4 4

new operator traits: how to merge to the trunk?
by Frédéric Bron 20 Apr '11

20 Apr '11

Dear developpers, I am working on answering all comments of the review concerning the addition of operator traits. When this is finished, what will be the process to include the extension to the trunk? Is it something I will have to do my-self? If so, what is the way to do it? Thanks in advance, Frédéric

2 1

[Fusion] Tentative of trasnform_if failed :(
by falcou 19 Apr '11

19 Apr '11

The following code http://ideone.com/xYk4X doesn't compile and i cant get the why of it. The goal is to have a fusion transform_if that takes a compile-time predicates For each element int he sequence, if the predicates its true, we apply some transform on it, if not we return the element unchanged. What am I missing ?

3 6

Interest in doing project "concept Traits library"
by Rachit Kulshreshtha 19 Apr '11

19 Apr '11

I know that i am running late as i had my university exams but i have been following the projects entitled under Google Summer of Code 2011. I am a student of BITS-Pilani University, India doing my B.E. in Electronics and Instrumentation. I was going through the project "concept traits library" , trying to understand it. I was able to gather much information about what it is and how it works, with some details of the functions under operator traits, mpl_ext and even Concept traits. But since their is no well defined problem statement given on the website, i was wanting to know what functions \ templates already exist as parts of the library and what are we expected to create. Please reply soon... Thnx in advance -- its a bird, its a plane, its a rocket no its Rachit

3 14

Re: [boost] [MSM] Interrupt anonymous transitions or blocking process_events?
by Christophe Henry 19 Apr '11

19 Apr '11

Hi Mathias, <snip> >By calling p.process_event(play()); the the player will start playing >Song1 and then change to the next song by itself. But now in single >threaded mode it blocks until it reaches "Song3". So it is not possible >to process any other events during this time. In other words, it cannot >process another process_event call. The "Playing" state has a "stop" >event but calling this will not help as it will not be processed until >the MSM has reached "Song3". The problem is that a state machine is based on run-to-completion. This means in your case that a transition must be "short". An event comes, a transition is executed, the state machine is in a new stable state and can process a new event. Until this happens, events are queued (in the case of MSM). >I start the same p.process_event(play()); in thread 1. And in thread 2 I >call p.process_event(stop()); The problem with this is that the stop() >event does not get processed until it reaches Song3 because of the >blocking call in p.process_event(play());. Actually I'd think because of the mutex. In any case, your design will be hard to get right I'm afraid. >Perhaps I am going about this the wrong here and please tell me if it >can be done in some other much better way! I want to be able to have >automatic transitions that I can interrupt. You have to use run-to-completion. Base your design on short-terms events fed to the state machine, which triggers work and reacts to changes in forms of other events. In your case, one possibility would be to have the state machine delegate (post) some work upon state entry or transition action to a thread, then posting a new task upon state exit, etc. Make your state machine be serviced by only one thread, triggering work and reacting to events. Trust me on that one, having a state machine serviced by 2 threads is a good receipt for headaches ;-) If you know boost::asio, it's a bit like the async_xxx methods, trigger some work and get ready for the next action (which would be a callback, to continue with this asio example). HTH, Christophe

2 1

[preprocessor] seq/size.hpp BOOST_PP_SEQ_SIZE MSVC empty list warning
by damien benoist 19 Apr '11

19 Apr '11

Hello, It seems that BOOST_PP_SEQ_SIZE generates a warning with empty sequences under MSVC (vs 2010/boost 1.46.1). The same call works with gcc. The tests are available below. I've also put a patch but: - I'm really not sure of it (I have never been as far with preproceesor as in boost/preprocesor/) - I only tested it with BOOST_PP_CONFIG_MSVC (it should also be tested with BOOST_PP_CONFIG_EDG) And anyway this warning will likely appear with all macros manipulating sequences. Should this warning just be ignored or disabled with MSVC? More general question: I'm discovering boost. I'm really impressed by the macros in boost/preprocessor. It makes a lot of things possible. But it provides features the preprocessor was not meant for. For that, it uses a lot of tricks. How portable is it? How many architectures is it known to work/not work with? Can we be confident that it should work with any preprocessor? Thanks for your help. $ cat lstsz2.h #include "boost/preprocessor/seq/size.hpp" #define lst0 #define lst1 (a) #define lst2 (a)(b) #define lst3 (a)(b)(c) BOOST_PP_SEQ_SIZE(lst0) BOOST_PP_SEQ_SIZE(lst1) BOOST_PP_SEQ_SIZE(lst2) BOOST_PP_SEQ_SIZE(lst3) $ cpp -I ~/wh/softs/boost/1.46.1 < lstsz2.h ... 0 1 2 3 $ cl -I `cygpath -d "$HOME/wh/softs/boost/1.46.1"` /E lstsz2.h ... 0 1 2 3 lstsz2.h(8) : warning C4003: not enough actual parameters for macro 'BOOST_PP_SEQ_SIZE_I' $ diff -u 1.46.1/boost/preprocessor/seq/size.hpp.old 1.46.1/boost/preprocessor/seq/size.hpp --- 1.46.1/boost/preprocessor/seq/size.hpp.old 2005-06-21 09:55:15.000000000 +0200 +++ 1.46.1/boost/preprocessor/seq/size.hpp 2011-04-19 14:42:02.218750000 +0200 @@ -13,6 +13,7 @@ # define BOOST_PREPROCESSOR_SEQ_SIZE_HPP # # include <boost/preprocessor/cat.hpp> +# include <boost/preprocessor/empty.hpp> # include <boost/preprocessor/config/config.hpp> # include <boost/preprocessor/tuple/eat.hpp> # @@ -21,7 +22,7 @@ # define BOOST_PP_SEQ_SIZE_I(par) BOOST_PP_SEQ_SIZE_II ## par # define BOOST_PP_SEQ_SIZE_II(seq) BOOST_PP_CAT(BOOST_PP_SEQ_SIZE_, BOOST_PP_SEQ_SIZE_0 ## seq) # elif BOOST_PP_CONFIG_FLAGS() & BOOST_PP_CONFIG_EDG() || BOOST_PP_CONFIG_FLAGS() & BOOST_PP_CONFIG_MSVC() -# define BOOST_PP_SEQ_SIZE(seq) BOOST_PP_SEQ_SIZE_I(seq) +# define BOOST_PP_SEQ_SIZE(seq) BOOST_PP_SEQ_SIZE_I(seq BOOST_PP_EMPTY()) # define BOOST_PP_SEQ_SIZE_I(seq) BOOST_PP_CAT(BOOST_PP_SEQ_SIZE_, BOOST_PP_SEQ_SIZE_0 seq) # elif defined(__IBMC__) || defined(__IBMCPP__) # define BOOST_PP_SEQ_SIZE(seq) BOOST_PP_CAT(BOOST_PP_SEQ_SIZE_, BOOST_PP_CAT(BOOST_PP_SEQ_SIZE_0, seq))

2 1

[TypeTraits] Are any of the new C++2011 traits implementable using SFINAE expressions?
by John Maddock 19 Apr '11

19 Apr '11

I'm quite sure the answer to this is no.... but are there any new language features in C++2011 that would allow the implementation of any of the following traits within the language? Thanks in advance, John. template <class T> struct is_trivial template <class T> struct is_trivially_copyable template <class T> struct is_standard_layout template <class T> struct is_literal_type template <class T, class... Args> struct is_constructible; template <class T> struct is_default_constructible; template <class T> struct is_copy_constructible; template <class T> struct is_move_constructible; template <class T, class U> struct is_assignable; template <class T> struct is_copy_assignable; template <class T> struct is_move_assignable; template <class T> struct is_destructible; template <class T, class... Args> struct is_trivially_constructible; template <class T> struct is_trivially_default_constructible; template <class T> struct is_trivially_copy_constructible; template <class T> struct is_trivially_move_constructible; template <class T, class U> struct is_trivially_assignable; template <class T> struct is_trivially_copy_assignable; template <class T> struct is_trivially_move_assignable; template <class T> struct is_trivially_destructible; template <class T, class... Args> struct is_nothrow_constructible; template <class T> struct is_nothrow_default_constructible; template <class T> struct is_nothrow_copy_constructible; template <class T> struct is_nothrow_move_constructible; template <class T, class U> struct is_nothrow_assignable; template <class T> struct is_nothrow_copy_assignable; template <class T> struct is_nothrow_move_assignable; template <class T> struct is_nothrow_destructible; template <class T> struct underlying_type;

2 1

Re: [boost] [Filesystem] error including filesystem v3 with icpc -std=c++0x
by Galen Andrew 19 Apr '11

19 Apr '11

> > Hello, > > > > Including boost/filesystem.hpp is giving me errors using Intel > > compiler in Linux with -std=c++0x that look like > > > > > boost/filesystem/v3/operations.hpp(303): error: name followed by "::" > > must be a class or namespace name > > {detail::copy_file(from, to, > > copy_option::fail_if_exists);} > > ^ > > It compiles fine under g++ -std=c++0x. > > What happens with the Intel compiler if you don't specify -std=c++0x? Without -std=c++0x those errors are gone, but a similar error pops up in another boost library I'm using boost/random/variate_generator.hpp(209): error: name followed by "::" must be a class or namespace name typedef typename random::detail::engine_helper<have_int, want_int>::BOOST_NESTED_TEMPLATE impl<decorated_engine, typename Distribution::input_type>::type internal_engine_type; ^ > The regression tests are passing for Intel on Linux, but it doesn't > look like any of them specify -std=c++0x > > What version of the Intel compiler are you using? Version 12.0.2.137 Build 20110112 > > What version of Boost are you using? 1.46.1 Thanks!

1 0

[network] Release 0.9.0
by Dean Michael Berris 19 Apr '11

19 Apr '11

Good day everyone, apologies for the cross-post. I just wanted to point everyone interested in the development of the cpp-netlib project to the 0.9.0 release announcement over at C++ Soup: http://cplusplus-soup.com/2011/04/18/cpp-netlib-0-9-0-released/ -- more information about what happened in the library between the beta and the official release can be found there. As earlier mentioned, this version is the pre-1.0 snapshot that is being officially submitted to the Boost C++ Library as Boost.Network. I would like to ask the review wizards to please accept this announcement as a request to put Boost.Network/cpp-netlib into the review queue pending a review manager. I would greatly appreciate volunteers who would like to be the review manager(s) for the Boost.Network review. Have a good one and I definitely hope this helps. Cheers from down under! -- Dean Michael Berris http://about.me/deanberris

2 1

[gsoc] Review needed --- BGL extension : community detection algorithm
by Xu Sun 19 Apr '11

19 Apr '11

Hi, Thanks for Robert's advise. I've posted my proposal on 04/05 but still didn't receive any reply including email or comment. I will be very appreciated if any one can give me any feedback about my proposal. The link is here: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/sunbow/1 And the abstract: Implement new library based on Blondel's method and Newman's method providing community detection functionality into Boost libraries. Through this library, users can get their input direct/indirect weighted/unweighted graph segmented based on the criterion that the nodes within the same community have a more significant relationship than those between different communities. Sorry to bother others. Thanks, Xu Sun

3 2

[OT] Boost Users/Developers Down Under?
by Dean Michael Berris 19 Apr '11

19 Apr '11

Hey Everyone! Apologies for the cross post and off-topic, but I just moved to Sydney, Australia and I was wondering whether there are any Boost users/developers that are based here who'd like to get together for a geek out session somewhere in the city? I tried to look at the Boost Users Map (http://goo.gl/O1I15) and I only saw one other Boost user in the area -- maybe there are others lurking around who'd be interested in a meet-up here? :) Cheers from down under! :D -- Dean Michael Berris http://about.me/deanberris

1 0

FW: [locale] Off-list review
by steve.bush＠neosys.com 19 Apr '11

19 Apr '11

-----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Vicente BOTET Sent: 19 April 2011 10:33 >Hi, I have the impression that this review has already been sent at Date: Sat, 16 Apr 2011 15:40:53 +0400 . >BTW, who sent it? I did. I am sorry for wasting everybody's time. I joined the list immediately afterwards and have followed the very lively discussion intently since then. Artyom is quite resolute in the defence of his design decisions some of which brutally practical compromises - even if theoretically ugly. Things like broken standard libraries and "Broken" csv just aren't going to be fixed. This particular library has to live in the real world of existing libraries, not a vacuum, so the exquisite design purity which is so much a part of many boost libraries is less a consideration here. One of the strengths of the library seems to be that Artyom has used it in production for some years, although apparently mainly in posix/utf-8 environment and without CJK. I seriously doubt there will be any better offer for internationalisation library than this and it may trigger a better solution later on. If that is the case then this review better try to identify any unacceptable features in the library - especially those that cannot be replaced in future versions. If there are few or none then I think it should be admitted. Steve Bush

1 0

[locale] Off-list review
by Chad Nelson 19 Apr '11

19 Apr '11

This review was sent to me privately, rather than to the list. I don't think I realized that when I received it. Apologies if I had forwarded it earlier too. -- Chad Nelson Oak Circle Software, Inc. * * * Begin forwarded message: Date: Sat, 16 Apr 2011 15:40:53 +0400 From: <steve.bush(a)neosys.com> --- What is your evaluation of the design? Very good to start with since leveraging locale for i18n/l10n is a great rallying point for developers. Translate GETTEXT might be better in a separate library to increase degrees of freedom and reduce coupling. --- What is your evaluation of the implementation? The wrapper/backend strategy provides immediate benefit while leaving the door open to progressive reimplementation. Since it is a wrapper, could PARTS of it be implemented as a header only? --- What is your evaluation of the documentation? The documentation is more than good enough to start with considering this library's potential usefulness. --- What is your evaluation of the potential usefulness of the library? This library is potentially *extremely* useful because it LEVERAGES an important chunk of standard C++ that is sadly underutilised merely due to a few design and implementation flaws. This library has potential something of the order of Boost.FileSystem. This is a VERY strategic library and any shortcomings will be resolved with time. --- Did you try to use the library? With what compiler? Did you have any problems? Didn't try. --- How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I meticulously read all documentation several times. --- Are you knowledgeable about the problem domain? Yes, we have used similar technique for Exodus http://devwiki.neosys.com and will replace those with Boost.Locale if and when it becomes available. --- Do you think the library should be accepted as a Boost library? YES - It is relatively small but has a massive effect. It has a very low cost/benefit ratio since it leverages long standing classic C++ locale design/skills.

3 3

[locale] review
by Phil Endecott 19 Apr '11

19 Apr '11

Dear All, Here is a brief review of the proposed Boost.Locale library. I know little about the internationalisation issues that this library addresses, so I will focus just on the few areas where I do have some experience. The documentation is generally of good quality but could be expanded in places as noted below. I appreciate the introduction of std::locale at the beginning; having avoided std::locale for precisely the "common critical problems" mentioned, this introduction was useful. As others have said, a similar introduction to icu, perhaps even deep links to appropriate parts of its documentation, and perhaps also to Unicode docs would be useful. I found that it was not sufficiently easy to find which header each function is in, e.g. on the charset_handling.html page the name of the header is not mentioned; if I click on e.g. from_utf I get to a reference page that also doesn't name the header. Use of strings rather than symbols: there are a few places where the library uses strings such as "UTF-8" or "de_DE.UTF8" rather than symbols like utf_8 or de_DE_UTF8. This use of strings can make things run-time errors that could otherwise be compile-time errors. Mis-typing e.g. "UTF_8" or "de-DE" is too easy. Perhasp in some cases the domain of the parameter is not known at compile time, but even in those cases, it should be possible to provide symbols for the most common choices. Collation: I would be interested to know how fast these comparisons are compared to regular std::string::operator<. If I correctly understand what transform does (more docs needed), it would be interesting to then compare the performance of std::map<...,comparator> with a std::map<> storing transformed strings. Or similarly, to compare std::sort using the comparator with std::sort of a pair<transformed string, original string>. Ideally these collation functions would take character ranges of arbitrary types, however I guess that the icu API takes char* making this unreasonable. Apparently there is no option for a NULL-terminated char*, unlike the case conversion functions, right? Case conversions: I don't know what "title case" is or what "fold case" means; the docs should define this. At least linking to the definitions of the Unicode normalisation forms would also be useful; preferably, some explanation of how they should be used would be included. I can think of two recent case-conversion problems that I have had, both related to geographic names: 1. I had a list of North American names, in "UPPER CASE". I decided to convert them to "Initial Capitals" for better appearance, but later realised that this was broken for accented names in Quebec. I could imagine some sort of "case conversion is lossy" property of a locale that would detect this; does anything like that exist? (I guess not.) 2. In a similar case I found that " 's " was being wrongly capitalised, e.g. "St. John'S Street". (This was with PostgreSQL's case conversion functions.) Again it would be useful to know whether (a) does the library try to handle this sort of thing correctly, and (b) can it tell me whether the operation that I want to do is lossy or not? For example, say I have a set of place names that are a mixture of en_US and en_CA and fr_CA but I don't know which; can I perform a conversion that works because those locales all have the same rules for e.g. ' and -? (I guess not.) Character set conversion: I think it's great that Boost might finally get character set conversion - it's overdue! However, I'm not enthusiastic about this: std::string utf8_string = to_utf<char>(latin1_string,"Latin1"); 1. It should be possible for the source character set to be a compile-time constant symbol, and a template parameter e.g. conv<latin1,utf8>(str). As it is, if I want to convert just a few bytes, it will surely spend more time decoding the charset name string than actually converting. 2. As above, ideally it should take a range of arbitrary type and output to a back_insert_iterator; presumably this is an icu limitation. 3. The error handling seems to be basic - it's "all or nothing". Considering from_utf, since this is the direction where there are more things that can be unrepresentable, I might want to: - Skip the character; - Replace with '?'; - Replace with an unaccented version, or e.g. curly-quotes to plain-quotes; - Throw an exception that aborts the whole operation; - Do the conversion up to the point of difficulty and then indicate the problem. 4. There's also the case where the input is chunked, and the chunk-breaks might fall within multi-byte characters; so individual chunks are potentially malformed while the overall stream is OK. I think the best way to handle this is with a stateful functor to do the comparison; I wrote one using iconv, like this: Iconver<latin1,utf8> latin1_to_utf8; while (!end_of_input()) { output.append( latin1_to_utf8(input.get_chunk()) ); } assert(latin1_to_utf8.empty()); // detect unconverted partial chars at end of input Also: how is the performance of this conversion? If it is being done by icu, we should have a hook (i.e. specialisation, hence my suggestion of template parameters for the character sets) so that we can provide optimised versions of important conversions. Here are my answers to the "normal questions": - What is your evaluation of the design? Generally it seems like a reasonable design for an icu wrapper. If it were not an icu wrapper, no doubt some things could be done better. - What is your evaluation of the implementation? I've looked at very little of the source. I decided to look at iconv_codepage.hpp since I have some experience with iconv. I note that a union is being used in what I believe is an undefined way: union { char first; uint16_t u16; uint32_t u32; } v; v.u16 = 1; if(v.first == 1) { return "UTF-16LE"; } else { return "UTF-16BE"; } In my own iconv wrapper code I need a const_cast because the POSIX spec misses a const on the second argument to iconv(); some platforms correct this, but not all: #if defined(__FreeBSD__) || defined(__OpenBSD__) || defined(__NetBSD__) || defined(__sun__) // Previously __APPLE__ was included in this list; presumably they have // changed their headers. If you have an older system you may need to put // it back. #define ICONV_ARG2_IS_CONST #endif This doesn't seem to be done here. There seems to be some use of reinterpret_cast which I think should be a static_cast via void*: virtual std::string convert(char_type const *ubegin,char_type const *uend) { .... char const *begin = reinterpret_cast<char const *>(ubegin); "int err" should probably be "errno_t err". There seems to be a "magic constant" of 10 to allow for the difference in size between the input and the output. Some comments would help. For example, to describe the meaning of the return values and error codes from iconv(). Based on that limited look, my view is that the code probably works, but it could be improved in many ways. - What is your evaluation of the documentation? Good enough. - What is your evaluation of the potential usefulness of the library? Useful and overdue. - Did you try to use the library? With what compiler? Did you have any problems? No, I've not compiled anything. - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? 3 hours reading the docs and looking at a tiny bit of the implementation. - Are you knowledgeable about the problem domain? Not beyond the areas that I have discussed above. > Please explicitly state in your review whether the library should be > accepted. It's borderline. I was going to say "yes, but please consider updating at least the charset conversion functions in the way that I proposed". But then I looked at the source and noted what I think are well-known issues like abuse of union and reinterpret_cast, which have lowered my opinion a bit. And then I've seen some other reviews that have looked at the areas I've not considered (i.e. message translation) and they have been quite critical. Based on all of that, my view has shifted to "no, but this is worthwhile functionality, so please come back when you've resolved some of these concerns". Regards, Phil.

4 9

[locale] Strange(?) result in example code
by Noah Roberts 19 Apr '11

19 Apr '11

#include <boost/locale.hpp> #include <iostream> //#include <ctime> using namespace boost::locale; int main() { generator gen; //std::locale::global(gen("snthsnth")); // no exception std::locale::global(gen("en_US.UTF-8")); double now = time(0); std::cout << "Today is " << as::date << now << std::endl << "Current time is " << as::time << now << std::endl << "The current weekday is " << as::ftime("%A") << now << std::endl; std::cin.get(); } http://cppcms.sourceforge.net/boost_locale/html/formatting_and_parsing.html I get warnings about converting from time_t to double (which I rather expected) and then get basic, double formatted output: Today is 1.3029e+009 Current time is 1.3029e+009 The current weekday is 1.3029e+009

5 14

[locale] Review
by Noah Roberts 19 Apr '11

19 Apr '11

- What is your evaluation of the design? Functions. Seems straight forward to use. - What is your evaluation of the implementation? What I used worked. I did not look over the source. - What is your evaluation of the documentation? Good except that there are at least some errors/inconsistencies (ngettext in messages_formatting.html for example is missing an argument). Also need to be explicit about which version of 3rd party programs are required (see below). - What is your evaluation of the potential usefulness of the library? I'll probably be using it for our product (assuming it plays fine with Qt, which I don't see any reason why not) so I'd say very. - Did you try to use the library? With what compiler? Did you have any problems? Yes. MSVC2010. No problems specific to the library but did have a pretty hard time figuring out which version of gettext was necessary and finding it. Simple search for gettext win32 or windows does not turn up a version compatible with this library (--keyword=translate:1,1t syntax invalid). Had to get the recent MSYS developer toolkit (mingw + msys wasn't even enough). After a couple of hours of searching it seemed to be the only option. - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I wrote a simple program and played with a few of the functions. I downloaded and installed various tools that are supposed to help with translating. Basically did a short, 4 hour evaluation of whether I could propose it for use. - Are you knowledgeable about the problem domain? Not as much as I certainly should be. - Should it be in boost? I have some concerns about the fact that it relies so much on 3rd party stuff. The gettext tools are obviously moving targets and not having an easily accessible version of xgettext for Visual Studio users is not an optimal situation. Having to install MinGW and the works shouldn't be required. Various supposed binary downloads of gettext for win32 either are not or are too old. I also found that of the tools listed for working on po files, only one both worked with plural forms and worked on win32. In fact possibly only the one worked with plural forms at all. The fact that this library implements a gettext like setup is nice, but the dependency then upon gettext to provide the source extraction tools and such is unfortunate and could certainly lead to problems where there are version conflicts. Based on my experience I'd say that clearly there are some availability issues in this area for those using Visual Studio. Since gettext is someone else's problem, I don't see how boost can safely make sure the necessary programs are available to anyone using boost. Certainly some better documentation about which version of gettext is being emulated should be included (I looked through the docs and never saw anything specifying version). Once I did find the correct version of the tools (or at least a version that responded as the documentation explained) the system seemed to work out just fine. I would like to see an alternative to a complete msys install (though I personally like to have it around, others on my team find it useless). I would guess that there should be one but I seriously couldn't find it. I would also like to see boost::locale::format work like boost::format. The documentation also calls this thing a printf like utility class but it doesn't, as opposed to boost::format, accept printf format strings. On the other hand, boost::format(translate("%.4g")) % 3.14 worked just fine so I don't know what this locale specific version is providing. All that said, I think it could be a good addition. We certainly need something like it and it at least does what I think I need from such a library.

4 13

[type_traits] Plans to add C++11 type traits?
by Beman Dawes 19 Apr '11

19 Apr '11

Now that C++11 (formerly C++0x) is done, are there any plans to add the type traits to Boost that we don't already have? See http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3290.pdf --Beman

4 4

[locale] Review: Tutorial
by Gevorg Voskanyan 19 Apr '11

19 Apr '11

index.html: "Correct case conversion, case folding and normalization." Please insert a link to a resource explaining the difference between case conversion and case folding. std_locales.html: In the first code snippet "std::use_facet<std::ctype>(some_locale)" is wrong. Should be: std::use_facet<std::ctype<char> >(some_locale) "imbued into an iostream" doesn't look OK, especially with 'iostream' in fixed-width font. "imbued into an I/O stream object" perhaps. Such usage of 'iostream' is present on most other pages as well. A link near the "cout.imbue(std::locale("en_US.UTF-8")); ..." example to the "Locale names are not standardized. ..." paragraph would help. Would be good to mention std::has_facet. What is paper_size::inches? I guess it should be measure::inches. The comment below needs to be corrected too. class measure is missing the static std::locale::id id; member print_distance example should use the 'out' object instead of std::cout. "// Set default locale as global" This comment is misleading. The default locale in C++ programs is the 'classic' locale. std::locale("") is the user's preferred locale. Or perhaps we can use the system's default locale term, but I think "user's preferred" is better. formatting_and_parsing.html: Strictly speaking, "the iostream STL library" is not correct formulation. Should be e.g. "the standard I/O streams". why "double now=time(0);" and not "time_t now=time(0);" ? s/tommorrow/tomorrow/ s/display in local time format/display in local time zone/ s/as::locale_time/as::local_time/ s/Locale time is/Local time is/ conversions.html: Add code example calling to_lower and fold_case on "grüßen" to help users understand the difference between the two. messages_formatting.html: s/Is change to/Is changed to/ Is there a default search path for dictionaries (/usr/share/locale under *nix), or should an application always call add_messages_path() ? "The source text is not copied." Sometimes 'not' is highlighted, and sometimes 'is'. So what does it try to say after all? That the provided string argument must not die before the translated string is fetched? s/tanslate/translate/ s/Japaneese/Japanese/ ja << msg missing semicolon s/main()/int main()/ std::wstring msg = translate("Do you want to open the file?").str<wchar_t>(some_locale) missing semicolon s/GNU Gettext catalogs has/GNU Gettext catalogs have/ "is \c n 1 or not" looks like a doxygen formatting problem. Such problems exist in some other places as well. s/Occured/Occurred/ s/managment/management/ "Is there any reason to prefer the Boost.Locale implementation to the original GNU Gettext runtime library? In either case I would probably need some of the GNU tools." Maybe add a c. point about license charset_handling.html: s/does not provides/does not provide/ localized_text_formatting.html: s/when we create a messages/when we create messages/ localized_text_formatting.html: wcout << wformat(L"Today {1,date} I would meet {2} at home") % time(0) % name <<endl missing semicolon int a_and_b = a+b; please change to int a_plus_b = a+b; dates_times_timezones.html: s/they fully aware/they are fully aware/ Or rather, what does 'they' refer to here? s/than setting "current day of week"/then setting "current day of week"/ add << between some_point and " is the " s/We recommended you look/We recommend you to look/ And what date-time range does the ICU backend support? I'd like to echo other reviewers that printing date/time should not print a number by default. s/alway/always/ s/and over that build dates/and over that builds dates/ working_with_multiple_locales.html: s/get.locale_cache_enabled(true);/gen.locale_cache_enabled(true);/ s/std::locale ar=get("ar_EG.UTF-8");/std::locale ar=gen("ar_EG.UTF-8");/ s/as parameters in various functions/as parameters to various functions/ using_localization_backends.html: s/Case handing/Case handling/ recommendations_and_myths.html: s/it probably the most/it is probably the most/ s/and may other applications/and many other applications/ building_boost_locale.html: s/If your icu build in placed/If your icu build is placed/ s/if you relay on auto-linking/if you rely on auto-linking/ appendix.html: "is depend" substitute with "is dependent" or "depends" s/not bring read performance advantage/not bring real performance advantage/ s/would work only of standard facets/would work only if standard facets/ s/Boost locale fully supports/Boost Locale fully supports/ s/may broke/may break/ s/tje/the/ "including all Western, Cyrillic, Hebrew, Thai, Arabic and CJK encodings." Shouldn't be "characters"? s/std::sting/std::string/ s/not indented to be used in production/not intended to be used in production/ General remarks: Usage of comments in code snippets is inconsistent in the sense that sometimes the comment comes after the code is addresses, the other times it comes before. One of those styles should be used all over the place - preferably comments coming first as that is the common practice in other Boost libraries. Would like to see examples of using Boost.Locale facets directly. Would like to see examples of user-defined I/O inserters/extractors that respect the current state of Boost.Locale formatting as altered by manipulators. E.g. a "class money" example which uses the Boost.Locale currency formatting info for its I/O, or a "class bigint" example which uses the Boost.Locale number formatting info for its I/O. Bonus points if they fallback to std facets if corresponding Boost.Locale info is missing from the stream! Thanks, Gevorg

2 4

[locale] Formal review of Boost.Locale library starts tomorrow
by Chad Nelson 19 Apr '11

19 Apr '11

The formal review of the Boost.Locale library by Artyom Beilis starts tomorrow, April 7th, and is scheduled to last through April 16th. *************** * Its Purpose * *************** Boost.Locale provides thorough localization features to C++ programs by way of std::locale facets. Excerpted from the introduction: C++ offers a very good base for localization via the existing C++ locale facets [...] But these are very limited and sometimes buggy by design. Support for localization varies [...], and there are frequently incompatibilities between them. On the other hand, there is a great, well debugged, high quality, widely used ICU library that gives all of the goodies. But it has a very dated API that mimics Java behavior, completely ignores the STL, and provides a useful API only for UTF-16 encoded text, ignoring other popular Unicode encodings like UTF-8 and UTF-32 and limited but still popular national character sets like Latin1. Boost.Locale provides the natural glue between the C++ locales framework, iostreams, and the powerful ICU library. Although it can use the ICU library, it supports several other processing options as well. ******************* * Where to get it * ******************* You can find the "boost_locale_for_review" version here: https://sourceforge.net/projects/cppcms/files/boost_locale/ The HTML documentation can also be seen at: http://cppcms.sourceforge.net/boost_locale/html/index.html ******************** * Writing a review * ******************** The reviews and all comments should be submitted to the developers list, and the email should have "[locale]" at the beginning of the subject line to make sure it's not missed. Please explicitly state in your review whether the library should be accepted. The general review checklist: - 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? -- Chad Nelson Oak Circle Software, Inc. * * *

17 82

[Filesystem] error including filesystem v3 with icpc -std=c++0x
by Galen Andrew 19 Apr '11

19 Apr '11

Hello, Including boost/filesystem.hpp is giving me errors using Intel compiler in Linux with -std=c++0x that look like boost/filesystem/v3/operations.hpp(303): error: name followed by "::" must be a class or namespace name {detail::copy_file(from, to, copy_option::fail_if_exists);} ^ It compiles fine under g++ -std=c++0x. There are also a plethora of warnings like boost/filesystem/v3/operations.hpp(626): warning #279: controlling expression is constant BOOST_ASSERT(m_imp.get() && "attempt to dereference end iterator"); ^ I'd appreciate any help/ideas. Thanks, Galen

2 1

[locale] Review of Boost.Locale library
by Edward Diener 18 Apr '11

18 Apr '11

This is my review of the Boost Locale library. It is divided into two parts, a review of the documentation and a review of the library itself. I will refer to Boost Locale as just Locale, with a capital L, for the remainder of this review. I will use the term C++ locale to refer to the C++ standard library locale implementation. 1. Documentation The layout of the main page is decent, but I would have expected a discussion there, or as a first topic, of what Locale brings that the C++ standard locale does not have. I was disappointed not to find such a discussion. The documentation topics are specified as Tutorials. I do not think they are Tutorials, which is fine with me since I much prefer topics rather than exmaples when trying to understand a library. a. Introduction to C++ Standard Library localization support The common critical problems of the C++ locale portion of the standard library seems spurious to me. The problems mentioned are really about implementations or programmer usage, not the C++ locale library itself. The only valid problem mentioned I find there is that the C++ standard library did not attempt to standardize any locale names. This makes using C++ locales based on locale names non-portable. Unfortunately the issues there make a very weak argument for the Locale library itself. b. Locale generation I would have liked it if the doc here specified where one finds valid lists of language, country, encoding, and variant which make up a locale name. Without this information, the one valid problem mentioned regarding C++ locale is also a problem with Locale. The note about wide strings and 8-bit encoding makes no sense to me at all. If I am using a wide string encoding, why would I not be using wide string iostreams ? c. Collation There is no explanation about what 'collation' is about. This is very disappointing, as it makes the rest of the discussion difficult to follow. The examples were worthless to me since the classes involved have not been mentioned or discussed. Also the examples are woefully incomplete even in what they represent. This is one reason why I dislike documentation which attempts to teach by example. It always seems to assume that if it throws examples at the reader before anything about the classes/templates in the examples have been mentioned, that this is somehow an effective way of learning a library. Instead it just creates confusion and serves unfortunately as a way by which a library implementer does not have to explain how the classes in his library actually work or relate to each other. d. Conversions "You may notice that there are existing functions to_upper and to_lower in the Boost.StringAlgo library. The difference is that these function operate over an entire string instead of performing incorrect character-by-character conversions." In he second sentence, "these function" gramatically refers to the functions in Boost.StringAlgo, but I doubt that is what is meant. I do not understand how these conversion functions use a locale. The example gives: boost::locale::to_upper(gruben) used in a stream. Is this function using the locale imbued in the iostream ? Again this is what happens when one creates examples without first explaining topics in a rational and orderly way. e. Numbers, Time and Currency formatting and parsing A bunch of ICU flags are mentioned but with no indication about how these are supposed to be used by iostreams. These flags look like they are supposed to be used by C-like format printf statements but since Locale uses iostreams I can not understand their purpose with Locale. f. Messages Formatting (Translation) Gnu gettext should be explained when it interfaces with Locale. Just telling someone to learn Gnu gettext is not adequate. Other than that the explanation is pretty thorough. g. Character Set Conversions An explanation of what character sets are, and what character set conversions entail, should be the beginning of this documentation. h. Localized Text Formatting "Each format specifier is enclosed within {} brackets.." These are not "brackets" but "braces". Brackets are '[]'. i. In general It is confusing to me how generated locales affect the functionality of the different sections presented under 'Using Boost.Locale'. In a number of situations I am looking at classes or functions and I have no idea how these pick up a locale. I do understand that when used with iostreams the locale is determined by the locale imbued in the iostream. But outside of iostreams I do not understand from the documentation what locale is being used. If it is the C++ global locale, the documentation should say so. This entire issue about how locales are actually being used in various parts of the library should be explained as part of an overall explanation of the library. I find this good overall explanation of the library the major flaw in the documentation. The documentation itself is well-ordered and the explanations generally decent. But I find it next to impossible to understand a library when the documentation does not take the time to explain concepts/topics and instead substititutes exmaples as a means of understaning a library. 2. Library itself I did not look at the code itself and have no interest in critiquing the source. Others do this much better than I ever can. The library offers a great deal of functionality and a great positive of the library is that it works with multiple backends and brings those backends into the C++ world. In general I think that using the global locale is a bad programming practice when one specifically intends to work with locales. Unfortunately it was hard for me to understand how individual locales are used with each of the parts of the library from the documentation. But I will assume for the time being, because it seems the only correct design, that each part of the library which is documented can work with some non-global locale which is created and passed around as necessary. The only design flaw which I could discover in the library was in message translation. The fact that translation always begin from English ( or perhaps some other narrow character language ) to something else is horrendous. I can understand that the Locale implementer wanted to use something popular and that already exists, but an idea so tremendously flawed in its conception either needs to be changed, if possible, or discarded for something better. I do understand that translation is just one part of this large library, but I hope that the implementer undestands how ridiculous it is to assume that non-English programmers are going to be willing to translate from English to language X rather than from their own language to language X. I am assuming that all other parts of the library support both narrow character encodings and wide character encodings fully, and that at least UTF-16 is always supported using wide characters. It was really hard for me to make out from the docs whether or not this was the case. I believe a great deal of work was put into the library, and that this work is invaluable in bringing locale usage into C++ in a better way than it is currently supported in C++ locale. But I would have to vote "No" that the library should be accepted into Boost at the current time, with some provisos which would most likely gain my own change to a "Yes" vote in the future. 1) The documentation should explain the differences and improvements of Locale over C++ locale in a good general way. 2) The documentation should explain the use of locales for each of the topics. 3) A number of topics should discuss what they are about in general, and more time should be given to discuss how the classes/templates relate to each other. 4) Message translation should be reconsidered. I don't mean to say that the way it is done is enough to have the library rejected, but I can not believe that it is not a flawed system no matter what the popularity of Gnu gettext might be. My major trouble with the library, which has led to my "No" vote, is that I can not really understand how to use the library from the documentation or what the library really offers over and above C++ locales. I realize the library programmer may not himself be a native English speaker, but if I can not really understand a library from its documentation in a way that makes sense to me I can not vote for its inclusion into Boost. I strongly suspect that if I were to understand the functionality of the library through a more rigorous explanation of its topics, and each topics relationship to a locale class and various encodings, I mught well vote for its inclusion into Boost. But for now, and in the state which the documentation resides for me, I can not do so. So I hope this review will be undersstood at least partially as a request to improve the docs as much as anything else.

6 10

[locale] Review. Internationalization library?
by Vicente BOTET 18 Apr '11

18 Apr '11

Hi, from the name of the library Boost.Locale and the section "What is Boost.Locale?" I didn't get enough information about the motivation and the scope of the library. I think that maybe be this is due to the fact that the dependency to ICU hides a lot of features the library provides. I think that a direct link to what ICU is is a must, but I would expect a little bit more than "On the other hand, there is a great, well debugged, high quality, widely used ICU library that gives all of the goodies" in this section. >From my side if the library was named Boost.Internationalization I'm sure I would had take a look long time ago. Do you think that this renaming (or a shorter one) will cover the whole library or there are parts of the library that don't fall in the internationalization domain? As the review period has been extended, I will try to review at least the documentation. Best, Vicente

3 17

Would a construct_cast<T>(u..) be useful?
by Johannes Schaub (litb) 17 Apr '11

17 Apr '11

I was wondering whether it makes sense to have another kind of cast in boost, which behaves like the following: template<typename T, typename ...U> T construct_cast(U &&... u) { T t(std::forward<U>(u)...); return t; } This cast works if std::is_constructible<T, U...>::value is true, and fails if it is false. It presents a slightly more explicit form of boost::implicit_cast<T> in that explicit constructors of T are allowed, and for the case of a single- elemented parameter pack, explicit conversion functions of U converting to "T" are allowed. It does not allow non-implicit conversions like void* -> nonvoid*, Base* -> Derived*. Advantages over not having construct_cast: - Converting expressions to "bool" by use of "contextually converted to bool", without using things like "!!x" or "x ? true : false" (the first may trigger user defined opeators for "operator!", which may not be desired). - No need for introducing a temporary named variable like the above "t". - If all you want is to consider contexual conversions, explicit constructors and conversion functions, this can be used. All these conversion seem "safe", compared to the set of conversions allowed by T(u) and even static_cast<T>(u). What do you think about it?

2 1

BGL
by Sultana Rashid 17 Apr '11

17 Apr '11

Hi all, I have submitted two proposals to Boost.I am very interested in C++ works and algorithms,so I submitted only for Boost projects.I met an accident after proposal submission so that I could not refine my project ideas.Now I am well and have enough free time to interact with mentors and do the necessary works.My proposals can be found here: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/monowara… http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/monowara… Now I am writing something about one of my algorithms' prospective design. *Dinitz blocking max flow algorithm:* *Input:* Graph& g .A directed graph. The graph's type will be a model of VertexListGraph and IncidenceGraph. *Input:* *source node* which is a vertex. Its type will be graph's vertex descriptor type. *Input:* *sink node* ,its type will be same as source node. *Input:* capacity map(CapacityEdgeMap cap),the edge capacity property map. The type must be a model of a constant Lvalue Property Map. The key type of the map must be the graph's edge descriptor type. Default: get(edge_capacity, g) *Input:* reverse edge map(ReverseEdgeMap rev) An edge property map that maps every edge (u,v) in the graph to the reverse edge (v,u). The map must be a model of constant Lvalue Property Map. The key type of the map must be the graph's edge descriptor type. Default: get(edge_reverse, g) *Input:*residual capacity map(ResidualCapacityEdgeMap res) ,This maps edges to their residual capacity. The type must be a model of a mutable Lvalue Property Map. The key type of the map must be the graph's edge descriptor type. Default: get(edge_residual_capacity, g) At first the whole capacity will be the residual capacity,then after every phase of calculation it will act as output. *Input:* vertex index(VertexIndexMap index_map) Maps each vertex of the graph to a unique integer in the range [0, num_vertices(g)). The map must be a model of constant LvaluePropertyMap. The key type of the map must be the graph's vertex descriptor type. Default: get(vertex_index, g) *Output:*The total flow of the network,flow in every iteration and min cut. *** User will be able to use the algorithm in two ways, named parameter version and non-named parameter version.* *** In named parameter version,explicit inputs will be the graph,source and sink node.Other will be default params. * *** In non-named parameter version,all will be explicitly input. * * * I studied already implemented flow algorithms and took help.But I am in confusion about UTIL parameters.* * If I get help or advice ,I'll try my best to refine my ideas about implementation and design.I studied all the relevant algorithms and wish to write all after getting feedback.I am not sure what to write about algorithm design.Would I write details how input and output will work as how min cut will be got or how flow will be determined? Please give me some hints.Hope to get some help.If I am not suitable for GSoC,however I want to know and implement. Mariya

2 1

Proposal Complete
by Sitesh Shrivastava 17 Apr '11

17 Apr '11

Dear Andrew, First of all, I'd like to thanks for letting me complete the timeline and other missing details in the proposal. I have almost completed my proposal. Please have a review of it and do let me know in case modification is required. Proposal URL: http://socghop.appspot.com/gsoc/proposal/review/google/gsoc2011/sitz/3001 --Thanks & Regards, *Sitesh Shrivastava* Junior Undergraduate, BIT Mesra Phone: *+91-9470521313 *E-Mail: *siteshshrivastava(a)gmail.com *Home-Page: *https://sites.google.com/site/siteshshrivastava** *

1 0

[locale] Off-list review of Boost.Locale library
by Chad Nelson 17 Apr '11

17 Apr '11

Date: Sat, 16 Apr 2011 15:40:53 +0400 From: <steve.bush(a)neosys.com> --- What is your evaluation of the design? Very good to start with since leveraging locale for i18n/l10n is a great rallying point for developers. Translate GETTEXT might be better in a separate library to increase degrees of freedom and reduce coupling. --- What is your evaluation of the implementation? The wrapper/backend strategy provides immediate benefit while leaving the door open to progressive reimplementation. Since it is a wrapper, could PARTS of it be implemented as a header only? --- What is your evaluation of the documentation? The documentation is more than good enough to start with considering this library's potential usefulness. --- What is your evaluation of the potential usefulness of the library? This library is potentially *extremely* useful because it LEVERAGES an important chunk of standard C++ that is sadly underutilised merely due to a few design and implementation flaws. This library has potential something of the order of Boost.FileSystem. This is a VERY strategic library and any shortcomings will be resolved with time. --- Did you try to use the library? With what compiler? Did you have any problems? Didn't try. --- How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I meticulously read all documentation several times. --- Are you knowledgeable about the problem domain? Yes, we have used similar technique for Exodus http://devwiki.neosys.com and will replace those with Boost.Locale if and when it becomes available. --- Do you think the library should be accepted as a Boost library? YES - It is relatively small but has a massive effect. It has a very low cost/benefit ratio since it leverages long standing classic C++ locale design/skills.

3 2

doxygen limitations
by Vicente BOTET 17 Apr '11

17 Apr '11

Hi, I would like to comment some limitations I have found while trying to generate the reference manual from the code comments using doxygen. 1. C++0x explicit operators are not documented as explicit with a warning explicit operator underlying_type const&() const ^^^^ gives operator underlying_type const &() const; 2. ::type misplaced when inheriting from a metafunction template < typename Final, typename UT, typename MetaMixinSeq=boost::mpl::vector0<>, typename Base=base_opaque_type > class new_class : public linear_hierarchy::type { gives template, typename Base = base_opaque_type> class new_class : public linear_hierarchy::type< MetaMixinSeq, Final, Base > { // ^^^^ 3. The base type is missing if the class is not documented elsewhere. This applies to other classes defined in other libraries in Boost or the Stl, but also when we use parameterized inheritance. template struct inherited_from_underlying { template struct type : Base { // Parameterized inheritance }; }; gives template struct inherited_from_underlying { // member classes/structs/unions template struct type { }; }; 4. When the brief comment takes only one line the comment is included on the Synopsis and nothing on the description section //! the underlying type typedef UT underlying_type; generates typedef UT underlying_type; // the underlying type 5. The classes are sometimes implicitly prefixed with his namespace template < typename UT, typename Tag=void, typename Bool=bool, typename MetaMixinSeq=boost::mpl::vector0<>, typename Base=base_private_opaque_type > class private_opaque_type : public private_opaque_class< private_opaque_type, UT, Bool, MetaMixinSeq, Base> gives template, typename Base = base_private_opaque_type> class private_opaque_type : public boost::opaque::private_opaque_class< private_opaque_type< UT, Tag, Bool, MetaMixinSeq, Base >, UT, Bool, MetaMixinSeq, Base > Do you have a workaround to some of these issues? What about creating a specific doxygen limitations and workarounds wiki page? Is there a possibility that the generated html goes to a single reference html file? Best, Vicente P.S. You can see directly some real examples on the documentation of Boost.Opaque https://svn.boost.org/svn/boost/sandbox/opaque/libs/opaque/doc/html/index.h….

3 5

[locale] Review of the proposed Boost.Locale library
by Volker Lukas 17 Apr '11

17 Apr '11

Hello, this is my review of the Locale library proposed for inclusion in Boost. I vote to accept the proposed Boost.Locale as a Boost library. - What is your evaluation of the design? The library is nicely structured into individual components, as far as I can infer from the documentation and having a glance at some of the source files. I like that it is possible to use different backends, utilizing the large ICU library when available. - What is your evaluation of the implementation? I was having only a superficial look at some of the source files, so I can not comment much. What I have seen looks clean to me. While reading the source code I think I could benefit from even more code comments. There are a lot already, but on the other hand there exists for example a source file libs/locale/src/shared/mo_lambda.cpp apparently containing a whole state machine or something without any word how it is used. I also stumbled over an odd comment in file libs/locale/src/std/numeric.cpp in line 163: "// workaround common bug - substitute NBSP with ordinary space". As a reader who did not already write the code I can not infer much from comments such as this one - I mean "What is the common bug then?" If this comment refers to the situation that e.g. the locale implementation of GCCs standard library implementation generates invalid UTF-8 when using NBSP as thousands seperator, then the comment should say that. Well, my point about comments is a minor issue of course. I do not suggest that the author goes over all the code again just to add or change comments. I am a bit worried over the size of the libraries binary. On GNU/Linux x86_64 the built libboost_locale.so is almost 10MB large and codesize according to the "size" utility is almost 1MB. This comes in addition to the underlying ICU library. Is there any potential for reducing codesize? Due to the same concern about codesize I have also one concrete suggestion relating to the comparator template of the collation component. I suggest to not make the default comparision level a template parameter, instead to store it as a member. This way, when instantiating container templates the number of instantiations can be kept down. Or am I mistaken in thinking this would lead to more compact code? - What is your evaluation of the documentation? It is nicely structured. I could easily find the documentation for any specific component I was using and the documentation is also very helpful if you have a task at hand and want to find out which component to use (and whether such a component is available in the proposed Boost.Locale). There are some issues I have: Phrasing is sometime odd. For example right in the beginning, under the headline "What is Boost.Locale" there is a sentence which reads "C++ offers a very good base for localization via the existing C++ locale facets std::num_put, std::ctype, std::collate etc. But these are very limited and sometimes buggy by design." I can only guess what that means. Superficially it seems like a contradiction to me, something which is excellent can not be buggy by design, not even sometimes. Okay, minor issue again, it just stands out because it is only the fourth or fifth sentence or so. There are some typos (I guess) where it is important to be correct: Under "Messages Formatting (Translation)", subheading "Indirect Message Translation" all functions are documented as "The source text is not copied.". From the emphasis in the original document I think I can conclude that some of these functions copy and some do not. The reference section of the documentation should document the requirements on the CharType which many functions/classes are parameterized upon (can it be char/wchar_t only?). The reference documentation for token_iterator and break_iterator should not have individual entries for operator++, operator--, operator== and other operators which are always required for iterators, unless the documentation adds information. Instead, it should just be stated to which iterator concepts these templates conform. Documentation for the dereferening operators (operator*) of these templates states that the underlying sequences iterated over can not be modified with these operators. As this is the case, could a usage hint be incorporated stating that users should always use const_iterators as arguments to these templates? If a user sometimes employs for example std::string::iterator and sometimes std::string::const_iterator this would lead to unnecessary code bloat. Also, operator-> is missing from these templates. - What is your evaluation of the potential usefulness of the library? It is potentially very useful. The only objection I could conceive of is that ICU already provides much of the functionality of Boost.Locale. This library also duplicates functionality of Matthew Wilsons excellent Fastformat library (http://fastformat.sourceforge.net/) though the latter does not feature localization support as complete as that of the proposed Boost.Locale. - Did you try to use the library? With what compiler? Did you have any problems? I used the CMake way to build this library on an Opensuse system on x86_64. Compiler is GCC 4.5.1 (or a Svn snapshot roughly corresponding). The Boost version built against is 1.46.1, as delivered by Opensuse. I did not encounter any problems building the library. I played around with some of the components of the library and ran the supplied test cases. There is one inconsistency I noted, the following program generates output "Currency: $100.11" when the environment variable LANG is set to "en_US.UTF-8" and variable LC_MONETARY is set to "de_DE.UTF-8". Shouldn't the library honor LC_MONETARY? If LANG is set to "de_DE.UTF-8" "Currency: 100,11 €" is put out. Program: ------------------------------------------------- #include <ios> #include <iostream> #include <ostream> #include <locale> #include "boost/locale.hpp" int main() { namespace loc = boost::locale; using std::cout; loc::generator gen; cout.imbue(gen("")); cout << "Currency: " << loc::as::currency << 100.11 << '\n'; } ------------------------------------------------- - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? Reading the tuturial section of the Documentation. Glancing over the reference section. I also had a look at some of the source files, but only superficially. - Are you knowledgeable about the problem domain? Only marginally. With best regards, Volker Lukas

2 1

[locale] Review: Build
by Gevorg Voskanyan 17 Apr '11

17 Apr '11

build/Jamfile.v2: line 18: s/Feaures/Features line 130: There should be a space between '!' and '<target-os>cygwin', otherwise the whole condition will never evaluate to true line 132: s/need/needs/ . Also it can be equivalently replaced with just: EXIT "error: Boost.Locale needs either iconv or ICU library to be built." ; line 200: doesn't posix backend work for BSDs other than darwin? line 283: <link>shared:<define>BOOST_LOCALE_DYN_LINK=1 should be present in usage requirements too. The same applies to <threading>multi as well. lines 275, 282: what's the reason for commenting build_options and having <conditional>@configure instead? line 288: Being a vim user myself I appreciate this, but in general tabs are not allowed in code per Boost's development policy. Users of other editors would not be happy with tabs here :) General remarks: As a Boost.Build user I would see it very beneficial when using Boost.Locale to be able to have ICU build from source with BB just like the other 3rd party libraries commonly are. For it to work Boost.Locale Jamfile can check if a project /icu is available, and if so use /icu//icu as source and skip ICU configuration checking together with options for linking to prebuilt ICU. I can prepare and propose a patch for this if that scheme is OK with you. Examples and performance benchmarks should have Jamfiles too. Gevorg

2 6

SFINAE yes_type and no_type
by Jeroen Habraken 16 Apr '11

16 Apr '11

Hi, Is there a specific yes_type and no_type inside boost that I should be using when writing a SFINAE test? There seem to be quite a few defined already and reinventing the wheel (albeit it being trivial) again doesn't make sense. Regards, Jeroen

6 9

[GSoC] Reviewing
by Andrew Sutton 16 Apr '11

16 Apr '11

We have a little less than a week to finalize the set of 10 accepted projects. I've made tentative assignments to the top 10 projects that have a single willing mentor. There are two proposals with two mentors, that I did not assign a mentor to. If you are one of the mentors, you'll be getting a separate email, off list :) There are two highly rated proposals without mentors. I'm trying to work out what to do with those also. If you don't like your tentative assignment, let me know. There are 15-20 proposals that haven't been rated. I know that some are waiting on further input, but we should at least have initial ratings by the end of the week. Also, please check with the students of your highest rated proposals to see if they submitted proposals to other projects. I have to sit thru the duplication meeting next week and would like to know in advance if we're in competition with other organizations. Thanks, Andrew

1 0

[random] example code fails inside struct
by Beman Dawes 16 Apr '11

16 Apr '11

struct X { boost::mt19937 rng; boost::uniform_int<> million(1,1000000); // VC++ 10 error C2059: syntax error : 'constant' boost::variate_generator<boost::mt19937&, boost::uniform_int<> > random_value(rng, million); }; Why does the example code from the docs fail to compile when placed inside a struct or class? What am I missing? --Beman

3 4

Changesign function and nonfinite facets added to Boost.Math
by Paul A. Bristow 16 Apr '11

16 Apr '11

I've just added changesign function and nonfinite facets to Boost.Math in boost-trunk. These functions were part of the original floating-point collection written by Johan Rade but were previously only available from Spirit in boost-sandbox. Making them First Class citizens in Boost.Math will allow portable input/output of infinity and NaN, including use of lexical cast, archiving and serialization. Multiplatform testing of these new features should start soon. I hope this will not have any unwanted side effects - I'm sure you'll shout if it does. Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

1 0

[serialization] Add UTF-8 BOM support to xml_warchive
by Tijmen van Voorthuijsen 15 Apr '11

15 Apr '11

Hi, Recently I ran into the problem that the boost::serialization library could not handle XML files which contain the three UTF-8 BOM (Byte Order Mark) bytes. The serialization library creates XML files without the BOM bytes but when saving such files in an external Windows program, for example XML Notepad, these bytes are automatically added. Thereafter the XML file cannot be read anymore by the boost::serialization library. According to Wikipedia http://en.wikipedia.org/wiki/Byte_order_mark the UTF-8 BOM is optional and therefore creating XML files without the BOM bytes is all right. However, the reading should extended and be able to handle both types, files with and without the BOM. I propose to enhance the xml_warchive and text_warchive for reading with support of the BOM bytes. Example: namespace { const wchar_t g_cchUtf8Bom1 = 0xEF; const wchar_t g_cchUtf8Bom2 = 0xBB; const wchar_t g_cchUtf8Bom3 = 0xBF; } void CheckAndCorrectUtf8Bom(std::wifstream* pifs) { _ASSERT_POINTER(pifs); wchar_t chUtf8Bom1 = 0; wchar_t chUtf8Bom2 = 0; wchar_t chUtf8Bom3 = 0; chUtf8Bom1 = pifs->peek(); if (chUtf8Bom1 == g_cchUtf8Bom1) { *pifs >> chUtf8Bom1; _ASSERT(chUtf8Bom1 == g_cchUtf8Bom1); *pifs >> chUtf8Bom2; _ASSERT(chUtf8Bom2 == g_cchUtf8Bom2); *pifs >> chUtf8Bom3; _ASSERT(chUtf8Bom3 == g_cchUtf8Bom3); } else { // Reset to start of the stream pifs->seekg(0, std::ios_base::beg); } } Kind regards, Tijmen van Voorthuijsen ----------------------------------------------------------------------------------- T. van Voorthuijsen Senior System Engineer Noldus Information Technology bv Nieuwe Kanaal 5 P.O. Box 268 6700 AG Wageningen The Netherlands Phone: +31-(0)317-473300 Fax: +31-(0)317-424496 E-mail: T.van.Voorthuijsen(a)Noldus.nl<mailto:T.van.Voorthuijsen@Noldus.nl> Web: www.noldus.com<http://www.noldus.com>

3 2

[MSM] Interrupt anonymous transitions or blocking process_events?
by Mathias A 15 Apr '11

15 Apr '11

Hi there! I have been experimenting with the MSM (Meta State Machine) and I think it is a very nice tool! After reading and trying most of the example code regarding the MSM I present to you my problem. How do I interrupt blocking calls or long running states with anonymous transitions? Ok, here is my story. Regarding "Defining a submachine" in the docs (http://www.boost.org/doc/libs/1_46_1/libs/msm/doc/HTML/ch03s02.html#d0e597) and supplied source code example (http://www.boost.org/doc/libs/1_46_1/libs/msm/doc/HTML/examples/CompositeTu…) Let's say that this was a real CD player then the player would change to the next song by itself. It would not rely on the user pushing the Next button to change song. Now, if I implement the transition table like this: struct transition_table : mpl::vector4 // Start Event Next Action Guard -----------+-------------+---------+---------------------+----------------------+ a_row < Song1 , none , Song2 , &pl::start_next_song >, a_row < Song2 , PreviousSong, Song1 , &pl::start_prev_song >, a_row < Song2 , none , Song3 , &pl::start_next_song >, a_row < Song3 , PreviousSong, Song2 , &pl::start_prev_song > +---------+-------------+---------+---------------------+----------------------+ > {}; Note the "none" for anonymous transitions. By calling p.process_event(play()); the the player will start playing Song1 and then change to the next song by itself. But now in single threaded mode it blocks until it reaches "Song3". So it is not possible to process any other events during this time. In other words, it cannot process another process_event call. The "Playing" state has a "stop" event but calling this will not help as it will not be processed until the MSM has reached "Song3". In multi threaded mode (no complete source code for this here sorry. with mutex protected access to process_event) thread 1: lock(mutex) p.process_event(play()); lock.unlock(); thread 2: wait a few ms so we are in the middle of playing a song lock(mutex) p.process_event(stop()); lock.unlock(); I start the same p.process_event(play()); in thread 1. And in thread 2 I call p.process_event(stop()); The problem with this is that the stop() event does not get processed until it reaches Song3 because of the blocking call in p.process_event(play());. Perhaps I am going about this the wrong here and please tell me if it can be done in some other much better way! I want to be able to have automatic transitions that I can interrupt. A not so elegant workaround: In thread 2 access the Playing state directly and set a bool variable. (bool externalStop_;) Add a guard to each anonymous transition checking if the source state has externalStop_ == true and stop the transition. The Playing state can then create a stop event and then call process_event(stop()) by itself. And we have successfully injected a stop event. Summary: I cannot seem to get round the blocking call using only the transition table. I really hope it can be done in a more elegant way than I did in the workaround. Any suggestions on how to do this? Thank you! Best regards, Mathias

1 0

[locale] localization_backend_manager interface issue
by Max Sobolev 15 Apr '11

15 Apr '11

> std::auto_ptr<localization_backend> > localization_backend_manager::get() const; Class localization_backend_manager is marked as BOOST_LOCALE_DECL. This is hinting at placing instances of the class in a standalone shared library without problems. But here it is: using std::auto_ptr<> in interfaces is an error (Due to possibility of placing instances of classes in dynamic libraries). Dynamic library that contain your class might be compiled in debug / release / another mode, but client's code might have an alternative heap (because it use another C++ Run Time system) with an alternative heap manager. std::auto_ptr<> doesn't carrying *deleter* with a raw pointer of the allocated object, as boost::scoped_ptr<>, boost::shared_ptr<> or c++0x's std::unique_ptr<> does. Memory allocated from one heap might be "released" by foreign heap manager! :-/ See Sutter/Alexandrescu recommendation do not use std::auto_ptr<> (in ISBN: 9780321113580, C++ Coding Standards, "Rule 60: Avoid allocating and deallocating memory in different modules") and problem description (in ISBN: 9780201604641, Douglas Schmidt, Stephen Huston - C++ Network Programming [Volume 2] Chapter 5, "Sidebar 29: Portable Heap Operations with ACE") ..so change std::auto_ptr<> to some of the more safe smart pointer. > void localization_backend_manager::select( > std::string const& backend_name, > locale_category_type category = all_categories); Why you don't use enums instead of std::string and locale_category_type? (latter is unsigned, actually). So this code is permissible: boost::locale::localization_backend_manager::global().select("...", static_cast<unsigned>(std::rand())); std::string as opposed to ((emulated) scoped) enum implies discarded static type checking plus run-time overhead (due to *run-time* "type" checking, as i guess). unsigned type provides a wider "supertype" for argument than necessary -- - Do you speak English? Мужик с глубоким вздохом: - Yes I do. А хули толку?

5 5

[locale] Formal review of Boost.Local library -- need reviews!
by Chad Nelson 15 Apr '11

15 Apr '11

The final day of the Boost.Locale formal review is scheduled to be Saturday, and though there has been a lot of discussion, so far only one complete review has been submitted. If you're planning to review it, please don't delay. 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 (me). 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. -- Chad Nelson Oak Circle Software, Inc. * * *

8 11

Fw: [locale] Formal review of Boost.Locale library
by Chad Nelson 15 Apr '11

15 Apr '11

Begin forwarded message: Date: Thu, 07 Apr 2011 08:49:20 +0900 From: Darren Cook <darren(a)dcook.org> Subject: [locale] Formal review of Boost.Locale library Hello, I'm not on the devel list but just had a look at the Boost.Locale library documentation. Feel free to forward this to the list, or discard it. > - What is your evaluation of the documentation? * No prev/next page links [This should be fixed ASAP, as it discourages evaluating the library] * Confusing first page as it seems to only talk about other libraries, not the one in question. (?) * The examples are not motivating, and just end up looking complex. * I'd have liked to see examples in more languages, in particular some Asian languages, to comfort me that the library has taken their issues into consideration. If the itch being scratched here is just for a couple of European languages then the library may have design flaws. * The backends page ( http://cppcms.sourceforge.net/boost_locale/html/using_localization_backends… ) looks interesting, and may be the start of justifying the reason for this library to exist. It could be expanded with something more concrete: complete examples of doing something useful with different backends, with timings and exe sizes we could compare. > - What is your evaluation of the potential usefulness of the > library? I would choose to use ICU directly, as I couldn't see a reason not to, and I'd be concerned that the wrapper would not have wrapped some obscure function in ICU that I find I end up needing. > - How much effort did you put into your evaluation? A glance? A > quick reading? In-depth study? A quick reading. > - Are you knowledgeable about the problem domain? I've used ICU (it is essential in some situations), though possibly not from C/C++. Darren -- Darren Cook, Software Researcher/Developer http://dcook.org/work/ (About me and my work) http://dcook.org/blogs.html (My blogs and articles)

19 52

Re: [boost] [chrono] Compiler errors for mpl/abs.hpp
by Vicente BOTET 15 Apr '11

15 Apr '11

Hi, since Boost.Chrono was accepted I have moved to the trunk and the release branch. There are a lot of file in the sandbox that have been changed since. In particular the error comes from some compilers don't supporting nested value arithmetic in templates. To workaround this the trunk contain instead template<> struct abs_impl { #if defined(BOOST_MPL_CFG_NO_NESTED_VALUE_ARITHMETIC_2) template< typename N > struct apply : aux::abs_wknd< typename N::value_type, N::value > #else template< typename N > struct apply : integral_c< typename N::value_type, ((N::value < 0) ? (-N::value) : N::value ) > #endif { }; }; For this reason a suggest you to move to the trunk or the release branch. I will remove the Chrono sandbox as soon as the release 1.47 is out. Best, Vicente Message du 15/04/11 00:29 > De : "lcaminiti" > A : boost(a)lists.boost.org > Copie à : > Objet : [boost] [chrono] Compiler errors for mpl/abs.hpp > > Hello all, > > I am trying to compile the example below on MSVC using Boost.Chrono > (headers-only) from the sandbox but I am getting some compiler errors. > > What am I doing wrong? > > Thank you very much. > --Lorenzo > > #define BOOST_CHRONO_INLINED > #include > #include > #include > #include > #include > #include > #include > > int main(int argc, char* argv[]) { > assert(argc == 2); > unsigned long n = sqrt(double(atol(argv[1]))); > > using boost::phoenix::ref; > using boost::phoenix::arg_names::_1; > > double sum = 0.0; > int factor = 1; > > std::vector v(n); > std::fill(v.begin(), v.end(), 1.0); > > boost::chrono::duration sec; > for (unsigned long i = 0; i < n; ++i) { > boost::chrono::system_clock::time_point start = > boost::chrono::system_clock::now(); > std::for_each(v.begin(), v.end(), ( > ref(sum) += factor * _1 > )); > sec += boost::chrono::system_clock::now() - start; > } > std::cout << sec.count() << std::endl; > > assert(sum == n * n); > return 0; > } > > E:\sandbox\boost-sandbox-local\libs\local\example>cl /EHs /Ox /I..\..\.. > /I"c:\P > rogram Files\boost\boost_1_46_1" /I..\..\..\..\boost-sandbox-chrono.x > benchmark_ > boost_phoenix.cpp > Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for > 80x86 > Copyright (C) Microsoft Corporation. All rights reserved. > > benchmark_boost_phoenix.cpp > ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : error C2143: > syntax e > rror : missing ',' before ')' > ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(75) : see > reference > to class template instantiation 'boost::mpl::abs_impl::apply' being > compiled > ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : error C2059: > syntax e > rror : ')' > ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(74) : error C2143: > syntax e > rror : missing ';' before '{' > ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(75) : error C2143: > syntax e > rror : missing ';' before '}' > ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : error C2143: > syntax e > rror : missing ';' before '}' > ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : fatal error > C1004: un > expected end-of-file found > > > -- > View this message in context: http://boost.2283326.n4.nabble.com/boost-chrono-Compiler-errors-for-mpl-abs… > Sent from the Boost - Dev mailing list archive at Nabble.com. > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost >

1 0

[move] Declarations of the copy constructor and copy-assign operator produced by BOOST_MOVABLE_BUT_NOT_COPYABLE
by Joseph Trebbien 15 Apr '11

15 Apr '11

Looking through the sources of Boost.Move in trunk, I am wondering about a couple of lines in <boost/move/move.hpp> that are part of the expansion of BOOST_MOVABLE_BUT_NOT_COPYABLE when BOOST_NO_RVALUE_REFERENCES is defined: #define BOOST_MOVABLE_BUT_NOT_COPYABLE(TYPE)\ private:\ TYPE(TYPE &);\ TYPE& operator=(TYPE &);\ public:\ operator ::boost::rv<TYPE>&() \ { return *static_cast< ::boost::rv<TYPE>* >(this); }\ operator const ::boost::rv<TYPE>&() const \ { return *static_cast<const ::boost::rv<TYPE>* >(this); }\ private:\ // Why do the declarations of the copy constructor and copy-assign operator overload not take a const-reference to TYPE? When BOOST_NO_RVALUE_REFERENCES is not defined, they do: #define BOOST_MOVABLE_BUT_NOT_COPYABLE(TYPE)\ public:\ typedef int boost_move_emulation_t;\ private:\ TYPE(const TYPE &);\ TYPE& operator=(const TYPE &);\ // Joseph Trebbien

2 1

[chrono] Compiler errors for mpl/abs.hpp
by lcaminiti 14 Apr '11

14 Apr '11

Hello all, I am trying to compile the example below on MSVC using Boost.Chrono (headers-only) from the sandbox but I am getting some compiler errors. What am I doing wrong? Thank you very much. --Lorenzo #define BOOST_CHRONO_INLINED #include <boost/chrono.hpp> #include <boost/spirit/include/phoenix.hpp> #include #include #include #include #include int main(int argc, char* argv[]) { assert(argc == 2); unsigned long n = sqrt(double(atol(argv[1]))); using boost::phoenix::ref; using boost::phoenix::arg_names::_1; double sum = 0.0; int factor = 1; std::vector v(n); std::fill(v.begin(), v.end(), 1.0); boost::chrono::duration sec; for (unsigned long i = 0; i < n; ++i) { boost::chrono::system_clock::time_point start = boost::chrono::system_clock::now(); std::for_each(v.begin(), v.end(), ( ref(sum) += factor * _1 )); sec += boost::chrono::system_clock::now() - start; } std::cout << sec.count() << std::endl; assert(sum == n * n); return 0; } E:\sandbox\boost-sandbox-local\libs\local\example>cl /EHs /Ox /I..\..\.. /I"c:\P rogram Files\boost\boost_1_46_1" /I..\..\..\..\boost-sandbox-chrono.x benchmark_ boost_phoenix.cpp Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for 80x86 Copyright (C) Microsoft Corporation. All rights reserved. benchmark_boost_phoenix.cpp ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : error C2143: syntax e rror : missing ',' before ')' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(75) : see reference to class template instantiation 'boost::mpl::abs_impl::apply' being compiled ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : error C2059: syntax e rror : ')' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(74) : error C2143: syntax e rror : missing ';' before '{' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(75) : error C2143: syntax e rror : missing ';' before '}' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : error C2143: syntax e rror : missing ';' before '}' ..\..\..\..\boost-sandbox-chrono.x\boost/mpl/abs.hpp(72) : fatal error C1004: un expected end-of-file found -- View this message in context: http://boost.2283326.n4.nabble.com/boost-chrono-Compiler-errors-for-mpl-abs… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

[locale] trouble building
by Noah Roberts 14 Apr '11

14 Apr '11

I grabbed the ICU bin for VS2010. I extracted the content into d:\icu so that d:\icu\include has the various includes. I set up the PATH variable to include d:\icu\bin... I copied boost and lib from the review into boost_1_46_1 where the root of boost source is. The docs seem to imply that I can get a build without ICU if I'm using Windows but this doesn't seem to be the case. I tried --without-icu and I got an error about using --with and --without for the same lib. Here's my attempt to build (with ICU installed): D:\boost_1_46_1\boost_1_46_1>bjam --build-dir=.\build toolset=msvc-10 --with-loc ale --prefix=d:\boost_msvc_1461 --layout=system -sICU_PATH=d:\icu stage Performing configuration checks - iconv (libc) : no - iconv (separate) : no - icu : no D:/boost_1_46_1/boost_1_46_1/tools/build/v2/build\virtual-target.jam:1079: in vi rtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <pstage\lib>libboost_locale.lib error: previous virtual target { common%common.copy-libboost_locale.lib.STATIC_L IB { msvc%msvc.archive-libboost_locale.lib.STATIC_LIB { msvc%msvc.compile.c++-en coding\codepage.obj.OBJ { encoding/codepage.cpp.CPP } } { msvc%msvc.compile.c++- shared\date_time.obj.OBJ { shared/date_time.cpp.CPP } } { msvc%msvc.compile.c++- shared\format.obj.OBJ { shared/format.cpp.CPP } } { msvc%msvc.compile.c++-shared \formatting.obj.OBJ { shared/formatting.cpp.CPP } } { msvc%msvc.compile.c++-shar ed\generator.obj.OBJ { shared/generator.cpp.CPP } } { msvc%msvc.compile.c++-shar ed\ids.obj.OBJ { shared/ids.cpp.CPP } } { msvc%msvc.compile.c++-shared\localizat ion_backend.obj.OBJ { shared/localization_backend.cpp.CPP } } { msvc%msvc.compil e.c++-shared\message.obj.OBJ { shared/message.cpp.CPP } } { msvc%msvc.compile.c+ +-shared\mo_lambda.obj.OBJ { shared/mo_lambda.cpp.CPP } } { msvc%msvc.compile.c+ +-util\codecvt_converter.obj.OBJ { util/codecvt_converter.cpp.CPP } } { msvc%msv c.compile.c++-util\default_locale.obj.OBJ { util/default_locale.cpp.CPP } } { ms vc%msvc.compile.c++-util\info.obj.OBJ { util/info.cpp.CPP } } { msvc%msvc.compil e.c++-util\locale_data.obj.OBJ { util/locale_data.cpp.CPP } } { msvc%msvc.compil e.c++-std\codecvt.obj.OBJ { std/codecvt.cpp.CPP } } { msvc%msvc.compile.c++-std\ collate.obj.OBJ { std/collate.cpp.CPP } } { msvc%msvc.compile.c++-std\converter. obj.OBJ { std/converter.cpp.CPP } } { msvc%msvc.compile.c++-std\numeric.obj.OBJ { std/numeric.cpp.CPP } } { msvc%msvc.compile.c++-std\std_backend.obj.OBJ { std/ std_backend.cpp.CPP } } { msvc%msvc.compile.c++-util\gregorian.obj.OBJ { util/gr egorian.cpp.CPP } } { msvc%msvc.compile.c++-win32\collate.obj.OBJ { win32/collat e.cpp.CPP } } { msvc%msvc.compile.c++-win32\converter.obj.OBJ { win32/converter. cpp.CPP } } { msvc%msvc.compile.c++-win32\lcid.obj.OBJ { win32/lcid.cpp.CPP } } { msvc%msvc.compile.c++-win32\numeric.obj.OBJ { win32/numeric.cpp.CPP } } { msvc %msvc.compile.c++-win32\win_backend.obj.OBJ { win32/win_backend.cpp.CPP } } } } error: created from ./stage-proper error: another virtual target { common%common.copy-libboost_locale.lib.STATIC_LI B { msvc%msvc.archive-libboost_locale.lib.STATIC_LIB { msvc%msvc.compile.c++-enc oding\codepage.obj.OBJ { encoding/codepage.cpp.CPP } } { msvc%msvc.compile.c++-s hared\date_time.obj.OBJ { shared/date_time.cpp.CPP } } { msvc%msvc.compile.c++-s hared\format.obj.OBJ { shared/format.cpp.CPP } } { msvc%msvc.compile.c++-shared\ formatting.obj.OBJ { shared/formatting.cpp.CPP } } { msvc%msvc.compile.c++-share d\generator.obj.OBJ { shared/generator.cpp.CPP } } { msvc%msvc.compile.c++-share d\ids.obj.OBJ { shared/ids.cpp.CPP } } { msvc%msvc.compile.c++-shared\localizati on_backend.obj.OBJ { shared/localization_backend.cpp.CPP } } { msvc%msvc.compile .c++-shared\message.obj.OBJ { shared/message.cpp.CPP } } { msvc%msvc.compile.c++ -shared\mo_lambda.obj.OBJ { shared/mo_lambda.cpp.CPP } } { msvc%msvc.compile.c++ -util\codecvt_converter.obj.OBJ { util/codecvt_converter.cpp.CPP } } { msvc%msvc .compile.c++-util\default_locale.obj.OBJ { util/default_locale.cpp.CPP } } { msv c%msvc.compile.c++-util\info.obj.OBJ { util/info.cpp.CPP } } { msvc%msvc.compile .c++-util\locale_data.obj.OBJ { util/locale_data.cpp.CPP } } { msvc%msvc.compile .c++-std\codecvt.obj.OBJ { std/codecvt.cpp.CPP } } { msvc%msvc.compile.c++-std\c ollate.obj.OBJ { std/collate.cpp.CPP } } { msvc%msvc.compile.c++-std\converter.o bj.OBJ { std/converter.cpp.CPP } } { msvc%msvc.compile.c++-std\numeric.obj.OBJ { std/numeric.cpp.CPP } } { msvc%msvc.compile.c++-std\std_backend.obj.OBJ { std/s td_backend.cpp.CPP } } { msvc%msvc.compile.c++-util\gregorian.obj.OBJ { util/gre gorian.cpp.CPP } } { msvc%msvc.compile.c++-win32\collate.obj.OBJ { win32/collate .cpp.CPP } } { msvc%msvc.compile.c++-win32\converter.obj.OBJ { win32/converter.c pp.CPP } } { msvc%msvc.compile.c++-win32\lcid.obj.OBJ { win32/lcid.cpp.CPP } } { msvc%msvc.compile.c++-win32\numeric.obj.OBJ { win32/numeric.cpp.CPP } } { msvc% msvc.compile.c++-win32\win_backend.obj.OBJ { win32/win_backend.cpp.CPP } } } } error: created from ./stage-proper error: added properties: <debug-symbols>on <inlining>off <optimization>off <runt ime-debugging>on <variant>debug error: removed properties: <debug-symbols>off <define>NDEBUG <inlining>full <opt imization>speed <runtime-debugging>off <variant>release D:/boost_1_46_1/boost_1_46_1/tools/build/v2/build\virtual-target.jam:490: in act ualize-no-scanner from module object(file-target)@962 D:/boost_1_46_1/boost_1_46_1/tools/build/v2/build\virtual-target.jam:135: in obj ect(file-target)(a)962.actualize from module object(file-target)@962 D:/boost_1_46_1/boost_1_46_1/tools/build/v2\build-system.jam:748: in load from m odule build-system D:\boost_1_46_1\boost_1_46_1\tools\build\v2/kernel\modules.jam:283: in import fr om module modules D:\boost_1_46_1\boost_1_46_1\tools\build\v2\kernel\bootstrap.jam:142: in boost-b uild from module D:\boost_1_46_1\boost_1_46_1\boost-build.jam:17: in module scope from module D:\boost_1_46_1\boost_1_46_1> Any ideas?

3 3

[Boost.Pool] TR1?
by Phil Bouchard 14 Apr '11

14 Apr '11

Greetings, I see the Boost.Pool is not making its way up to the C++ standards yet an it is very unfortunate given its great use. Boost.Pool provides an is_from() member function that does a simple range check and returns whether a pointer is part of the pool or not. This is a very useful function which I think should be part of the standards because it could be used for the global pool as well; i.e. the one used by operator ::new and ::delete. The benefits outweigh the costs. Thanks, -Phil

8 49

[Parallel BGL] Property access problem
by Cosimo Calabrese 14 Apr '11

14 Apr '11

Hi to all, I'm working on a WinXP, VS2010, boost 1.46.1, openMPI 1.4.3. I've used in the past the BGL lib, and now I would explore the PBGL extension. I've writed a simple program (you can find it in attach), but I've some problem. When I run it with: mpirun -np 1 .\test.exe it works. But if I use 2 or 4 processors the program crash sistematically in the following way, on different machines too: num_vertices: 10 num_edges: 19 A-->B : 1 A-->C : 10 A-->D : 11 B-->D : 13 C-->D : 12 B-->E : 1 C-->A : 14 E-->D : 1 D-->B : 15 D-->A : 1 E-->B : 16 -------------------------------------------------------------------------- Sorry! You were supposed to get help about: odls-default:could-not-kill But I couldn't open the help file: D:\dev\CommesseAperte\Sviluppo\TELLUSXX_CalcServer\lib\openmpi\installed\share\openmpi\help-odls-default.txt: No such file or directory. Sorry! -------------------------------------------------------------------------- Every process allocates 1 GB. The problem disappear only when I eliminate all the property access (get() and put()). Maybe I access to the MPI framework for the first time during the property access, and so could be an MPI problem? Am I using the property in a wrong way? Thanks in advance, Cosimo Calabrese.

1 1

New, powerful way to use enable_if in C++0x
by Matt Calabrese 13 Apr '11

13 Apr '11

I'm not sure if there is much interest in this or if someone else discovered this as well, but I realized today that enable_if can be used in a new way in C++0x. Traditionally when working with enable_if with function templates you invoke it either in the return type or in an additional function parameter of the function. Each of these has advantages and disadvantages. The parameter form has the downside of augmenting the parameter list. The most notable problems with this approach are that it can't be used with overloaded operators that require a fixed number of arguments, and it can't be used after a variadic argument list. The return type use of enable_if is often preferred since it does not involve augmenting the parameter list, meaning that it can be used with most overloaded operators, but you still can't use it for conversion operations and you can't use it all with constructors as they have no explicit return type. However, in C++0x, there is a new way to use enable_if by altering neither the function parameter list nor the specification of the return type. It can be used with operators, constructors, variadic function templates, and even overloaded conversion operations (the latter of which was previously considered impossible). The way to do it is with C++0x default function template parameters. Rather than try to explain any further in English, the following code should demonstrate the approach fairly clearly (tested in GCC 4.5.2): http://codepaste.net/23yo8o There is only one drawback that I can think of off of the top of my head -- you can't refer to the function parameters by name for the enable_if condition, whereas in C++0x if you use the return type form of enable_if along with the new trailing return type form of function declarations you can. I have never personally wanted to do this and I highly doubt that it's common so this is likely entirely a non-issue, plus you can always use std::declval anyway so you aren't actually losing any high-level functionality. Are there any thoughts on this or drawbacks other than what I mentioned? Should such use be added to the docs as supported behavior in 0x compilers? -- -Matt Calabrese

16 34

[config] Local classes as template parameters
by Lorenzo Caminiti 13 Apr '11

13 Apr '11

On Sat, Feb 12, 2011 at 5:50 AM, John Bytheway <jbytheway+boost(a)gmail.com> wrote: > On 11/02/11 22:29, Lorenzo Caminiti wrote: >> On Fri, Feb 11, 2011 at 4:31 PM, Lorenzo Caminiti <lorcaminiti(a)gmail.com> wrote: >>> From: John Bytheway <jbytheway+boost(a)gmail.com> >>> 2. Might anyone care so much about performance that they absolutely must >>> have the code inlined? The answer is probably "yes" (or at least there >>> will be people who *think* they care, which is also a problem). For >>> these people you could, if you choose, provide an alternate >>> implementation which doesn't indirect through local::function<>, and >>> thus will only work in C++0x (or C++03 with non-standard extensions). >> >> Without inheriting from local::function_base<> and then using >> local::function_ref<> the local struct cannot be passed as a template >> parameter in C++. Is this different for C++0x (C++03)? > > Yes, in C++0x local structs can be passed as template parameters. > Obviously, in C++0x there are lambdas too, so you might think your > library is useless, but I'd expect most compilers to support passing > local structs as template parameters before they support lambdas, so > there is some advantage in having this intermediate implementation. > Also, your macros would allow writing code that worked in C++0x and > C++03, with the virtual function business in only those compilers/modes > where it is necessary. Hello all, Is there a Boost.Config macro that indicates if the compiler allows local classes to be passed as template parameters? Thank you. -- Lorenzo

3 2

[GSoC] Boost.Tree and Boost.BloomFilter
by Alejandro Cabrera 13 Apr '11

13 Apr '11

Hello all, I've filed two proposals for this Google Summer of Code. Boost.Tree: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/cppcabre… <http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/cppcabre…> Boost.BloomFilter: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/cppcabre… I'd be glad to work on either project. Feedback is welcome. Thanks, -Alej

3 5

Installation fails if env VMS is set
by Dreamcat4 12 Apr '11

12 Apr '11

Hi, Over on the Boost-Users mailinglist we have found that this environment variable (and perhaps unknown but maybe others) will cause bootstrap.sh / Jam failure during the Boost libraries compile and install. Heres the full thread: http://lists.boost.org/boost-users/2011/04/67716.php You (or Jam developement team) may wish to consider taking some kind of action to avoid this as VMS is a very common acronym for "Virtual Machines". Its usage elsewhere is widespread and certainly not Boost-specific. Other choices of course - maybe look towards documenting such usag(es) if they cannot be easily avoided. Or consider ways to detect / warn / clean out the users shell environment variables if they are conflicting. Sorry I cant help any further however as a new user I simply have no experience with the Boost library yet. Many thanks. dreamcat4 dreamcat4(a)gmail.com

2 4

[GSOC]SIMD Library
by Faiçal Tchirou 12 Apr '11

12 Apr '11

Hi everyone, I recently ask documentation about the SIMD Library project here and I receive some guides and references links from Joel Falcou. Now I have some questions about the library itself. Is the goal of the project to build a library similar to libSIMDx86 but more focusing on the AltiVec instruction set ? Joel also advises me to take a look at Proto. I read that Proto is used to build DSEL. Will Proto be used to map high level classes and methods of the library to native SIMD instructions ? What about the library itself ? Which modules have to be developped ? Thanks.

8 37

[trac] Misuse of trac system by spammer
by Joachim Faulhaber 12 Apr '11

12 Apr '11

Hi, I received a ticket today: https://svn.boost.org/trac/boost/ticket/5457 that's only purpose is to distribute a commercial link. Has anyone experienced a similar misuse of the trac system? Are there ideas how to prevent this? Regards, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de

3 5

[GSoC] Proposal reviewing
by Andrew Sutton 12 Apr '11

12 Apr '11

Mentors, We need to establish some guidelines for reviewing proposals. They won't be complicated :) I'm opting not to use the mentors mailing list for this announcement. I know that all the mentors are subscribed here. Here's how this should work: 1. Identify the set of proposals for projects that you are interested in mentoring. 2. Evaluate the proposal and write your evaluation as a PRIVATE comment. 3. If you have questions of the student, you can write PUBLIC comments or send them an email. 4. Rank the proposal (I think 5 is the best this year). That would be the project that you want to mentor. Towards the end of the review process, we will select the 10 best proposals. This doesn't guarantee that we'll *fund* 10 proposals, just that I've requested 10 slots. I would like, this year, if all students got feedback regarding their proposals even if they are clearly rejects. The reason for writing evaluations privately, for now, is that it will help me write a public summary for proposals that are not accepted. I'll figure out how this is going to work over the course of the week :) Specific evaluation criteria are up to you (the mentors). You may ask students to modify good proposals. You do not need to ask *all* students to improve their proposals. At the end of the week, you should have a list of 1 or 2 proposals that *you yourself* will mentor. If you are not offering to mentor the project, please don't review it as a 5. Otherwise, we end up with a case where we have to assign a mentor to a project that they aren't interested in. I don't think that this has worked out very well in the past. Also, would prefer that comments regarding specific proposals not be sent to the list. I don't think it would be a good idea for a flood of "this proposal is AWFUL" emails to start popping up. I'm all for transparency, but I don't think airing value judgements would be a beneficial for community development :) Questions or comments involving evaluation criteria and process are fine. Andrew

4 8

[convert] incomplete reference documentation
by Vicente BOTET 11 Apr '11

11 Apr '11

Hi, I was taking a look at the documentation and it seems to me that the reference documentation is incomplete and not ready for review. Do you plan to complete it before review? Thanks, Vicente

4 9

[locale] Reminder - Review 7-16 in April
by Artyom 11 Apr '11

11 Apr '11

Dear Boosters, I'd like to remind you that there is a formal review of the Boost.Locale library running these days. http://lists.boost.org/boost-announce/2011/04/0298.php It is very important to provide the feedback during the formal review so it would be possible to decide whether it is valuable addition to boost (I hope so). I know that some of view provided very good and important feedback during preliminary reviews and some of you already use it in your projects. So I'm looking forward for your formal reviews of the Boost.Locale library. Thank you very much, Artyom Beilis

1 0

[Fusion] fold takes state by cref. Why ?
by Joel Falcou 11 Apr '11

11 Apr '11

Why is the State passed by const reference ? I have a couple of use case (like using fold to access the element (i0,...,in) of a fusion sequence of pointer to ... pointer to T array) where I need to be able to discriminate the constness of the State to forward to the proper PFO overload of operator(). Is there any intrinsic stuff I am missing ?

3 3

Boost Verify
by Olaf van der Spek 11 Apr '11

11 Apr '11

Hi, > It has exactly the same behavior as BOOST_ASSERT, except that the expression that is passed to BOOST_VERIFY is always evaluated. Does it just evaluate the expression or does it also fail is it evaluates to false? Why is there no BOOST_VERIFY_MSG? http://www.boost.org/doc/libs/1_46_1/libs/utility/assert.html#BOOST_VERIFY Greetings, -- Olaf

3 3

Boost MPL metafunction shortcut
by Joel Falcou 11 Apr '11

11 Apr '11

I was thinking lately that it is a shame we can't do the following : boost::mpl::transform< SomeSequence, _1&> instead of the lengthy boost::mpl::transform< SomeSequence, add_reference<_1> > same goes for *, const, volatile : boost::mpl::transform< SomeSequence, volatile _1**&> Could it be possible to get such a behavior in MPL by having a pass of replacing type qualifier by corresponding metafunction until none are left then apply the lambda ? In the same vein, having a MPL trandform turning a sequence of std::vector into their corresponding value_type require out of line small metafunction to be written. I guess a macro like BOOST_MPL_ADAPTED_PLACEHOLDER( v, (type)(value_type)(reference)(const_reference) ) builds a whoel familly of _v1, ..., _v5 placeholder which behaves like _n and expose typedef called value_type etc ... that resolve to said small lambda function directly. This would allow for a terse: boost::mpl::transform< SomeSequence, _v1::reference> Are these ideas out of the question due to some internals of MPL I missed ? Are they worthy a patch ?

4 5

[serialization] conflicting declaration in version.hpp
by sguazt 11 Apr '11

11 Apr '11

Hello, I've just updated the trunk version of Boost (rev. 71184). Now GCC 4.6 fails to compile due to the following error: --- [error] --- boost-trunk/boost/serialization/version.hpp:57:17: error: conflicting declaration ‘int boost::serialization::version<T>::value’ boost-trunk/boost/serialization/version.hpp:52:5: error: ‘boost::serialization::version<T>::value’ has a previous declaration as ‘const int boost::serialization::version<T>::value’ boost-trunk/boost/serialization/version.hpp:57:17: error: declaration of ‘const int boost::serialization::version<T>::value’ outside of class is not definition [-fpermissive] --- [/error] --- It seems that adding the const specifier fixes the problem, that is: #ifndef BOOST_NO_INCLASS_MEMBER_INITIALIZATION template<class T> const int version<T>::value; #endif Could you fix it? Thank you very much! Best, -- Marco

1 0

building BOOST problems
by Brestin Seby 11 Apr '11

11 Apr '11

hello, I am trying now for several days to build Boost, but apparently I have encountered some errors. Please give some help. razyelx@razyelx-X51L:~/Libraries/boost_1_46_1$ bjam nBuilding the Boost C++ Libraries.nn warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. ...patience... ...patience... ...patience... ...found 7309 targets... ...updating 70 targets... gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.4.5/release/threading-multi/bzip2.o libs/iostreams/src/bzip2.cpp:20: fatal error: bzlib.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_DYN_LINK=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I"." -c -o "bin.v2/libs/iostreams/build/gcc-4.4.5/release/threading-multi/bzip2.o" "libs/iostreams/src/bzip2.cpp" ...failed gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.4.5/release/threading-multi/bzip2.o... ...skipped <pbin.v2/libs/iostreams/build/gcc-4.4.5/release/threading-multi>libboost_iostreams.so.1.46.1 for lack of <pbin.v2/libs/iostreams/build/gcc-4.4.5/release/threading-multi>bzip2.o... ...skipped <pstage/lib>libboost_iostreams.so.1.46.1 for lack of <pbin.v2/libs/iostreams/build/gcc-4.4.5/release/threading-multi>libboost_iostreams.so.1.46.1... ...skipped <pstage/lib>libboost_iostreams.so for lack of <pstage/lib>libboost_iostreams.so.1.46.1... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/numeric.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/numeric.hpp:8, from libs/python/src/numeric.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/numeric.o" "libs/python/src/numeric.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/numeric.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/list.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/list.hpp:8, from libs/python/src/list.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/list.o" "libs/python/src/list.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/list.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/long.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/long.hpp:8, from libs/python/src/long.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/long.o" "libs/python/src/long.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/long.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/dict.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/dict.hpp:8, from libs/python/src/dict.cpp:4: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/dict.o" "libs/python/src/dict.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/dict.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/tuple.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/tuple.hpp:8, from libs/python/src/tuple.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/tuple.o" "libs/python/src/tuple.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/tuple.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/str.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/str.hpp:8, from libs/python/src/str.cpp:4: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/str.o" "libs/python/src/str.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/str.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/slice.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/slice.hpp:9, from libs/python/src/slice.cpp:1: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/slice.o" "libs/python/src/slice.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/slice.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/from_python.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/converter/from_python.hpp:8, from libs/python/src/converter/from_python.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/from_python.o" "libs/python/src/converter/from_python.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/from_python.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/registry.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/type_id.hpp:8, from ./boost/python/converter/registry.hpp:7, from libs/python/src/converter/registry.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/registry.o" "libs/python/src/converter/registry.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/registry.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/type_id.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/type_id.hpp:8, from libs/python/src/converter/type_id.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/type_id.o" "libs/python/src/converter/type_id.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/type_id.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/enum.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object_core.hpp:10, from ./boost/python/object/enum_base.hpp:8, from libs/python/src/object/enum.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/enum.o" "libs/python/src/object/enum.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/enum.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/class.o In file included from ./boost/python/detail/prefix.hpp:13, from libs/python/src/object/class.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/class.o" "libs/python/src/object/class.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/class.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/function.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object/function.hpp:8, from ./boost/python/docstring_options.hpp:8, from libs/python/src/object/function.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/function.o" "libs/python/src/object/function.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/function.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/inheritance.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/type_id.hpp:8, from ./boost/python/object/inheritance.hpp:8, from libs/python/src/object/inheritance.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/inheritance.o" "libs/python/src/object/inheritance.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/inheritance.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/life_support.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object/life_support.hpp:7, from libs/python/src/object/life_support.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/life_support.o" "libs/python/src/object/life_support.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/life_support.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/pickle_support.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/make_function.hpp:8, from libs/python/src/object/pickle_support.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/pickle_support.o" "libs/python/src/object/pickle_support.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/pickle_support.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/errors.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/errors.hpp:12, from libs/python/src/errors.cpp:10: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/errors.o" "libs/python/src/errors.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/errors.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/module.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/scope.hpp:8, from libs/python/src/module.cpp:9: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/module.o" "libs/python/src/module.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/module.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/builtin_converters.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/handle.hpp:8, from libs/python/src/converter/builtin_converters.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/builtin_converters.o" "libs/python/src/converter/builtin_converters.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/builtin_converters.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/arg_to_python_base.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/handle.hpp:8, from ./boost/python/converter/arg_to_python_base.hpp:7, from libs/python/src/converter/arg_to_python_base.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/arg_to_python_base.o" "libs/python/src/converter/arg_to_python_base.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/converter/arg_to_python_base.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/iterator.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object_fwd.hpp:8, from ./boost/python/object/iterator_core.hpp:8, from libs/python/src/object/iterator.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/iterator.o" "libs/python/src/object/iterator.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/iterator.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/stl_iterator.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/ssize_t.hpp:9, from ./boost/python/object.hpp:8, from libs/python/src/object/stl_iterator.cpp:10: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/stl_iterator.o" "libs/python/src/object/stl_iterator.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/stl_iterator.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object_protocol.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object_protocol.hpp:8, from libs/python/src/object_protocol.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object_protocol.o" "libs/python/src/object_protocol.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object_protocol.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object_operators.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object_operators.hpp:8, from libs/python/src/object_operators.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object_operators.o" "libs/python/src/object_operators.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object_operators.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/wrapper.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/detail/wrapper_base.hpp:7, from ./boost/python/wrapper.hpp:7, from libs/python/src/wrapper.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/wrapper.o" "libs/python/src/wrapper.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/wrapper.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/import.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/ssize_t.hpp:9, from ./boost/python/object.hpp:8, from ./boost/python/import.hpp:8, from libs/python/src/import.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/import.o" "libs/python/src/import.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/import.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/exec.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/ssize_t.hpp:9, from ./boost/python/object.hpp:8, from ./boost/python/exec.hpp:8, from libs/python/src/exec.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/exec.o" "libs/python/src/exec.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/exec.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/function_doc_signature.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/converter/registrations.hpp:8, from libs/python/src/object/function_doc_signature.cpp:9: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/function_doc_signature.o" "libs/python/src/object/function_doc_signature.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/threading-multi/object/function_doc_signature.o... ...skipped <pbin.v2/libs/python/build/gcc-4.4.5/release/threading-multi>libboost_python.so.1.46.1 for lack of <pbin.v2/libs/python/build/gcc-4.4.5/release/threading-multi>numeric.o... ...skipped <pstage/lib>libboost_python.so.1.46.1 for lack of <pbin.v2/libs/python/build/gcc-4.4.5/release/threading-multi>libboost_python.so.1.46.1... ...skipped <pstage/lib>libboost_python.so for lack of <pstage/lib>libboost_python.so.1.46.1... gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.4.5/release/link-static/threading-multi/bzip2.o libs/iostreams/src/bzip2.cpp:20: fatal error: bzlib.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I"." -c -o "bin.v2/libs/iostreams/build/gcc-4.4.5/release/link-static/threading-multi/bzip2.o" "libs/iostreams/src/bzip2.cpp" ...failed gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.4.5/release/link-static/threading-multi/bzip2.o... ...skipped <pbin.v2/libs/iostreams/build/gcc-4.4.5/release/link-static/threading-multi>libboost_iostreams.a(clean) for lack of <pbin.v2/libs/iostreams/build/gcc-4.4.5/release/link-static/threading-multi>bzip2.o... ...skipped <pbin.v2/libs/iostreams/build/gcc-4.4.5/release/link-static/threading-multi>libboost_iostreams.a for lack of <pbin.v2/libs/iostreams/build/gcc-4.4.5/release/link-static/threading-multi>bzip2.o... ...skipped <pstage/lib>libboost_iostreams.a for lack of <pbin.v2/libs/iostreams/build/gcc-4.4.5/release/link-static/threading-multi>libboost_iostreams.a... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/numeric.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/numeric.hpp:8, from libs/python/src/numeric.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/numeric.o" "libs/python/src/numeric.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/numeric.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/list.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/list.hpp:8, from libs/python/src/list.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/list.o" "libs/python/src/list.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/list.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/long.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/long.hpp:8, from libs/python/src/long.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/long.o" "libs/python/src/long.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/long.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/dict.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/dict.hpp:8, from libs/python/src/dict.cpp:4: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/dict.o" "libs/python/src/dict.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/dict.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/tuple.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/tuple.hpp:8, from libs/python/src/tuple.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/tuple.o" "libs/python/src/tuple.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/tuple.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/str.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/str.hpp:8, from libs/python/src/str.cpp:4: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/str.o" "libs/python/src/str.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/str.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/slice.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/slice.hpp:9, from libs/python/src/slice.cpp:1: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/slice.o" "libs/python/src/slice.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/slice.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/from_python.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/converter/from_python.hpp:8, from libs/python/src/converter/from_python.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/from_python.o" "libs/python/src/converter/from_python.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/from_python.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/registry.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/type_id.hpp:8, from ./boost/python/converter/registry.hpp:7, from libs/python/src/converter/registry.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/registry.o" "libs/python/src/converter/registry.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/registry.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/type_id.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/type_id.hpp:8, from libs/python/src/converter/type_id.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/type_id.o" "libs/python/src/converter/type_id.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/type_id.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/enum.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object_core.hpp:10, from ./boost/python/object/enum_base.hpp:8, from libs/python/src/object/enum.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/enum.o" "libs/python/src/object/enum.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/enum.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/class.o In file included from ./boost/python/detail/prefix.hpp:13, from libs/python/src/object/class.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/class.o" "libs/python/src/object/class.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/class.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/function.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object/function.hpp:8, from ./boost/python/docstring_options.hpp:8, from libs/python/src/object/function.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/function.o" "libs/python/src/object/function.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/function.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/inheritance.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/type_id.hpp:8, from ./boost/python/object/inheritance.hpp:8, from libs/python/src/object/inheritance.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/inheritance.o" "libs/python/src/object/inheritance.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/inheritance.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/life_support.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object/life_support.hpp:7, from libs/python/src/object/life_support.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/life_support.o" "libs/python/src/object/life_support.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/life_support.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/pickle_support.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/make_function.hpp:8, from libs/python/src/object/pickle_support.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/pickle_support.o" "libs/python/src/object/pickle_support.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/pickle_support.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/errors.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/errors.hpp:12, from libs/python/src/errors.cpp:10: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/errors.o" "libs/python/src/errors.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/errors.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/module.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/scope.hpp:8, from libs/python/src/module.cpp:9: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/module.o" "libs/python/src/module.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/module.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/builtin_converters.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/handle.hpp:8, from libs/python/src/converter/builtin_converters.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/builtin_converters.o" "libs/python/src/converter/builtin_converters.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/builtin_converters.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/arg_to_python_base.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/handle.hpp:8, from ./boost/python/converter/arg_to_python_base.hpp:7, from libs/python/src/converter/arg_to_python_base.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/arg_to_python_base.o" "libs/python/src/converter/arg_to_python_base.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/converter/arg_to_python_base.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/iterator.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object_fwd.hpp:8, from ./boost/python/object/iterator_core.hpp:8, from libs/python/src/object/iterator.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/iterator.o" "libs/python/src/object/iterator.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/iterator.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/stl_iterator.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/ssize_t.hpp:9, from ./boost/python/object.hpp:8, from libs/python/src/object/stl_iterator.cpp:10: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/stl_iterator.o" "libs/python/src/object/stl_iterator.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/stl_iterator.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object_protocol.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object_protocol.hpp:8, from libs/python/src/object_protocol.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object_protocol.o" "libs/python/src/object_protocol.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object_protocol.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object_operators.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/object_operators.hpp:8, from libs/python/src/object_operators.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object_operators.o" "libs/python/src/object_operators.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object_operators.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/wrapper.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/detail/wrapper_base.hpp:7, from ./boost/python/wrapper.hpp:7, from libs/python/src/wrapper.cpp:5: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/wrapper.o" "libs/python/src/wrapper.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/wrapper.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/import.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/ssize_t.hpp:9, from ./boost/python/object.hpp:8, from ./boost/python/import.hpp:8, from libs/python/src/import.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/import.o" "libs/python/src/import.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/import.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/exec.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/ssize_t.hpp:9, from ./boost/python/object.hpp:8, from ./boost/python/exec.hpp:8, from libs/python/src/exec.cpp:6: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/exec.o" "libs/python/src/exec.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/exec.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/function_doc_signature.o In file included from ./boost/python/detail/prefix.hpp:13, from ./boost/python/converter/registrations.hpp:8, from libs/python/src/object/function_doc_signature.cpp:9: ./boost/python/detail/wrap_python.hpp:75: fatal error: patchlevel.h: No such file or directory compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DBOOST_PYTHON_STATIC_LIB -DNDEBUG -I"." -I"/usr/include/python2.6" -c -o "bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/function_doc_signature.o" "libs/python/src/object/function_doc_signature.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi/object/function_doc_signature.o... ...skipped <pbin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi>libboost_python.a(clean) for lack of <pbin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi>numeric.o... ...skipped <pbin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi>libboost_python.a for lack of <pbin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi>numeric.o... ...skipped <pstage/lib>libboost_python.a for lack of <pbin.v2/libs/python/build/gcc-4.4.5/release/link-static/threading-multi>libboost_python.a... ...failed updating 58 targets... ...skipped 12 targets...

2 1

[shifted_ptr] Documentation
by Phil Bouchard 11 Apr '11

11 Apr '11

Greetings, There is more to come but I just documented the main classes of the Shifted Pointer code. To generate & look at the docs simply use: $ cd shifted_ptr/ $ svn up $ cd libs/smart_ptr/doc $ doxygen $ firefox html/index.html Some people like and some people dislike Doxygen but in my opinion it keeps the docs and the code in perfect harmony and requires no duplication of the function names and parameters. Bests, -Phil

5 20

BoostCon 2011: Registration deadline is Wednesday
by Dave Abrahams 10 Apr '11

10 Apr '11

The premier annual US C++ event, BoostCon, runs May 15-20, 2011 in beautiful Aspen, Colorado! See http://boostcon.boost.org for details. Hans Boehm, the father of C++ garbage collection and the C++0x threading model, headlines the fifth annual Boost Conference, with his keynote, "Threads and Shared Variables in C++0x." Other sessions about which which I'm personally excited: * Christopher Kohlhoff, the author of ASIO, is coming all the way from the "land down under" to present his library, slated for TR2. Also IPv6, and more! * Bartosz Milewski is going to talk about the relationship between C++ template metaprogramming and Haskell * Matt Calabrese presents his library implementation of the postponed C++0x concepts features Further topics include Unicode, lockfree programming, Boost.Units, compile-time graphs, database mapping, high-performance numerics, and... too many other good things to list. I'll be running a daily infrastructure workshop where we'll develop the frameworks for documentation, web services, build, test, packaging and distribution of C++ components, including ryppl. As usual, the best things about BoostCon are the people and the work that gets done between sessions. The pictures at http://boostcon.boost.org/photos/ give a pretty good sense of it, but there's truly no substitute for being there. If you haven't registered yet, fix that :-) at http://boostcon.boost.org/registration/. Your chance to save $100 expires on Wednesday. See you there! -- Dave Abrahams BoostPro Computing http://www.boostpro.com

3 5

[GSOC]Proposal withdrawn
by Faiçal 10 Apr '11

10 Apr '11

Hello I made a big mistake when submitting my proposal. On April 8, I was not able to see my proposal in the proposal list, so I click the button "Withdrawn" (as suggested in the gsoc mailing list) to after resubmit a new one. But nothing happens so I submit again but it seems that nothing happens again because my proposal status is now "withdrawn". Can I have a chance to resubmit ?

1 0

help with including boost.log into the current trunk
by Bernd Prager 10 Apr '11

10 Apr '11

I would appreciate some help in including the logging libs into the boost compilation process. I am using the recent SVN trunks, Cygwin 1.7.9 and g++ (GCC) 4.3.4. Unfortunately there is nor README or INSTALL docs as I am used to in a GNU automake environment. So I tried my best based on what I found google-ing it: I downloaded the current boost SVN trunk and the current boost-log SVN trunk. Then I linked the log directories into the boost trunk: $ ln -s boost-log/trunk/boost-log/libs/log/ boost-trunk/libs/ $ ln -s boost-log/trunk/boost-log/boost/log/ boost-trunk/boost/ Compiling boost with normal ./bjam does not recognise the log components at all: ... Component configuration: - chrono : building - date_time : building - exception : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - system : building - test : building - thread : building - wave : building ...patience... Explicitly including it gets me an error message: $ ./bjam.exe target-os=cygwin --with-log error: wrong library name 'log' in the --with-<library> option. What am I missing? Is there an easier way to do it? Thanks a lot for any help. -- Bernd

3 2

Proposed Library Boost.Algorithm
by Marshall Clow 09 Apr '11

09 Apr '11

(Finally) I have uploaded to the vault <http://www.boostpro.com/vault/index.php?action=downloadfile&filename=Boost.…> a proposal for the Boost.Algorithm library. This has been a matter of interest and discussion for a long, long time. Some of this code was written during the "Library in a week" session at BoostCon 2008. More was written last summer after this year's BoostCon. There is no way that I can write and submit all the algorithms that people want/need/are interested in, so I am proposing to set up a system by which people can submit algorithms to be included in the library, and have them reviewed, much like how new libraries are reviewed for acceptance into boost. The difference will be that a new algorithm is generally a much smaller piece of code than a new library, so hopefully we can lower the barrier to getting small pieces of code into Boost. So, what's in this proposal? 1) Three search algorithms: Boyer-Moore, Boyer-Moore-Horspool and Knuth-Morris-Pratt. (search.hpp) 2) A set of predicates for determining if a sequence is ordered (by some criteria) (ordered.hpp) Originally written by Grant Erickson during the "Library in a week" session at Boostcon 2008, and reworked somewhat by myself. 3) A set of predicates for determining other properties of a sequence, based on some suggestions for C++0x. (all.hpp) 4) An algorithm for restricting a value between two endpoints (clamp.hpp) And, of course, test cases and documentation. -- Marshall

6 13

Re: [boost] [lexical-cast] version of lexical_cast in 1.46.1 is quite older than in trunk
by Antony Polukhin 09 Apr '11

09 Apr '11

> On Wed, 2011-03-30 at 18:16 +0300, Matthew Chambers wrote: >> Does that mean lexical_cast is orphaned? I'd like to see lexical_cast have optimized conversions for >> string->number and number->string (template specializations using strtol/strtod; or optionally using >> the spirit-based construe_cast). Being able to pass ios flags to control the format (i.e. boolalpha) >> would be nice too [...] >> Which reminds me - lexical_cast error messages are not very >> informative[...] > >Agreed. This should be added as well[...] > >-Matt Added some optimizations for casts to integral types ( you can see them in tickets #5417 and #5350). Did not used strtol/strtod (it will be hard to implement tags/ios flags if we`ll use them, hard to detect overflows), did not used spirit library (it`s too big, includes too many files, and looks like it`s API changes often). Alexander Nasonov wrote: >Stewart, Robert wrote: >> Not true. You and others will benefit from the patches. First, they can be applied manually to local Boost installations, even if they aren't part of a Boost release. Second, others, with commit permission, can apply the patches even without an active maintainer if they are sufficiently comfortable with doing so (and there's enough noise to get their attention). Besides, you could volunteer to be the maintainer! > >No objections from me (the current maintaier). I don't have time for >this any more. > >Alex If there will be no active maintainer, I`d like to have at least commit permissions to lexical_cast library (if nobody has objections). I`ve got some ideas on implementing tags/ios flags and there are some more possible optimizations for float types and locales usage. So, is there any volunteers to be the maintainer? - Antony

5 10

Re: [boost] [range] for_each and std::map of std::list
by Jeremy Maitin-Shepard 09 Apr '11

09 Apr '11

On 04/07/2011 04:39 AM, Mathias Gaunard wrote: > On 07/04/2011 12:56, Thorsten Ottosen wrote: > >> Well, that is only a problem if you want to avoid manually applying the >> adaptor twice (or more), right? >> >> If so, I think that is a limitation we can live with. A simple solution >> covers most cases IMO. > > Oh, the adaptor I wrote flattens recursively. > > I guess just flattening the top level could be fairly easy. You could also require that the user specify the number of levels of recursion explicitly, as in many cases the final value_type you want to iterate over may be a range itself. Consider, for instance, that a string is itself a range of characters, but in many cases the user would not want to flatten a range of strings into a range of characters.

4 3

GSoC 2011,Graph library
by Sultana Rashid 09 Apr '11

09 Apr '11

I am Mariya Zaman.I am in the 6th semester in Bangladesh University of Engineering and Technology.My subject is CSE. I study a lot about your libraries.I saw ideas on graph in 2010 GSoC.I had studied graph theory,algorithm engineering.One of my interests is planar graph. I have found that some features may be added in your graph library.As: 1. For max flow and min cut Ford-Fulkerson and Dinitz Blocking Flow algorithms. 2. Fow min cut, the library has only Stoer Wagner algo.There are several randomized algo with high success rate as Krager's contraction or Recursive Contraction algo.These can be added. 3. Check if a graph have an Euler tour and find one and/or all possible Euler tours. 4.There are nine algorithms implemented on Planar Graph.We can implement some more algorithms as there exists a lot of algorithms on it. I have details plan on every topic.So I am just curious if you are interested in these types of algorithms.I thought you might be interested.So if you express interest on any topic,please let me know.I am eager to send you details. Thanking You, Mariya

3 2

[network] cpp-netlib v0.9-beta out now!
by Dean Michael Berris 09 Apr '11

09 Apr '11

Hi Everyone, Apologies for the cross-post, but I just want to announce that after a couple months delay because of some outstanding bugs and TODO items that needed to get dealt with, I am now ready to package a 0.9 release and with that in mind I've just uploaded the 0.9-beta release of cpp-netlib. When the beta period (1 week) is over and all outstanding bugs are addressed, the 0.9 release will be the basis for submission for review to the Boost C++ Library. You can get the beta from: https://github.com/cpp-netlib/cpp-netlib/downloads What's New in 0.9 (taken from the documentation): - IMPORTANT BREAKING CHANGE: By default all compile-time heavy parser implementations are now compiled to external static libraries. In order to use cpp-netlib in header-only mode, users must define the preprocessor macro BOOST_NETWORK_NO_LIB before including any cpp-netlib header. This breaks code that relied on the version 0.8.x line where the library is strictly header-only. - More consistent message API for client and server messages (request and response objects). - Refactoring of internal implementations to allow better separation of concerns and more manageable coding/documentation. - Client and Server constructors that support Boost.Parameter named parameters. - Client and Server cosntructors now take in an optional reference to a Boost.Asio io_service to use internally. - Documentation updates to reflect new APIs. This Beta has been tested mainly on Linux (GCC 4.4, 4.5) and Mac OS X (10.6.7, Xcode 3.2.x w/ GCC 4.2.1) builds against Boost trunk and Boost 1.45. Note that cpp-netlib does NOT work with Boost 1.46.1 because of some breaking changes in the Boost.Spirit customization points have caused cpp-netlib to cease to play well with it. That said, the issues have been addressed in Boost trunk and should be fixed in Boost.147. Thanks to everyone who contributed to making this Beta possible, namely Emre Turkay, Oleg Malashenko, and other users that filed issues on the Github issue tracker. Have a good day everyone and I do look forward to feedback! -- Dean Michael Berris http://about.me/deanberris

2 4

[context] missing part
by Oliver Kowalke 09 Apr '11

09 Apr '11

Hi, my previous message was incomplete - sorry: The modifications requested by the reviewers are incorporated into boost.context - available at git://git.gitorious.org/boost-dev/boost-dev.git (branch context-dev) @Vicente: I've send you several emails without response - possibly your ISP filters my emails (SPAM)? regards, Oliver - context: - stack unwinding: bool context::finished() const indicating that the called function has finished -> stack already unwinded void context::unwind_stack() jump back into context and throw a special exception -> stack will be unwinded (requires that no try/catch(...) was used) - context is now moveable - is not a template == the stack type is only passed/known in the templated ctor - the function to be called by the context is not saved on top of the stack - exceptions replaced by assertions / exceptions.hpp removed - fcontext_t used as default implementation; ucontext_t only fallback for platforms not supported by fcontext_t - on Windows Win Fiber API is used as default - protected stack: - keyword explicit added to ctor - public static members min_stacksize, max_stacksize, default_stacksize - fcontext_t renamed to boost_fcontext_t, boost_fcontext_get(), boost_fcontext_set(), boost_fcontext_jump(), boost_fcontext_make() -> move into global namespace - i386 ASM preserves SSE2 control/status word - x86 ASM uses indirect jump for boost_fcontext_set() and boost_fcontext_jump()

1 0

[phoenix] typo in doc
by Thomas Klimpel 09 Apr '11

09 Apr '11

In Table 1.7. Iteration Algorithms on <http://www.boost.org/doc/libs/1_46_1/libs/spirit/phoenix/doc/html/phoenix/a…> This first line of the table reads: for_each(r, c) for_each(begin(r), end(r), f) but I guess it should be: for_each(r, f) for_each(begin(r), end(r), f) Regards, Thomas

2 1

[QNX] Which macro to identify QNX operating system?
by Beman Dawes 08 Apr '11

08 Apr '11

Does anyone with QNX experience know if __QNX__ or __QNXNTO__ is preferred? Both are used in Boost code. Does it matter? Are the impacts the same for both GCC and Intel compilers? Are any other compilers used on that platform? For example, Watcom? --Beman

1 1

Re: [boost] [Boost][GSoC] Checks and hashes proposal
by Pierre Talbot 08 Apr '11

08 Apr '11

Well, I just modify the "specifics" because I don't have time to re-structured all the proposal. Thank you for those precisions. I join the skeleton library I coded few days ago. EDIT : I couldn't join it because the message exceed 75KB, so I uploaded it, please download the file with the following link : http://www.mediafire.com/file/0odobkg11p2uvda/checks_hashes_project.zip 2011/4/8 Pierre Talbot <pierre.talbot.6114(a)herslibramont.be> > Well, I just modify the "specifics" because I don't have time to > re-structured all the proposal. > > Thank you for those precisions. > > I join the skeleton library I coded few days ago. > > > 2011/4/8 Scott McMurray <me22.ca+boost(a)gmail.com> > >> On Fri, Apr 8, 2011 at 07:19, Pierre Talbot >> <pierre.talbot.6114(a)herslibramont.be> wrote: >> > >> > I wrote my proposal and posted it on the GSoC website, any feedbacks or >> > comments are welcomed. >> > >> >> You mix four distinct things in one: ISBN/EAN/VISA/etc, for catching >> human-entry errors; hash functions as in hash tables, which only care >> about distribution; checksums like CRC32, for catching data >> transmission errors; and cryptographic hash functions, the only ones >> useful against malicious adversaries. >> >> The summer is short, and the boost process is long. I'd encourage you >> to look only at the first category. As you mention, it's the one with >> the fewest alternative libraries, so you won't have to prove >> competitive performance and such, and there are no real security >> issues to deal with. >> >> Also, I'd like to see some sketches of interfaces. What do you expect >> user code to look like? >> >> A few specifics: >> >> "This kind of drama situation can be avoided by storing encrypted >> passwords." >> Encrypted means cyphers, not hashes. You want digests or MACs of >> passwords, not something reversible. >> >> "Write, test and document the hash functions MD5 and SHA-1 256 bits." >> There's no such thing as 256-bit SHA-1. Do you mean SHA-256, from >> "SHA-2"? >> >> Also, MD5, SHA-1, and SHA-2 are implemented in my hash library: >> <http://svn.boost.org/svn/boost/sandbox/hash/boost/hash/md5.hpp> >> <http://svn.boost.org/svn/boost/sandbox/hash/boost/hash/sha1.hpp> >> <http://svn.boost.org/svn/boost/sandbox/hash/boost/hash/sha2.hpp> >> >> ~ Scott >> _______________________________________________ >> Unsubscribe & other changes: >> http://lists.boost.org/mailman/listinfo.cgi/boost >> > >

1 0

[Boost][GSoC] Checks and hashes proposal
by Pierre Talbot 08 Apr '11

08 Apr '11

Hello, I wrote my proposal and posted it on the GSoC website, any feedbacks or comments are welcomed. http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/trademar… Thank you. Pierre Talbot.

2 1

[gsoc] JSON?
by Rene Rivera 08 Apr '11

08 Apr '11

Students and other interested parties, I would love it if there was a Boost quality JSON data parser, and optional printer, library. Currently I use one based on Spirit1 which has many drawbacks. I've been waiting for someone in the Spirit team, i.e. Joel, to have some mythical free time and inclination to write such a thing. But I'd really love one sooner, rather than later. Having one that is good and based on the latest Spirit would be wonderful. I can't say I have the time to mentor such a project. Hence this is just a though ;-) -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail

9 14

[GSoC] NLP Idea for GSoC 2011 project
by Sarma Tangirala 08 Apr '11

08 Apr '11

Hello list, I have worked with Boost on my projects but haven't really thought of using C++ as a language for NLP. The NLP that I have done is on Python and Java, for their built-in string methods. I don't know if this is inexperience or ignorance, but does C++ work well for NLP? I was thinking of having a GSoC project that is devoted to provide support for NLP. I mean like the kind that looks real easy on python. Also, I was looking at some C++ code using Boost/tokenizer.hpp that tokenized some text and it looked a bit scary. Any suggestions or advice? -- Regards, Sarma Tangirala, Junior - Class of 2012, Department of Information Science and Technology, College of Engineering Guindy - Anna University

4 9

[con] Links to BoostCon2009, session material
by Joachim Faulhaber 08 Apr '11

08 Apr '11

Hi, I tried to refer to some session material from BoostCon2009 under the link where it was available once: http://www.boostcon.org/community/wiki/show/Start/HandsOnCXX0x/ This link is broken, so I searched the new conference site: http://boostcon.boost.org/ Unfortunately I didn't find it there either. Are those session materials available somewhere else? Thanks, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de

1 1

lp solver GSOC proposal
by Chad Seibert 08 Apr '11

08 Apr '11

Hi, Just letting the community know that a draft version of my lp solver GSOC proposal can be found here: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/chadjsei… Any feedback would be greatly appreciated! Chad Seibert

2 2

Re: [boost] [Boost-users] Writing large binary files with boost gzip
by Steven Watanabe 08 Apr '11

08 Apr '11

AMDG On 04/07/2011 05:39 PM, Anders Knudby wrote: > Many thanks for the quick response. And apologies for being a total newbie, > but how do I close the stream (and how do I check that it has been closed)? > With normal iostreams I would just write "out.close();", out being the name > of the stream. But that doesn't seem to be the way to do it for > filtering_iostreams?!? It should be closed when it goes out of scope or when you call pop. > And I would think it would close when it goes out of > scope, but I haven't checked. Yes, the stream is closed when it goes out of scope. > Any help appreciated. I'm pleased it worked > for you on Linux, but I'm largely stuck with Windows for the time being... > I can try it on Windows, but it'll take a little bit, as I don't have zlib installed, right now. In Christ, Steven Watanabe

1 0

[phoenix] Functions and function pointers
by Lorenzo Caminiti 07 Apr '11

07 Apr '11

Hello all, How do I call functions and function pointers from within a Boost.Phoenix lambda function? For example: #include <boost/spirit/include/phoenix.hpp> #include <iostream> #include <vector> #include <algorithm> #include <cassert> #define N 1e4 #define S N * 1e2 const double& id(const double& x) { return x; } int main() { using boost::phoenix::ref; using boost::phoenix::arg_names::_1; double sum = 0.0; int factor = 1; const double& (*f)(const double&) = &id; std::vector<double> v(S); std::fill(v.begin(), v.end(), 1.0); for (size_t n = 0; n < N; ++n) { std::for_each(v.begin(), v.end(), ( ref(sum) += id(factor * f(_1)) // <<<<<<<<<<<<<< how do I call id(...) and f(...)? )); } std::cout << sum << std::endl; assert(sum == N * S); return 0; } Thank you very much. -- Lorenzo

2 1

[optional] Incorrect example
by Ahmed Charles 07 Apr '11

07 Apr '11

http://www.boost.org/doc/libs/1_46_1/libs/optional/doc/html/boost_optional/… int x = 1 ; int& rx = x ; optional<int&> ora ; optional<int&> orb(x) ; ora = orb ; // now 'ora' is bound to 'x' through 'rx' *ora = 2 ; // Changes value of 'x' through ' ora'assert(x==2); Either the comment on the fifth line is wrong or the fourth line should construct from rx rather than x.

1 0

[context] future design
by Oliver Kowalke 07 Apr '11

07 Apr '11

Hello, modifications I've made: - context: - stack unwinding: bool context::finished() const indicating that the called function has finished -> stack already unwinded boid context::unwind_stack() jump back into context and throw a special exception -> stack will be unwinded (requires that no try/catch(...) was used) - context is now moveable - is not a template == the stack type is only passed/known in the templated ctor - the function to be called by the context is not saved on top of the stack - exceptions replaced by assertions / exceptions.hpp removed - fcontext_t used as default implementation; ucontext_t only fallback for platforms not supported by fcontext_t - on Windows Win Fiber API is used as default - protected stack: - keyword explicit added to ctor - public static members min_stacksize, max_stacksize, default_stacksize - fcontext_t renamed to boost_fcontext_t, boost_fcontext_get(), boost_fcontext_set(), boost_fcontext_jump(), boost_fcontext_make() - i386 ASM preserves SSE2 control/status word - x86 ASM uses indirect jump for boost_fcontext_set() and boost_fcontext_jump() code is available at git://git.gitorious.org/boost-dev/boost-dev.git branch context-dev. @Vicente: could you check your SPAM filter , please (I've send several eMails to you). best regards, Oliver

1 0

Re: [boost] [range] for_each and std::map of std::list
by Thorsten Ottosen 07 Apr '11

07 Apr '11

Den 07-04-2011 11:37, Mathias Gaunard skrev: > On 06/04/2011 19:55, Thorsten Ottosen wrote: >> I suggest the syntax >> >> rngOfContainers | boost::adaptors::flattened >> >> and the underlying iterator should be up to bidirectional (if the >> underlying two container types support it). >> >> Anyone interested in implementing this? > > I have an implementation of this somewhere. > > One annoying thing is that you cannot detect that a type is a range > reliably. Well, that is only a problem if you want to avoid manually applying the adaptor twice (or more), right? If so, I think that is a limitation we can live with. A simple solution covers most cases IMO. -Thorsten

1 0

mismatched versions of Boost.Build engine and core
by Paul A. Bristow 07 Apr '11

07 Apr '11

I've got this message after running a bjam warning: mismatched versions of Boost.Build engine and core warning: Boost.Build engine (bjam) is 03.1.19 warning: Boost.Build core (at I:/boost-trunk/tools/build/v2) is 2011.04-svn Should I worry about this? I've tried to re-build using I:\boost-trunk\tools\build\v2\engine>bjam --toolset=msvc >build_bat.log but it still complains ### No toolset specified. Please use --toolset option. Is this supposed to be --toolset=msvc or --toolset msvc Suggestions? Thanks Paul PS This bit of the doc didn't seem right be me "For the Boost.Jam source included with the Boost distribution the jam source location is BOOST_ROOT/tools/jam/src." and was suggesting running build.bat I:\boost_1_46_0\tools\build\v2\engine\src contained build.bat and build.jam --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

4 4

Re: [boost] [shifted_ptr] Review Request
by Olaf van der Spek 07 Apr '11

07 Apr '11

On Wed, Apr 6, 2011 at 7:22 PM, Phil Bouchard <phil(a)fornux.com> wrote: > > > On 4/6/2011 9:58 AM, Olaf van der Spek wrote: >> >> What version of Boost was used? > > 1.34.1 > >> Does it use make_shared? > > No. Not very meaningful either, I'm afraid.

3 2

[shifted_ptr] Review Request
by Phil Bouchard 06 Apr '11

06 Apr '11

Greetings, For those who are not aware in 2008 I wrote a memory manager running in real-time so that heap objects are being destructed instantly. A quick introduction can be found here: https://svn.boost.org/svn/boost/sandbox/shifted_ptr/libs/smart_ptr/doc/Shif… The library still needs more documentation but we can see the simplicity of its usage in its examples found in the sandbox. Here's a quick copy & paste compilation of the examples: $ svn co http://svn.boost.org/svn/boost/sandbox/shifted_ptr $ cd shifted_ptr/libs/smart_ptr/example $ make shifted_ptr_test1 $ make t100_test1 $ ./shifted_ptr_test1 $ ./t100_test1 "shifted_ptr_test1" shows its versatility and simplicity while "t100_test1" shows a more complicated application on a neural network. I would like to request a review while I add the necessary documentation for a better support. Thanks, -Phil

8 30

Re: [boost] Python 3.2: convert convert PyObject* to PyUnicodeObject*?
by Ralf W. Grosse-Kunstleve 06 Apr '11

06 Apr '11

Thanks for the patch and the pointer. I just checked in the fix and closed the ticket. Ralf ----- Original Message ----- > From:Matthew Bradbury <matt-bradbury(a)live.co.uk> > To:boost@lists.boost.org > Cc: > Sent:Wednesday, April 6, 2011 3:43 AM > Subject:Re: [boost] Python 3.2: convert convert PyObject* to PyUnicodeObject*? > > Steve M. Robbins <steve <at> sumost.ca> writes: > > > > > Hi, > > > > Boost 1.46.1 fails to build with Python 3.2 on linux (Debian). The > > build fails with: > > > > error: cannot convert -F�PyObject*� to �PyUnicodeObject*� for argument �1� > to > �Py_ssize_t > > PyUnicodeUCS4_AsWideChar(PyUnicodeObject*, wchar_t*, Py_ssize_t)�-A > > > > at this code: > snip > > > > Is there an easy fix? > > > > Thanks, > > -Steve > > > Yes, I submitted a bug and a patch some time ago. > > https://svn.boost.org/trac/boost/ticket/4994 > > Matt > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [boost] [range] for_each and std::map of std::list
by Thorsten Ottosen 06 Apr '11

06 Apr '11

Den 06-04-2011 16:03, Mark Snelling skrev: > Hi, > > Consider a map defined as... > > std::map< int, std::list< std::string > > my_map; > > I'm wondering if/how it's possible to use Boost.Range to call a function > on each std::string in each of the lists contained in the map. I have an > implementation below which works using a C++0x lambda function but am > curious if this can be done purely using Boost.Range? > > boost::for_each( > boost::adaptors::values( my_map), > []( const std::list< std::string >& my_list ) { boost::for_each( > my_list, some_func ); } ); > > ideas anyone? What we need is a generic range adaptor that can make a container of containers look like a "flat" sequence. I suggest the syntax rngOfContainers | boost::adaptors::flattened and the underlying iterator should be up to bidirectional (if the underlying two container types support it). Anyone interested in implementing this? -Thorsten

2 2

Python 3.2: convert convert PyObject* to PyUnicodeObject*?
by Steve M. Robbins 06 Apr '11

06 Apr '11

Hi, Boost 1.46.1 fails to build with Python 3.2 on linux (Debian). The build fails with: error: cannot convert -F�PyObject*� to �PyUnicodeObject*� for argument �1� to �Py_ssize_t PyUnicodeUCS4_AsWideChar(PyUnicodeObject*, wchar_t*, Py_ssize_t)�-A at this code: static std::wstring extract(PyObject* intermediate) { std::wstring result(::PyObject_Length(intermediate), L' '); if (!result.empty()) { int err = PyUnicode_AsWideChar( intermediate , &result[0] , result.size()); if (err == -1) throw_error_already_set(); } return result; } Is there an easy fix? Thanks, -Steve

3 2

[config] Boost PP and variadic macros
by Edward Diener 06 Apr '11

06 Apr '11

This is largely directed to John Maddock, the maintainer of config, but of course anyone else can respond who is interested. I have been working to integrate my VMD library, and essentially variadic macro support, into Boost PP, with help and discussion offline of Paul Mensonides. I am now at the testing phase and all is now going well. This is currently being done in a separate library but when Paul and I are satisfied we intend to update the trunk with our changes. The library is at https://svn.boost.org/svn/boost/branches/pplib/variadics. One problem that I have can be explained by the fact that Boost PP currently does not depend on any other Boost library, not even Boost config. The reason for this is that Boost PP has been designed to work with C compilers ( or C++ compilers in C mode ) as well as C++ compilers. This means that the code to detect variadic macro support in Boost is duplicated in two places, both in config, which I basically started with the blessing of John Maddock with the BOOST_NO_VARIADIC_MACROS macro, and in Boost PP in a configuration file which I have coded and essentially duplicates the code in config for variadic macro support. I do not like this. Duplicating functionality in two different places, even as simple as determining variadic macro support for compilers, is error prone and a maintenance problem. Changes in one place have to be done in the other, and this would need to constantly be tracked. My initial thought was to see if config could work with C compilers, but all investigation there has led me to believe that it would be too many unnecessary changes to config, would complicate config greatly, would need extensive testing against all compilers, and that since config is central to all of Boost such a potential massive change to it it is a bad idea. So my current thought is to remove the code in config which tests for variadic macro support for a given compiler, to determine if BOOST_NO_VARIADIC_MACROS should be set, into a separate header file for each compiler which might set BOOST_NO_VARIADIC_MACROS, and then #include that header file in the compiler's header file, at the place where currently the setting of BOOST_NO_VARIADIC_MACROS exists ( or possible at the end ). The separate header file itself for testing variadic macro support is easily C compatible and I could use it in my Boost PP configuration file. This would eliminate duplication of the code to test for variadic macro support in config and Boost PP while keeping the goal of allowing Boost PP to still work with C compilers. Is this possible/desirable as far as config goes ? It would only affect the current code for setting BOOST_NO_VARIADIC_MACROS, hardly a Boost world-shaking event, and can easily be done by me and tested in regression tests. If it is, one further consideration is that the code in the Boost PP configuration file still would have to internally duplicate the checking and order of each compiler in the 'select_compiler_config.h' in config, but this is at least much better, and much less of a maintenance problem for Boost PP, than having to duplicate the code for checking for variadic macro support itself. Even this could be worked around, with a probably undesirable change to 'select_compiler_config.h', which I will proceed to suggest nonetheless. If we could add to that file another set of #defines for the corresponding variadic macro checking header file for each compiler that needs it. Something like: #define BOOST_COMPILER_CONFIG_NVM "boost/config/compiler/somecompiler_nvm.hpp" then in my Boost PP config header file I could go: #include <boost/config/select_compiler_config.hpp> #ifdef BOOST_COMPILER_CONFIG_NVM #include BOOST_COMPILER_CONFIG_NVM #endif and I could then check BOOST_NO_VARIADIC_MACROS and this will work for C compilers ( 'select_compiler_config.hpp' itself has nothing related to C++ and should work with any C compiler AFAICS ). But I would understand that littering 'select_compiler_config.hpp' with another set of #defines just to satisfy my need in Boost PP may not be acceptable to the clean design of that file, even if it would eliminate my need to reduplicate its logic in the Boost PP configuration file for variadic macro support in Boost PP which I have created.

5 17

archive_exception causes Link failure serialization
by Paul A. Bristow 06 Apr '11

06 Apr '11

I am trying to rebuild an existing demo program for Johan Rade's nonfinite facets from François Mauger The program was previously tested with Boost 1.44, gcc 4.4.1, Linux/i686 (32bits) Using MSVC 10, it compiles OK, but fails to link. Can anyone gives me any clues what I am doing wrong? Thanks! Paul ------ Rebuild All started: Project: nonfinite_num_serialization, Configuration: Release Win32 ------ nonfinite_num_facet_serialization.cpp Searching libraries Searching C:\Program Files\Microsoft SDKs\Windows\v7.0A\lib\kernel32.lib: <snip> Searching C:\Program Files\Microsoft Visual Studio 10.0\VC\lib\libcpmt.lib: Searching I:\boost-trunk\stage\lib\libboost_serialization-vc100-mt-s-1_47.lib: Finished searching libraries Creating library J:\Cpp\MathToolkit\test\Math_test\Release\nonfinite_num_serialization.lib and object J:\Cpp\MathToolkit\test\Math_test\Release\nonfinite_num_serialization.exp Searching libraries Searching C:\Program Files\Microsoft SDKs\Windows\v7.0A\lib\kernel32.lib: <snip> Searching C:\Program Files\Microsoft Visual Studio 10.0\VC\lib\libcpmt.lib: Searching I:\boost-trunk\stage\lib\libboost_serialization-vc100-mt-s-1_47.lib: Searching C:\Program Files\Microsoft Visual Studio 10.0\VC\lib\LIBCMT.lib: Searching C:\Program Files\Microsoft Visual Studio 10.0\VC\lib\OLDNAMES.lib: Finished searching libraries nonfinite_num_facet_serialization.obj : error LNK2001: unresolved external symbol "public: __thiscall boost::archive::archive_exception::archive_exception( enum boost::archive::archive_exception::exception_code,char const *,char const *)" (??0archive_exception@archive@boost@@QAE@W4exception_code@012@PBD1@Z) J:\Cpp\MathToolkit\test\Math_test\Release\nonfinite_num_serialization.exe : fatal error LNK1120: 1 unresolved externals I have just rebuilt this library I:\boost-trunk\stage\lib\libboost_serialization-vc100-mt-s-1_47.lib. Library directory is I:\boost-trunk\stage\lib;$(LibraryPath) and appears to searching in the right lib file. Runtime library is /MT for release (I have also tried debug with similar results). The following includes are used in the demo program #include <boost/cstdint.hpp> #include <boost/serialization/nvp.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> #include <boost/archive/codecvt_null.hpp> Is there anywhere I should have told serialization/archive not to use exceptions?

1 0

[chrono] Interoperability with ICL and common concepts
by Joachim Faulhaber 06 Apr '11

06 Apr '11

Hi Vicente and Boost Chronoists, thank you for implementing Boost.Chrono! It's a very fine piece of software :) Currently I'm checking out the usage of chrono types with icl::intervals and interval containers. Obviously, using intervals of chrono::time_points or chrono::durations can be an important use case. Also ICL already works well with other date and time data types from boost data_time, so chrono's interoperability should be at least as easy. A problem here is, that Icl, while working instantly with built in data types (e.g. int, short, double or even int*), for other numeric types (e.g. boost::rational) or types "based on integral types" (e.g. data_time::ptime) I needed to provide adapter code. I think it'd be ideal, if boost libraries interoperated with each other just out of the box, of course. To achive this, we have to find a common understanding of those concepts, that make a seamless interoperability work. I think, this is important work to be done, because it widens the view from one's own library perspective to a broader horizon of generic interplay. The problem: There is a minimal set of requirements that Icl expects for the domain types of intervals and interval containers (1) A zero element, more precisely an identity element w.r.t. the type's composition operation, which usually is +. An assumption that works well for all built in types and many STL-types is, that we get this element by the default constructor T(). (2) A strict weak ordering < (3) For all discrete types and for continuous numeric types: Operators ++, -- (Only pre-variants needed e.g. ++x) (3.1) For discrete types ++/-- increments/decrements by a *least step* (3.2) For continuous numeric types ++/-- increments/decrements by a *unit step*. Most of the functionality of Icl works if requirements (1) through (3) are met. In addition, there are some functions that require a distance type, but only for more specific types, namely for numeric types that use varying interpretations of the origin (zero), like epoch based date and time and pointer-addresses. BTW, do we already have a name for this type of concept? origin_based_equidistant_scalar origin_based_equidifferential_scalar because they are based to an arbitrary origin, but have comparable differences or distances. Or shorter equidistant_scalar equidifferential_scalar because if we emphasize, that by "comparable differences or distances", it is implied that the origin is choosable. May favorite is "equidistant_scalar". This concept reminds me of "Levels of measurement" http://en.wikipedia.org/wiki/Level_of_measurement (4) For such equidistant scalar types D the ICL assumes, that the type of the difference values of D is D::difference_type. To summarize, for a domain type Dom, Icl expects Dom(), <, ++, -- and if dom is a equidistant scalar type we expect an associated type Dom::difference_type to be defined. Now boost::chrono::duration (D1*) Has a default ctor that leaves the type undefined. (D2) Has <, Ok. (D3) Has ++, --, Ok. boost::chrono::time_point (T1) Has a default ctor that implements the semantics assumed by the ICL, Ok. (T2) Has <, Ok. (T3*) Does not have ++, --. (T4*) Does not have difference_type So I end up with 3 of my requirements not met (D1, T3, T4) D1: Default ctor for chrono::duration leaves objects undefined. I assume this is due to efficiency considerations, nevertheless unfavorable from the view point of my library. For all built in types and most of the STL there has been something like an intuitive maybe unconscious may be conscious agreement to assign the identity element w.r.t. the fundamental composing operation of the constructed object's type as the semantics of the default ctor. From an algebraic, generic and interoprability point of view (and IMHO) this is the best choice. This choice has not been taken for chrono::durations, which is a little inconsistent also, because interestingly for its chrono::time_point type the semantic is just the desired one. The possibility of default ctor customization is no remedy, because ICL should ideally be completely "chrono agnostic" and still interoperable. For the same reason duration::zero() is not an option. T3: chrono::time_point does not implement ++ and --. I assume this is because of the specific maths that is designed for chrono::time_points (P) and durations (D) where - : P x P -> D + : P x D -> P + : D x P -> P but + : P x P -> P //verboten But this should not be an argument against ++ and -- because the "least steppable unit" for integral rep types as well as the "unit" for floating point rep types, that is processed by ++ and -- is the same for time_points and durations. T4: Finally, difference_type as the associated type for time_point is not defined. IMO, it should be, because from a concept point of view, chrono::time_point falls in the same equidistant scalar concept that other types are in (e.g. T*, random_access_iterator<T>) and those associate a difference_type. These are the main problems of Icl/Chrono interoperability. There are a few minor ones as well. Let's discuss these first. I hope we can arrive at a solution, where Icl can be chrono agnostic and vica versa and still everything works well together. Based on that, we could fix similar issues for other libs like data_time. Cheers, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de

5 38

more details on the project idea Boost.Polygon edge, polyline and edge set concepts for GSOC 2011
by arunesh vikram 06 Apr '11

06 Apr '11

can i get more details on what topic you want me to emphasize on.... for this project like what should i know or requirements for this project. eagerly waiting for your reply...... Arunesh vikram

2 1

Re: [boost] Student introduction - GSOC
by George Lucian CORLACIU 06 Apr '11

06 Apr '11

> > Hello, > > I hope is not too late to make my introduction and to express my interest > in 2 of the proposed ideas. > > 1. SIMD library > > 2. ConcepTraits library > > Please tell me if I can still apply, and if I can what should I do to > demonstrate my capabilities in order to get one of your slots in GSOC. > > > Short description: > > *About me* > > Name: George Lucian CORLACIU > > University: Universidad Politécnica de Madrid, Madrid, Spain > > Master: European Master on Software Engineering (Erasmus Mundus Programme > on Software Engineering) – 1st year > > Bachelor: University of Sibiu “Lucian Blaga”; Faculty of Engineering > “Hermann Oberth”, Computer Science Department (thesis - Designing and > developing a hardware + software system for creating panoramic pictures - > Grade 9.86) > > *Work experience* > > I have over three years work experience, almost one year as a Software > Tester for an automotive company where I used C and more than two years as a > Software Developer in a company where I was developing a Laboratory > information management system (LIMS), a web application in Asp.NET Ajax + > C#. > > *Coding ++* > > My coding skills, ordered by proficiency are: C#, C++, C, Asp.NET, Java, > ASM etc. > > Tools proficiency: Visual Studio, Builder, Eclipse etc. > > Taking some of the courses in the bachelor degree and master improved my > skills a lot in domains like: computer vision, compression, image > processing/compression, cryptography etc. > > > Regards, > > George Lucian CORLACIU >

1 0

Re: [boost] [Filesystem] Linking problem with 1_46_1
by Max Moorkamp 06 Apr '11

06 Apr '11

>> > Max Moorkamp wrote: >> > >>> >> Hi, >>> >> >>> >> I have recently upgraded to boost 1_46_1 and since then I am experience >>> >> linking problems with the filesystem library. >>> >> >>> >> I have performed a standard install using ./bootstrap.sh; bjam; bjam >>> >> install under Ubuntu 10.04 with the default gcc (4.4.3). >>> >> >> > > I had some issues in my early attempts. My problem was with my libs > location, then I installed this way: > > > - $ ./bootstrap.sh --with-toolset=gcc --prefix=/usr/local > --includedir=/usr/include --libdir=/usr/lib > --with-libraries=system,date_time,thread,filesystem > - $ ./bjam > - # ./bjam install > > Before to do it even linking lboost_system and lboost_filesystem didn't > work. Thanks for that. However, the linker does find the boost_filesystem library. If I just do g++ test.cpp -lboost_system then I get some additional linker errors /tmp/cc10fHYI.o: In function `boost::filesystem3::path::codecvt()': test.cpp:(.text._ZN5boost11filesystem34path7codecvtEv[boost::filesystem3::path::codecvt()]+0x5): undefined reference to `boost::filesystem3::path::wchar_t_codecvt_facet()' /tmp/cc10fHYI.o: In function `boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)': test.cpp:(.text._ZN5boost11filesystem39copy_fileERKNS0_4pathES3_[boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)]+0x2a): undefined reference to `boost::filesystem3::detail::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&, boost::filesystem3::copy_option::enum_t, boost::system::error_code*)' collect2: ld returned 1 exit status so it seems that in the version I have just boost::filesystem3::detail::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&, boost::filesystem3::copy_option::enum_t, boost::system::error_code*)' is missing. Actually I just found one clue. If I do nm -Ca /usr/local/lib/libboost_filesystem.so | grep boost::filesystem3::detail::copy_file I get boost::filesystem3::detail::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&, boost::filesystem3::copy_option::enum_type, boost::system::error_code*) so the library uses boost::filesystem3::copy_option::enum_type, while the linker is looking for boost::filesystem3::copy_option::enum_t. This must have something to do with some preprocessor macro, but I can't figure out which one and why. Regards Max -- Max Moorkamp IFM-GEOMAR Wischhofstr. 1-3 24148 Kiel Tel.: Germany - 431 - 600 2570 FAX.: Germany - 431 - 600 2915

1 0

Re: [boost] [lexical cast] Performance improvements
by Vicente BOTET 05 Apr '11

05 Apr '11

> Message du 05/04/11 18:18 > De : "Antony Polukhin" > A : boost(a)lists.boost.org > Copie à : > Objet : Re: [boost] [lexical cast] Performance improvements > > >From Gruenke, Matt > > I`ve looked at Boost.Conversion library at sandbox/conversion/. The > idea is interesting, but: > > 1) > > char ch = '0'; > > std::cout << boost::lexical_cast(ch) << " " << > boost::numeric_cast(ch); > > This code will output "0 48" Good point. Thanks for this simple example. > We can not make your library output both values... There are some > tags, but in both cases it will be boost::dummy::type_tag (or > may be I didn`t get the idea) I have not tried that, but i guess that you could use different tags for different conversions. I'm not sure the following will compile (I will try soon) template struct lex { typedef T type; }; template struct num { typedef T type; }; template typename Target::type convert_to(Source const& v , boost::dummy::type_tag > const&) { return lexical_cast(v); } template typename Target::type convert_to(Source const& v , boost::dummy::type_tag > const&) { return numeric_cast(v); } Then you can use them as follows std::cout << boost::convert_to< lex >(ch) << " " << boost::convert_to< num >(ch); This code will output "0 48" This is a little bit artificial, but it could work in some contexts. Note that I'm not saying the library should be used in tis way. > 2) For each conversation user will need to write > convert_to function overload. It will be much better, > if user was required to write only one conversion function (to some > intermediate type), and the library will be able to convert to any > other type from intermediate type. There is already lexical_cast and Boost.StringConvert (to be reviewed soon) that use an intermediary type or mechanism. Boost.Conversion is intended to provide an interface for direct conversions which should be more efficient in most of the cases (as you have shown). If you know that two types are convertible using an intermediary type, you can use convert_to_via Target target = convert_to_via(source); > I use lexical_cast<>() a lot, so I`d better improve it first. I guess any improvement to lexical_cast that preserves the semantics will be welcome by the Boost comunity. Best, Vicente

1 0

Why Boost.Build?
by Gregory Crosswhite 05 Apr '11

05 Apr '11

Hey everyone, Is there a reason why Boost uses Boost.Jam/Boost.Build for reasons other than tradition? Does it have advantages over other build systems, in particular CMake (which I consider to be its main competitor)? Are there many people/projects who use Boost.Jam/Boost.Build outside of Boost? These questions are asked purely out of curiosity due to my ignorance of Boost.Jam/Boost.Build, not because I have an axe to grind. Cheers, Greg

23 43

std::tuple vs boost::tuple clashes in C++0x
by Christopher Jefferson 05 Apr '11

05 Apr '11

Just wanted to post a general comment, to boost library developers. There are lots of names which in C++0x occur in both boost:: and std::. The big ones are tuple, make_tuple and array, but there are others (for example locking functions from thread). I am fixing bugs which occur in the C++0x mode of clang/libc++, and the vast majority of these bugs are tests which write things like: ... using namespace boost; using namespace std; .... tuple<int,int> t; Even if you don't include <tuple>, a definition of tuple gets pulled in by <utility>, which almost everything includes. Please don't write "using namespace std; using namespace boost;" in boost tests. You probably shouldn't write it at all :) Chris

3 3

Re: [boost] GSoC Proposal Preparation For Encoding Awared String
by Artyom 05 Apr '11

05 Apr '11

> From: Soares Chen <crf(a)hypershell.org> > > Hi all, > > [snip] > > I think there are several options that I can choose for my project: > 1. To use Chad Nelson's code as base, try to incorporate other ideas > proposed in the mailing list, integrate with Boost.Locale, and make it > Boost quality to submit for review. If this option is chosen, I wish > that Chad Nelson can be my mentor. > 2. To start a new code base, gather and compile ideas suggested in > mailing list, final design decisions made by me and my mentor but not > the community (to keep the project going on fast), make it Boost > quality and submit for review. > 3. To start the boost::string project, where another better string is > reinvented and fix all the weaknesses of std::string. > 4. Adopt different proposal, and improve on existing project such as > Boost.Unicode [2] or Boost.Locale [3] such that it really solves the > encoding awareness problem. > 5. Any other suggestion? Hello, I want you to address several points: It would be very hard to get the consensus about the way to solve the problem. Probably the best and the most wishful thinking solution is to assume that all strings are UTF-8 based, however it is not the reality. The problem is actually not the string but rather the way you code. Even if you create a perfect UTF-8 string and then call fopen(your_perfect_string.c_str(),"r") Under windows... And it would not work <sigh... damn Windows> As you can see from multiple discussions, there are many contradicting requirements about how should string look like and what should it bring with. If you want to provide better Unicode awareness to Boost you don't need new cool utf-XYZ string, you need a policy. I think boost::filesystem v3 is a big step forward, it allows you to use UTF-8 strings on Windows which I think is a really good beginning. This is my opinion. Boost.Locale and several other my projects (CppCMS, CppDB) live happily with std::string. The problem is that in vast majority of cases you don't need encoding aware string, as so many operations you usually do on strings are encoding agnostic. But this is other story. Bottom line, if you want to improve Unicode awareness of Boost I think you need to adopt Boost.Filesystem v3 like policy all over the code base of Boost. 1. Use Wide API as native one in Boost everywhere under Windows 2. Use char * API as native one in Boost everywhere under non-Windows platforms 3. Use std::codecvt to handle this (after many tricks... ) The Unicode String/Encoding Aware String is the last thing to do not the first thing. Why? 1. Because you will never get the consensus about what is the "right-thing" to do (wide, narrow, utf-8, utf-16) etc. Project that are handled and directed by a single source or management like Qt, GTK(mm), Java, C#, Python or others may decide what is the right thing. This will never happen in Boost as it is too pluralistic even in cases where it does not always make sense, just because the way libraries are developed, reviewed and got in - based on public reviews that eventually encourages diversity. 2. Because you would not likely to be able to enforce users to actually use your string. As boost is more about collaboration then enforcement of specific style. 3. Even heavy discussions there hadn't got to any conclusion. So what would happen and final review of your library? My $0.02 Artyom

7 11

Re: [boost] [lexical-cast] version of lexical_cast in 1.46.1 is quite older than in trunk
by Antony Polukhin 05 Apr '11

05 Apr '11

Christopher Jefferson wrote: > On 4 Apr 2011, at 21:19, Antony Polukhin wrote: >> >> If there will be no active maintainer, I`d like to have at least >> commit permissions to lexical_cast library (if nobody has objections). >> I`ve got some ideas on implementing tags/ios flags and there are some >> more possible optimizations for float types and locales usage. > > If you are making modifications, there really needs to be someone who keeps an eye on the test results and bug reports to make sure nothing is broken. > > If you want to make some changes anyway,why not also be the maintainer? :) > > Chris I like your idea. But I need some information on how to maintain boost library and how to become a maintainer. - Antony

1 0

GSoC 2011(Weighted Voronoi Diagram)
by Sultana Rashid 05 Apr '11

05 Apr '11

Hello, I have mailed about some ideas on Boost Graph Librrary.I have gone through some libraries of Boost.I did not find Weighted Voronoi Diagram. I have studied and implemented it in C++.It might be interesting to you. Thanking You, Mariya

2 1

GSoC2011 proposal submitted : Community Detection Module
by Xu Sun 05 Apr '11

05 Apr '11

Hi, I have submitted the proposal about implementing a community detection module for BGL. Everyone is welcomed to give me a comment as the feedback. Details at: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/sunbow/1 Thanks, Xu Sun

1 0

Re: [boost] [lexical cast] Performance improvements
by Antony Polukhin 05 Apr '11

05 Apr '11

>From Gruenke, Matt >>From Vicente BOTET, on Mon 4/4/2011 5:59 PM: >> I think that it is better to improve my library that is there to manage with any conversion, and let lexical cast do what it did originally. >> Let me know what do you think. > >It didn't sound like he change the behavior of lexical_cast<>(), at all. I am very much in favor of these optimizations going in, since I have a large >amount of code which uses lexical_cast<>(). Yes, I did not changed the behavior of the library, but only added optimizations for some conversions, which sometimes occur when lexical_cast is used in generic programming. There are some more optimizations for lexical_cast in bug database (tickets #5417 and #5350) >From Vicente BOTET > Let me know what do you think. > > Best, > Vicente I`ve looked at Boost.Conversion library at sandbox/conversion/. The idea is interesting, but: 1) char ch = '0'; std::cout << boost::lexical_cast<int>(ch) << " " << boost::numeric_cast<int>(ch); This code will output "0 48" We can not make your library output both values... There are some tags, but in both cases it will be boost::dummy::type_tag<char> (or may be I didn`t get the idea) 2) For each conversation user will need to write convert_to<required_type> function overload. It will be much better, if user was required to write only one conversion function (to some intermediate type), and the library will be able to convert to any other type from intermediate type. I use lexical_cast<>() a lot, so I`d better improve it first.

1 0

[release][1.47] Release branch open + schedule
by Daniel James 05 Apr '11

05 Apr '11

Hello everyone, It's been over a week since the release, so it's time to open the release branch. Since we're running late, and we haven't discussed the changes to the schedule, and I think it helps people to pace their development, we should probably decide on a schedule for this release pretty quickly, and then discuss the schedule for future releases later. We discussed having longer betas, 4 weeks was suggested. If we do that this time, it'll leave a very small window for merging to release, so I think 3 weeks might be better. Something like: 4th April: Release branch closed for beta (bug fixes only). 11th April: Beta target date. 2nd May: Release target date. Note: That's just a proposal, not the actual schedule. It isn't up to me. That's still a tight schedule, maybe a shorter beta or a delayed release would be better. Any thoughts? Daniel

4 7

Re: [boost] [Filesystem] Linking problem with 1_46_1
by Max Moorkamp 05 Apr '11

05 Apr '11

> Max Moorkamp wrote: >> > Hi, >> > >> > I have recently upgraded to boost 1_46_1 and since then I am >> > experience linking problems with the filesystem library. >> > >> > I have performed a standard install using ./bootstrap.sh; bjam; bjam >> > install under Ubuntu 10.04 with the default gcc (4.4.3). >> > I can boil the problem down to this test program: >> > >> > #include<boost/filesystem.hpp> >> > #define BOOST_FILESYSTEM_VERSION 3 >> > #define BOOST_FILESYSTEM_NO_DEPRECATED >> > >> > int main() >> > { >> > boost::filesystem::copy_file("a", "b"); >> > } >> > >> > compiling this with >> > >> > g++ test.cpp -lboost_system -lboost_filesystem >> > > It might be as simple as the order you link to the libraries. The boost > filesystem library depends on the boost system library, so you should > probably put "-lboost_system" after "-lboost_filesystem" on the command > line to link your program. That was my first thought, but the linking error does not come from boost_system, plus all of g++ test.cpp -lboost_filesystem -lboost_system g++ test.cpp -lboost_system -lboost_filesystem g++ test.cpp -lboost_filesystem give the same /tmp/cc9OO6P2.o: In function `boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)': test.cpp:(.text._ZN5boost11filesystem39copy_fileERKNS0_4pathES3_[boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)]+0x2a): undefined reference to `boost::filesystem3::detail::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&, boost::filesystem3::copy_option::enum_t, boost::system::error_code*)' collect2: ld returned 1 exit status Regards Max -- Max Moorkamp IFM-GEOMAR Wischhofstr. 1-3 24148 Kiel Tel.: Germany - 431 - 600 2570 FAX.: Germany - 431 - 600 2915

1 0

[lexical cast] Performance improvements
by Antony Polukhin 05 Apr '11

05 Apr '11

Working with Boost Lexical Cast library found that some casts are working really slow. For example, cast from short to int is done via cast from short to char[], and cast from char[] to int. Cast from char* to string is done via string() constructor call and string`s append function call (instead of string constructor call with char array as a parameter). So I wrote patch to Boost Lexical Cast library, that returns Target directly constructed from Source in cases, when: 1) Source and Target are arithmetics (and not char or wchar_t), and all values of Source are in range of Target 2) Source and Target are both char or both wchar_t 3) Source is array of CharT and Target is std::basic_string<CharT, ...> 4) Source and Target are std::basic_string with same template parameters It gives performance boost more than 10 times in case 1) , about 7 times in case 2), and about 1.5 times in cases 3) and 4). Existing tests for Boost Lexical Cast library cover considered cases. Patch was successfully tested on Intel 11.1.072, g++-4.4.5, VC++9 compilers. P.S.: I`m a newbie here, so where shall I send this patch? Shall I test it on other compilers?

5 5

[Filesystem] Linking problem with 1_46_1
by Max Moorkamp 05 Apr '11

05 Apr '11

Hi, I have recently upgraded to boost 1_46_1 and since then I am experience linking problems with the filesystem library. I have performed a standard install using ./bootstrap.sh; bjam; bjam install under Ubuntu 10.04 with the default gcc (4.4.3). I can boil the problem down to this test program: #include <boost/filesystem.hpp> #define BOOST_FILESYSTEM_VERSION 3 #define BOOST_FILESYSTEM_NO_DEPRECATED int main() { boost::filesystem::copy_file("a", "b"); } compiling this with g++ test.cpp -lboost_system -lboost_filesystem results in this error message /tmp/ccBuSw7s.o: In function `boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)': test.cpp:(.text._ZN5boost11filesystem39copy_fileERKNS0_4pathES3_[boost::filesystem3::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&)]+0x2a): undefined reference to `boost::filesystem3::detail::copy_file(boost::filesystem3::path const&, boost::filesystem3::path const&, boost::filesystem3::copy_option::enum_t, boost::system::error_code*)' collect2: ld returned 1 exit status I had a look at this thread http://boost.2283326.n4.nabble.com/Filesystem-problems-with-g-std-c-0x-td26… but adding or removing -std=c++0x does not change anything. I also tried to see whether any special compiler options were used during the build of boost, so here is the line for operations.hpp "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/filesystem/build/gcc-4.4.3/release/link-static/threading-multi/v3/src/operations.o" "libs/filesystem/v3/src/operations.cpp" There is nothing there that strikes me as special, any ideas anyone. Regards Max -- Max Moorkamp IFM-GEOMAR Wischhofstr. 1-3 24148 Kiel Tel.: Germany - 431 - 600 2570 FAX.: Germany - 431 - 600 2915

3 2