September 2004 - Boost - lists.preview.boost.org

RE: [boost] Where are they now? (needed license permissions)
by Ben Hutchings 16 Sep '04

16 Sep '04

John Maddock wrote: > Here are the people we still need to contact, in order to move the > rest of Boost over to the BSL, if anyone has a more up to date email > address for these folks than the ones shown here, please let me > know, as at present they're not responding :-( Where you've written "??" does that mean that you have no email address or that mail to it is bouncing? <snip> > Gennadiy Rozental ?? Subscribed as <gennadiy.rozental(a)thomson.com>. <snip> > Mathias Koch ?? Subscribed as <mail(a)mathias-koch.de>. <snip> > Stephen Silver ?? Possibly subscribed as <silver(a)gsc-game.kiev.ua>? > Terje Slettebø tslettebo(a)chello.no <snip> Subscribed and posted on Tuesday as <tslettebo(a)broadpark.no>. Ben.

1 0

[test] problems with new intel-win32-8.1 toolset
by Joaquín Mª López Muñoz 16 Sep '04

16 Sep '04

Just in case nobody noticed, seems like Boost.Test is failing with Intel 8.1. This error appears at run-time in plenty of tests: Exception in "call_test_main": memory access violation C:/boost_regression/boost/libs/test/src/unit_test_suite.cpp(127): fatal error in "call_test_main": Test case initialization has failed *** errors detected in test case "call_test_main"; see standard output for details Test case "call_test_main" was aborted due to uncaught exception, user assert or system error EXIT STATUS: 200 I'm quite sure the problem is in Boost.Test, since the crash happens at several different libraries, all of which use this Boost.Test. Maybe someone with local access to this compiler can debug some of the failing tests and narrow down the locus of the problem. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

4 3

Serializing bitsets and tuples
by Brian Riis 16 Sep '04

16 Sep '04

Again, Robert, I have to thank you immensely for the Serialization library. It has made my life much easier. Anyway, I was wondering, since you state in the manual that all STL containers are supported, why I can't seem to find std::bitset in that. I realize that it is probably not the most common container to serialize, but still. Also, considering the is Boost library now, I'm wondering about the apparent absence of serialization for boost::tuple. It's not the end of the world (I can write them myself rather easily, I suppose), but for completeness I'd think at least Boost.Tuple should be supported. -- /Brian Riis

2 2

Boost Software License: Summary
by John Maddock 16 Sep '04

16 Sep '04

I've made a set of summaries for BSL conformance available at http://freespace.virgin.net/boost.regex/index.html There's one summary per library + one for all of Boost, I'd encourage everyone to take a look to see whether their work can be used under the BSL alone, or if there are non-BSL dependencies that they rely upon. Note that there are one or two cases where dependencies are found that are not real: filesystem for example ends up being shown as dependent upon the Graph lib (not under the BSL), but this is an illusion, based on iterator_adapters pulling in some python headers, which leads to a presumed dependence upon the python source. In most cases though the information shown should be accurate. Regards, John.

4 6

Howto track changes?
by Neal D. Becker 16 Sep '04

16 Sep '04

I did cvs update recently on boost-cvs, and found lots of changes - probably anticipation 1.32. I don't see a way to get a summary of changes. Does boost have such a mechanism? At mimimum, a ChangeLog for each lib. As an example of best-of-class, http://cvs-digest.org/?issue=aug202004

1 0

It seems that boost.random doesn't work under vc6.0?
by huangliang 16 Sep '04

16 Sep '04

When I tried to compile the random_demo.cpp using vc6.0 and stlport5.0, there were many errors and warnings. Does boost.random correctly work under vc6.0? I use boost1.31.0.

1 0

Regression tests for Tru64 are back.
by Markus Schöpflin 16 Sep '04

16 Sep '04

Hello, the regular regression runs for Tru64 / cxx 6.5 are back. They are run once a day by a cron job. I will be out of office for the next week, therefore I won't be able to switch to the release branch next week. This is scheduled for Monday, Semptember 27th. Markus

