- Boost - lists.boost.org

[program_options] vc6 and vc7: explicit function template arguments
by Vladimir Prus 15 Jun '04

15 Jun '04

Hello, it appears that both vc6 and vc7 don't understand explicit function template arguments, like this: value<string>()->implicit() where 'value' is a function. Anybody can suggest a workaround? One possible approach would be to make 'value' a class which overloaded operator->, but that's a lot of work. TIA, Volodya

2 2

CVS problem
by Janusz Piwowarski 15 Jun '04

15 Jun '04

Hello, >From yesterday evening to now, there's agurtovoy's lock in /cvsroot/boost/boost/boost/python/converter. Regards, Janusz

2 2

RE: [boost] Re: Announcing a New C++ Zine
by Glen Knowles 15 Jun '04

15 Jun '04

>From: David Abrahams [mailto:dave@boost-consulting.com] >>>>>Has William reappeared? >>>> >> As last resort, his phone number is listed ;-) > >But I forgot what state he lives in. >From http://www.boost.org/people/william_kempf.htm Bill Kempf lives in Omaha, NE with his wife Bonnie, his cat Dexter and his two Chinchillas, Chimney and Minuet. He married on Oct. 30, 1999 where he and his wife held a Halloween costume reception. If that doesn't give you an idea of what kind of guy he is, nothing will. Glen

2 1

Re: Announcing a New C++ Zine
by Chuck Allison 14 Jun '04

14 Jun '04

Jeff Flinn wrote: > Has William reappeared? Actually, I haven't heard from him for a while. This is not the final list. I will soon do a final query of those who want their names to remain on the Editorial Board (and of course, others can be added). The list I sent contains those who have participated in the forming of The C++ Source since last October. You might want to ping him with a private message. I should add here that I forgot to mention in my original post that for now, contributing to The C++ Source is a "labor of love". None of us are getting paid. As we get sufficient advertising, we will share the wealth. We are starting small, but I predict a gradual swelling until this becomes a mainstay for the majority of C++ developers. Someone has suggested a subscription basis, but with today's Internet culture, I think we'll do the most good if we keep it free. That can change, but for now, that's the way it is. After all, Boosters are very familiar with this model :-). -- Chuck Allison

7 12

Announcing a New Online C++ Zine
by Chuck Allison 14 Jun '04

14 Jun '04

Hello Boosters, David Abrahams suggested I could send you an announcement on this list. For some time now (since last October, actually) a group of C++ luminaries have been discussing the virtues and possibilities of a peer-reviewed source for the C++ community. We have decided on the name "The C++ Source", and a preliminary page is available for viewing at http://www.artima.com/cppsource. The idea is to have seasoned C++ professionals review submissions to ensure that the publications are of high quality and of interest. There will also be tutorials, news, lots of stuff. The Editorial Board currently is: David Abrahams J. Stephen Adamczyk Andrei Alexandrescu Matthew Austern Pete Becker Walter Bright Steve Clamage Greg Colvin Jim Coplien Stephen Dewhurst Howard Hinnant Bjorn Karlsson William Kempf Andrew Koenig Martha Masinton Scott Meyers Thomas Plum Dan Saks Jerry Schwarz Jeremy Siek Bjarne Stroustrup Herb Sutter Matthew Wilson Leor Zolman (Like, wow!) I am writing to invite you to consider writing for The C++ Source. In fact, the first installments to appear later this month include an article by Booster Bjorn Karlsson. The chances that anything of interest to you will be of interest to the C++ community at large, and will make a positive contribution to daily C++ development. If you have any ideas, proposals, or suggestions, please email me at chuck(a)freshsources.com. Thanks! -- Best regards, -- Chuck Allison

5 5

RE: [boost] Re: Documentation
by Reece Dunn 14 Jun '04

14 Jun '04

John Nagle wrote: >Robert Ramey wrote: >>As far as writing documentation is concerned I found the the "standard" >>boost position at: >> >>C:\boost_1_31_0\more\writingdoc\index.html > > I'm having trouble reading your C: drive. Try replacing "C:\boost_1_31_0" with either http://www.boost-consulting.com/boost or the directory where your copy of Boost is located, e.g.: http://www.boost-consulting.com/boost/more/writingdoc/index.html HTH Regards, Reece _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

1 0

RE: [boost] Documentation
by Reece Dunn 14 Jun '04

14 Jun '04

David B. Held wrote: >Ok, if the Boost style documentation is too simple, and docs like >Spirit are too cute, what is a nice, happy median? Have you looked at the BoostBook generated docs :). Let me know what you think of the current L&F: I have updated this a while ago to try and bridge the gap between the two looks (the docs now have Spirit-style navigation). See http://boost.sourceforge.net/regression-logs/cs-win32_metacomm/doc/html/ind… for the new-stle docs. >If we're going >to demand uniformity in licensing, should we also demand more >uniformity in documentation? I agree on this. At the moment, we have the docs written in HTML, those in BoostBook format (like Boost.Any and the BBv2 docs) and the Spirit docs which have their own format. As far as I understand it, the BoostBook tool is relatively new and has a learning curve, so it will take some time to migrate the docs to this format. As for the Spirit docs, they have their own sourceforge area as well as being a part of Boost, so forcing them to change doc format wouldn't be fair. However, since the Spirit docs are in a special text format that is "compiled" into HTML using Spirit, it should be easy to create a BoostBook back-end and have the docs in boost in this format and the ones on the sourceforge area in the existing format. With this in mind, it might be beneficial to create a HTML to BoostBook converter (possibly using Spirit) to allow easier migration to the BoostBook format. >I think a single documentation style >across Boost would make it even easier to learn new libraries. I >recently found it very difficult to find the information I wanted about >the Boost.Test library, as well as Boost.Preprocessor. What can >be done about these issues? I think the BoostBook format would go a long way to resolving these issues, once the docs are all in this uniform format. Regards, Reece _________________________________________________________________ Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo

6 6

config tests breaking change imminent
by John Maddock 14 Jun '04

14 Jun '04

Following our recent discussion on file naming conventions, I've submitted a Sourceforge support request to have all the *.cxx files in libs/config/test renamed to *.ipp. When this change takes place the config tests will be broken until further notice (but probably only for a day or two). Regards, John.

2 1

Re:[boost] Re: Re: config and .cxx extensions
by Robert Ramey 14 Jun '04

14 Jun '04

Jeff Flinn wrote: > If it's VisualStudio, you can add the extensions to the registry to act > like headers or source(compilable) files. I would bet most others have a > similar facility. Please tell us how to do that. I looked for this and couldn't find it. I would like to tell my Visual.Net IDE to treat *.ipp file like *.hpp and *.cpp for editing purposes. Robert Ramey

3 2

Re: Documentation
by Robert Ramey 14 Jun '04

14 Jun '04

As far as writing documentation is concerned I found the the "standard" boost position at: C:\boost_1_31_0\more\writingdoc\index.html To be very helpful. I think it goes a long way to providing a common look and feel the boost docs. By providing a skeleton document for a boost library it also saves a lot of work. I tried to follow it as closely as possible for the boost serialization library. I think the discussions around boost documentation should focus on how this "document" document (meta-document?) should be updated. So it might a) Be a little more specific re tutorial and reference documentation sections. This is not quite as easy as one would first think as the requirements for formatting/tables of overloads are different from from function calls, etc. b) Suggest a common navigation facility. I actually liked the navigation pane used by the BOOST_PP library and have incorporated something similar in the new serialization library documentation. I find it very helpful. Robert Ramey

2 1