- Boost - lists.boost.org

Patch for BOOST_OLD_IOSTREAMS detection
by Matthias Troyer 30 May '05

30 May '05

Hi, Several places in Boost try to detect BOOST_OLD_IOSTREAMS using the following ifdefs: // support for pre 3.0 libstdc++ - thanks Phil Edwards! #if defined (__STL_CONFIG_H) && !defined (__STL_USE_NEW_IOSTREAMS) # define BOOST_OLD_IOSTREAMS #endif This incorrectly defines BOOST_OLD_IOSTREAMS for the Cray X1 C++ compiler. Could this be changed to include an && !defined(__crayx1) or something similar as in: #if defined (__STL_CONFIG_H) && !defined (__STL_USE_NEW_IOSTREAMS) && !defined(__crayx1) # define BOOST_OLD_IOSTREAMS #endif Three offending files are: boost/dynamic_bitset/config.hpp boost/range/iterator_range.hpp libs/dynamic_bitset/example/timing_tests.cpp Maybe it would be best to move this to the global config file? Best regards Matthias

3 4

[BGL] Comparison with LEDA
by Sylvain Pion 30 May '05

30 May '05

You may find this comparison with some LEDA graph algorithms interesting : http://www.algorithmic-solutions.com/leda-outperforms-boost.htm -- Sylvain

1 0

[gauging interest] Windows GUI - semi-installer
by Pablo Aguilar 30 May '05

30 May '05

Hi, After reading the "Customer Friendlier Boost Installation" thread, I've now enough motivation to get into this... I've been planning a boost GUI semi-installer, but hadn't gotten around to it due to lack of time. I call it "semi" in the sense that it wouldn't be the typical "wizard like" installer everyone's used to, but rather a configuring utility for (at least) the IDEs I'm familiar with. Here's what I thought it should do: 1) Register include/lib directories with VCx 2) Don't know how yet, but try the same with BCB (as I think it's on a per-project basis, rather than global settings like VC) 3) Allow building of libraries which require it, with the following options: - Which compiler(s) to use? - Which configuration (debug/threading/static/etc) for each compiler? I believe that detecting which libraries need building would just be a matter of searching for a "build" subdirectory within a given library's directory. Don't know about configurations, though, maybe some simple parsing of the jamfiles would do.. The reason I chose not to do it as an installer, is because I'm far more comfortable with developing GUIs with say, BCB, than I am with the installer programs I've tried. Comments, suggestions, requests are welcome. Pablo Aguilar

5 18

[range] Borland and GCC-2.95 workarounds for iostreams
by Jonathan Turkanis 30 May '05

30 May '05

Hi Thorsten, I made two changes to range, which should only affect gcc-2.95 and Borland: - in begin.hpp and end.hpp I applied some of the Borland workarounds to gcc-2.95 as well - in iterator_range.hpp, I removed some Borland workarounds which were causing iostreams to fail on Borland, and which did not seem to be necessary. The same tests passed with and without the workarounds. Jonathan

2 6

[Typeof] Formal Review in progress
by Andy Little 30 May '05

30 May '05

Hi All, A reminder that the Typeof Formal Review is currently in progress and runs until May 30th. So far there have been only two reviews, both in favour of the library. (Thanks again to both those reviewers for their time and energy). Nevertheless it would be nice to get some more opinion, affirmation , etc regarding this important library. One area in particular that has been cited as worthy of improvement is the documentation, so please download the library and take a look at it. (And then write a review ;-) ) Are there enough examples? Is there enough information regarding how to use the library. Is it workable in a large project?. is the effect on compile time a problem.? etc. I'm sure that Arkadiy and Peder would welcome feedback on the documentation in particular so that they can improve it. So please try to find time to write a review. The proposed Typeof library emulates the functionality of the non-standard 'typeof' operator, and incomplete implementations of decltype and the proposed 'auto' declarator , described in http://www.osl.iu.edu/~jajarvi/publications/papers/decltype_n1478.pdf. It is commonly acknowledged that this type of functionality is sorely needed and should be standardardised in the language. For compliant compilers the library requires some help in the form of registration macros but, because use of typeof is by its nature most likely in generic libraries, it is expected that this can often be done by the library author rather than the user. In some cases the compilers capabilities (by means of extensions and even compiler bugs) have been used to remove the need for registration. However, for portability and in order to test emulation mode on the compilers where it is available but not used by default (VC7.1, GCC etc), #define BOOST_TYPEOF_COMPLIANT [see note *1*]. Testing the emulation is useful, even on compilers that provide a better option, to get a rounded view of the library and its capabilities. I hope you will find time to write a review of the library, which is available at: http://boost-sandbox.sourceforge.net/vault/ , typeof.zip The system has been tested with the following compilers: MSVC 6.5/7.0/7.1/8.0; [see note *1* regarding VC7.0 and VC6.5] GCC 3.4.2 (The following is a quote from : http://www.boost.org/more/formal_review_process.htm ) 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. Andy Little Typeof review manager notes: *1* MSVC6.5 and VC7.0 are not supported by the BOOST_TYPEOF_COMPLIANT macro

6 34

Typeof: Formal Review period ended
by Andy Little 30 May '05

30 May '05