1 0

program_options bool_switch usage string ... how to prettify?
by Jonathan Graehl 16 Sep '04

16 Sep '04

I used to do this: >>bool help_flag; >>options.add_options() >> ("help,h","produce help message"); >>help_flag=vm.count("help") >> >>But it's possible to make a typo and everything isn't in one place (I >>prefer not to create a preprocessor macro to make "help" only occur once). >> >> > > > Now this is better: >bool help_flag; >options.add_options() > ("help,h", bool_switch(&help_flag),"produce help message"); > > > I tried it, and it works, but the usage string is a little odd: -h [ --help ] arg (=0) : produce help message -v [ --version ] arg (=0) : print the version number I would have hoped that the "arg (=0)" part would not be displayed at all for bool_switches. What would be the easiest way to suppress this? Similarly, is there some easy to use hook for customizing the "arg" to indicate the type of the data (similar to how the textual representation of the default argument can be changed, e.g. value<Infile>(&forests_file)->default_value(default_in,"STDIN"), so that I could get something like: "-f filename (=STDIN) :" instead of "-f arg (=STDIN) :"? -Jon p.s. should I post this sort of question in boost-users? I'd have to subscribe to it in order to post, so I didn't this time ...

3 6

program_options options description output
by Leo Goodstadt 16 Sep '04

16 Sep '04

Dear Volodya, Have you also given any consideration to how the descriptions wrap around if they are too long? For long descriptions, they can be quite ugly if left as is. At the moment, I output the description to a stringstream and wrap and indent everything post factum using the ": " in the output (I supply an optional line length for wrapping). This is fine and produces really nice output including embedded \n in the description text, but I wouldn't mind a more general solution. A minor nit pick, with option groups (chained options_description), the colons for the same group align but not across groups. Perhaps it might be possible to also dump the various fields of the output to some vector or even a templated callback object for greater flexibility of output. Llew Leo Goodstadt MRC Functional Genetics Unit Department of Human Anatomy and Genetics South Parks Road Oxford OX1 3QX United Kingdom leo.goodstadt(a)anatomy.oxford.ac.uk

2 1

FORMAL Review of "Output Formatter" library - 7 days left
by John Torjo 16 Sep '04

16 Sep '04

Dear boosters, For the FORMAL Review of "Output Formatter" - there are 7 days left. <side-note> There are quite a few hot topics at boost. So people might forget that there's a review going on ;) I would like to send a notification like this every 3 days. Boosters, please let me know if you find this ok or not. As I know, it hasn't been done before (announcing a format review multiple times) </side-note> Author: Reece Dunn Description: The outfmt library provides means to write and read containers/ arrays/ ranges (pairs of iterators) to/from STL streams. It also provides means to customize formatting as your write to/read from a stream: std::list<int> l; // { 1, 4, 10 } std::cout << formatob(l); // output: [ 1, 4, 10 ] std::cout << formatob(l).format("<",">"); // output: <1, 4, 10> Download: You can get it from the boost sandbox: http://cvs.sourceforge.net/viewcvs.py/boost-sandbox/boost-sandbox/libs/outf… http://cvs.sourceforge.net/viewcvs.py/boost-sandbox/boost-sandbox/boost/out… As a convenience (only for the period of the review), you can also get it from http://www.torjo.com/code/outfmt.zip (153Kb) Review process: Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. When doing the formal review, please answer the following questions: 1. What is your evaluation of the design? 2. What is your evaluation of the implementation? 3. What is your evaluation of the documentation? 4. What is your evaluation of the potential usefulness of the library? 5. Did you try to use the library? With what compiler? Did you have any problems? 6. How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? 7. Are you knowledgeable about the problem domain? And most important, 8. 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. More on the formal review process: http://www.boost.org/more/formal_review_process.htm The Review Manager is: John Torjo john.lists(a)torjo.com Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/

3 3