Hi, The Typeof formal review period is closed. Thanks to all those that participated in the review. Thanks also to Tom Brinkman, the review Wizard. I hope to provide a more detailed summary of the review shortly, meanwhile I am happy to say that the Typeof library has been accepted into boost. regards Andy Little

1 0

Yet another quickbook question
by Arkadiy Vertleyb 29 May '05

29 May '05

Hi all, How do I generate the document-level index in the quickbook? Right now it generates indexes for those sections that contain subsections, but not the top-level index. Regards, Arkadiy

3 4

[parameter] Comments and concerns
by Cromwell Enage 29 May '05

29 May '05

1. For type extraction, the name "binding" is *much* better than the name "index_result". 2. With regard to the rvalue issue recently tackled by Dave Abrahams and Daniel Wallin: 2.1. In my projects, I seldom assign a possible rvalue to a const reference; I almost always use a const variable. The functions for which I require named parameters are initializer functions; that is, they build containers, graphs, mazes, etc. The cost of making even several copies of mostly primitive objects is negligible in comparison. 2.2. The handful of times I do bind an rvalue to a const reference, I don't even need the object; I just want its type, and the static functions associated with it. All in all, no problems here. 3. By default, most of the property maps used by the BGL are created in the following manner: make_iterator_property_map( std::vector<ValueType>( num_vertices(graph) ).begin() , index_map , ValueType() ); Assuming such a call is expensive enough that it should be a lazy default, the corresponding code (if I'm not mistaken) would be: typedef typename property_map<Graph,vertex_index_t>::type VertexIndexMap; ... typedef std::vector<ValueType> ValueVector; ... VertexIndexMap index_map = get(vertex_index_t(), graph); ... function_impl( graph , p[ some_named_parameter || bind( &make_iterator_property_map< typename ValueVector::iterator , ValueType , VertexIndexMap > , ValueVector(num_vertices(g)).begin() , index_map , ValueType() ); ] , ... ); 3.1. A new user may easily neglect to specify the template parameter types by naively expecting Boost.Bind to accept function templates just as it does ordinary functions. (I sure did.) This is not a Boost.Parameter issue per se, but if one expects to commonly use Boost.Bind to produce lazy defaults, perhaps a gentle warning would be in order. 3.2. BTW, according to <http://www.boost.org/libs/property_map/iterator_property_map.html>, ValueType and IndexMap should be the third and second template parameters, respectively. Should <boost/property_map.hpp> be fixed to match its documentation? 3.3. These are minor issues for me, but they may be major concerns for Doug Gregor, Jeremy Siek, et al. if they're revamping the BGL to use Boost.Parameter. 4. Ah, the joys of GUI programming... 4.1. Even the simplest WxWidgets program grinds to a halt when calling a function that uses the Boost.Parameter mechanism. The same goes for FLTK and FOX. 4.2. OTOH, Irrlicht <http://irrlicht.sourceforge.net/> gives full cooperation. The only apparent difference between this library and the others (aside from the fact that it is mainly a 3D library) is that it opens up a DOS box in the background. IIRC a similar concern was posted a while back, I think wrt Boost.Test + GUIs. 4.3. I haven't had the time to produce simple test cases. If you want them, let me know. Cromwell D. Enage __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 3

Synchronize Pointer (thread safe wrapper)
by Axter 29 May '05

29 May '05

Is there any interest in adding to the boost library a synchronized pointer class which is a thread safe wrapper class for an object instance. If so, please examine the following source code, and please post feedback. http://code.axter.com/sync_ptr.h http://code.axter.com/sync_ctrl.h Or you can download it from the boost sandbox. It's listed as sync_ptr.zip The following link has the source code for a test case application: http://code.axter.com/TestCaseAppforThreadSafeObject_sourcecode.zip

2 2

RE: [boost] Re: Collecting Users/Usage of Boost (was A more confrontingBoost (long))
by Brian Braatz 29 May '05

29 May '05

> -----Original Message----- > On Behalf Of Loïc Joly > David Abrahams a écrit : > > > I don't think we need to do that kind of diligence. If we have heard > > from someone who we have reasonable confidence works for the company, > > that should be enough. If a company asks us to, we can always remove > > mention from the site. I do think it would be wrong to use a logo > > without special permission from someone in authority, but companies > > don't have any special right to control information about their use of > > Boost. > > Well, I'm not sure, but I think that many companies have some very > strict policies about how their names are used, and even more their logos. > > I use boost at work in my company. But I guess that if I told you to use > this company name, without checking with the company lawers and the > communication department, I would get into trouble. > > What might happen is that many small companies would agree easily, but > very few big companies, where administrative stuff is more > "brazil-like". I'm not sure wether seing many name I've never heard of > and no known name would be good or bad advertising. So I suggest that > before getting such a page online, it would be good to wait until there > are enough names, with some well knows ones. > [Brian Braatz Writes:] Yes. Some will have this problem. I sympathize. Allow me to offer up that the because Adobe has released a framework that sits on top of boost that this would help the issues you raise. Only the people who watch this list will KNOW that though. So if we had a products page, and we had a link to the adobe framework in addition to others, it might help speak to the problem of people not seeing boost as a viable path. Btw- I found the python link fascinating. An additional suggestion would be to have SITE MAP on boost.org. I keep seeing boost pages in these mails I never knew existed (the phyton projects page is one)

2 1