May 2009 - Boost - lists.preview.boost.org

[thread] #2739 shouldn't at_thread_exit work on the main thread?
by vicente.botet 01 Jun '09

01 Jun '09

Hi, Anthony, I have submitted a patch that makes a regression on the test test_tss. My patch was related to add a atexit call for the main thread when make_external_thread_data is called, but it adds also for the thread created with native threads. So the patch don't work. Is there a way to make a difference between the main thread and the others? BTW the test fails on cygwin gcc 3.6.4, could someone test it on Windows or Linux to see if this is specific to cygwin? Thanks, _____________________ Vicente Juan Botet Escribá

3 9

[Bug Sprint] Ticket #2867 - Adding a get_expected_args member to format
by Joel Falcou 01 Jun '09

01 Jun '09

https://svn.boost.org/trac/boost/ticket/2867 This ticket has a working patch + test attached. Should be merged and closed. -- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35

2 2

[config] Deprecate/remove BOOST_NO_INITIALIZER_LISTS
by Daniel James 01 Jun '09

01 Jun '09

Hi, Once BOOST_NO_0X_HDR_INITIALIZER_LIST has been added to release, I think we should remove BOOST_NO_INITIALIZER_LISTS. It's confusing having both macros. BOOST_NO_INITIALIZER_LISTS is probably useless as it only indicates compiler support and initializer lists can't really be used without the header. I seem to be the only person who uses it, so it might be okay to just remove it immediately or if not, deprecate it and remove it in the next release. Does that sound okay? Daniel

3 5

Bug Sprint Report for Saturday, May 30th
by Marshall Clow 31 May '09

31 May '09

The boost bug sprint started Friday, May 29th, and runs through Sunday June 7th. We're off to a great start! Status <https://svn.boost.org/trac/boost/report/1> 7:00 AM PDT 5/29: 797 open tickets. 7:45 AM PDT 5/30: 772 open tickets. 7:15 AM PDT 5/31: 763 open tickets. Activity: 5/29: 6 new tickets, 77 modifications, 25 tickets closed 5/30: 2 new tickets, 42 modifications, 17 tickets closed [ Numbers may not add up because I am counting via two different methods, using data that is time-stamped in two different time zones. Also, tickets can be closed and reopened. ] What can you do? See <https://svn.boost.org/trac/boost/wiki/BugSprintJune2009> for details. I've added four new reports to the trac: Open ticket count by owner: <https://svn.boost.org/trac/boost/report/18> Open ticket count by component: <https://svn.boost.org/trac/boost/report/19> Open ticket count by ticket type: <https://svn.boost.org/trac/boost/report/20> Open ticket count by milestone: <https://svn.boost.org/trac/boost/report/21> --------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou(a)u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost(a)objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco(a)osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4) 9) Steven Watanabe <watanabesj(a)gmail.com> (bug fixes, como) 10) vicente.botet" <vicente.botet(a)wanadoo.fr> 11) Stjepan Rajko <stjepan.rajko(a)gmail.com> (fusion) 12) Daniel Wallin (parameter, ...) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

[Bug Sprint] Ticket #613 - boost/crc.hpp uses non-standard conforming syntax
by Joel Falcou 31 May '09

31 May '09

https://svn.boost.org/trac/boost/ticket/613 The bugs seems indeed to have disappeared on gcc 4+. Should we close this one ? -- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35

2 2

Re: [boost] [Modularization] A new approach to header modularization
by JOAQUIN M. LOPEZ MUÑOZ 31 May '09

31 May '09

________________________________________ De: boost-bounces(a)lists.boost.org [boost-bounces(a)lists.boost.org] En nombre de Beman Dawes [bdawes(a)acm.org] Enviado el: jueves, 28 de mayo de 2009 23:06 Para: boost(a)lists.boost.org Asunto: Re: [boost] [Modularization] A new approach to header modularization > > On Thu, May 28, 2009 at 10:53 AM, troy d. straszheim > <troy(a)resophonic.com> wrote: > > In no particular order: > > > > - There is still the toplevel filesystem.hpp and friends to deal with. > > The way to deal with that is to migrate those to within the library's > header directory. > > As boost grows, filling the boost/ with headers becomes less and less > attractive. I don't see why this is less attractive than having boost/ filled with folders. > Of course we have to leave the current headers there for > compatibiltiy, but that location could be deprecated and eventually > only <boost/filesystem/filesystem.hpp> supported. *This* is less attractive to me; I think a Boost lib is entitled to have at least one top level header; many use it to include all or the the most usual components. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

4 3

[Bug Sprint] - Ticket #2599 - corner case in boost::fusion::all
by Joel Falcou 31 May '09

31 May '09

https://svn.boost.org/trac/boost/ticket/2599 This ticket contains a working patch and should be merged/closed. -- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35

2 1

Patches on tickets #3050 and #3051
by Marshall Clow 31 May '09

31 May '09

I tested these patches on darwin (gcc 4.0.1). They didn't break anything; which is not really surprising, since they are merely ifdef-ing out code on some systems - but not on darwin. If anyone builds with BOOST_NO_IOSTREAM and/or BOOST_NO_TYPEID, I would appreciate it if you could test out these patches. Thanks in advance! -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Can someone (using Windows) check ticket #316?
by Marshall Clow 31 May '09

31 May '09

It's hard to tell, but those look like Visual Studio warnings. If they no longer exist, that ticket should be closed. If they do still exist, they should be looked into. <https://svn.boost.org/trac/boost/ticket/316> Thanks! -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

2 4

Phoenix Reloaded
by Eric Niebler 31 May '09

31 May '09

I'm kick-starting the development effort to reimplement Phoenix on top of Proto. There's already been some discussion off-list among the interested parties, but there was general agreement to move the discussion here to do our work out in the open and possibly involve more people. To that end, I have ... ... created a Wiki page for coordinating our efforts: https://svn.boost.org/trac/boost/wiki/BoostPhoenix3 ... created a branch at branches/phoenix_v3. Anybody interested in helping out or just following along should do the following from BOOST_ROOT (trunk): cd boost svn co https://svn.boost.org/svn/boost/branches/phoenix_v3/boost/phoenix cd ../libs svn co https://svn.boost.org/svn/boost/branches/phoenix_v3/libs/phoenix There is nothing in boost/phoenix right now but stub headers, and libs/phoenix is simply copied from trunk/libs/spirit/phoenix. On the Wiki I put uploaded a miniphoenix.cpp file that demonstrates some ideas I have about what Phoenix-on-Proto might look like. Feedback is welcome. -- Eric Niebler BoostPro Computing http://www.boostpro.com

6 14

Re: [boost] [BCP] Script for global renaming Boost Namespace
by Artyom 30 May '09

30 May '09

Hello, > I > think there is interest for such a feature, especially if > you are willing to > maintain it on regular basis. If there is an interest in it and, it would be accepted I'd be glad to continue supporting it on regular basis. Probably it may be integreted with regeression test to ensure that Boost still works after renaming. > If we do expect all > possible users to have Python > installed, it may be nice to use python for this. But > how do you propose to > integrate with bcp? 1. First of all this script is "one time use" and it is targeted for mostly project maintainers/managers that need to solve name collision problems. So, if it is not a big price to install Python to run such script, especially that it is availible by default for most supported platforms, like Solaris, FreeBSD, Linux, with an exception of Windows where in can be easily installed. So I don't see a real problem in using Python for this purpose. In any case there are already some Perl scripts are used for code generation. (See Boost.Asio for example) 2. I don't see it as a part of BCP but rather the tool that can be used together, like: bcp --boost=/path/to/boost bind.hpp regex asio my_boost_dir boost_rename.py my_boost_dir mybst Because it can be actually applied on full Boost tree, if someone wants its full version. Artyom > -- > Bjørn Roald > > > On Saturday 30 May 2009 10:55:25 am Artyom wrote: > > Hello, > > > > Some updates: > > ------------- > > > > 1. Added copyright - Boost License. > > 2. Some more regression tests passed, some code > cleanup > > > > Questions: > > ---------- > > > > 1. How can I submit it as an addon to BCP utility? > > 2. Have anybody tested it, I'd like to see if there > any problems, > > especially on Windows platform -- I > hadn't tested it there. > > > > > > Thanks > > Artyom > > > > P.S.: The source is there http://art-blog.no-ip.info/files/rename.py > > > > --- On Mon, 5/25/09, Artyom <artyomtnk(a)yahoo.com> > wrote: > > > From: Artyom <artyomtnk(a)yahoo.com> > > > Subject: [BCP] Script for global renaming Boost > Namespace > > > To: boost(a)lists.boost.org > > > Date: Monday, May 25, 2009, 11:14 AM > > > Hello, > > > > > > Today Boost does not provide any backward binary > > > compatibility. This > > > makes big problems in shipping 3rd part libraries > that > > > depend on Boost > > > because library user must use the same version of > Boost as > > > that 3rd > > > part library was compiled with. > > > > > > The problem is become even more critical for ELF > platforms > > > (UNIXes) > > > where all symbols are exported by default. > > > > > > I had written a small Python script that switches > boost > > > namespace > > > to other, allowing 3rd part project include it > without > > > collisions > > > with primary Boost namespace. > > > > > > The script passes over the source tree of boost > and changes > > > each > > > include path from <boost/foo/bar.hpp> too > > > <newnamespace/foo/bar.hpp> > > > and renames all macros and identifiers from > > > some_BOOST_something to > > > some_NEWNAMESPACE_something and > some_boost_something to > > > some_newnamespace_something. > > > > > > It does not touch comments (copyright) and > strings unless > > > the string > > > is in form "boost/.*" which is usually some > reference for > > > include. > > > > > > I've run this script on the 1.39 version of boost > and > > > successfully build full boost release and run > some of > > > regression tests > > > like Boost.Asio, Boost.Regex, Boost.Function and > others, > > > > > > The source code is available at: > > > http://art-blog.no-ip.info/files/rename.py > > > > > > You run it as: > > > > > > ./rename /path/to/boost/source > > > new_namespace_name > > > > > > It renames all macros and namespaces to new > namespace, and > > > renames > > > main include directory to new_namespace_na,e. > > > > > > Few points: > > > > > > 1. It is only alpha version script, I just want > to see > > > feedback and > > > proposals > > > 2. I do not update build scripts. I assume that > each > > > library that > > > tryes to import its own version of > Boost > > > would provide its own > > > build system. > > > 3. The build scripts should be updated > differently because > > > they have > > > different syntax and grammar. The > > > required changes are to > > > fix different build defines > > > > > > Please, give feedback proposal. If there someone > who is > > > familiar > > > with Boost.Build systems can actually help, this > would be > > > very good. > > > > > > Today there is a big problem with working with > different > > > versions of > > > Boost. It should be solved. > > > > > > I think this script may be a valuable addition > to > > > Boost.BCP utility > > > that allows extracting a subset of boost for > integration in > > > 3rd part > > > tools and libraries. > > > > > > Thanks, > > > Artyom > > > > > > > > > > > > > _______________________________________________ > > Unsubscribe & other changes: > > http://lists.boost.org/mailman/listinfo.cgi/boost > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost >

2 1

mingw help
by Vladimir Prus 30 May '09

30 May '09

We have two issues: https://svn.boost.org/trac/boost/ticket/1907 https://svn.boost.org/trac/boost/ticket/2181 that claim the the names of library files on mingw are wrong. Unfortunately, the picture is not exactly clear, and it's not even clear what the right naming would be. I'd appreciate if somebody who actually uses mingw could clarify these points: 1. Currently, we use the same naming on mingw as on windows -- foo.dll and foo.lib for shared libs and import libs, and libfoo.lib for static library. Is this OK? 2. Are the search rules listed in tools/build/v2/tools/gcc.jam around line 657 matching the reality? 3. Is naming in (1) compatible with using -Bstatic to request static libs? Thanks, Volodya

3 4

Re: [boost] [BCP] Script for global renaming Boost Namespace
by Artyom 30 May '09

30 May '09

Hello, Some updates: ------------- 1. Added copyright - Boost License. 2. Some more regression tests passed, some code cleanup Questions: ---------- 1. How can I submit it as an addon to BCP utility? 2. Have anybody tested it, I'd like to see if there any problems, especially on Windows platform -- I hadn't tested it there. Thanks Artyom P.S.: The source is there http://art-blog.no-ip.info/files/rename.py --- On Mon, 5/25/09, Artyom <artyomtnk(a)yahoo.com> wrote: > From: Artyom <artyomtnk(a)yahoo.com> > Subject: [BCP] Script for global renaming Boost Namespace > To: boost(a)lists.boost.org > Date: Monday, May 25, 2009, 11:14 AM > Hello, > > Today Boost does not provide any backward binary > compatibility. This > makes big problems in shipping 3rd part libraries that > depend on Boost > because library user must use the same version of Boost as > that 3rd > part library was compiled with. > > The problem is become even more critical for ELF platforms > (UNIXes) > where all symbols are exported by default. > > I had written a small Python script that switches boost > namespace > to other, allowing 3rd part project include it without > collisions > with primary Boost namespace. > > The script passes over the source tree of boost and changes > each > include path from <boost/foo/bar.hpp> too > <newnamespace/foo/bar.hpp> > and renames all macros and identifiers from > some_BOOST_something to > some_NEWNAMESPACE_something and some_boost_something to > some_newnamespace_something. > > It does not touch comments (copyright) and strings unless > the string > is in form "boost/.*" which is usually some reference for > include. > > I've run this script on the 1.39 version of boost and > successfully build full boost release and run some of > regression tests > like Boost.Asio, Boost.Regex, Boost.Function and others, > > The source code is available at: > http://art-blog.no-ip.info/files/rename.py > > You run it as: > > ./rename /path/to/boost/source > new_namespace_name > > It renames all macros and namespaces to new namespace, and > renames > main include directory to new_namespace_na,e. > > Few points: > > 1. It is only alpha version script, I just want to see > feedback and > proposals > 2. I do not update build scripts. I assume that each > library that > tryes to import its own version of Boost > would provide its own > build system. > 3. The build scripts should be updated differently because > they have > different syntax and grammar. The > required changes are to > fix different build defines > > Please, give feedback proposal. If there someone who is > familiar > with Boost.Build systems can actually help, this would be > very good. > > Today there is a big problem with working with different > versions of > Boost. It should be solved. > > I think this script may be a valuable addition to > Boost.BCP utility > that allows extracting a subset of boost for integration in > 3rd part > tools and libraries. > > Thanks, > Artyom > > > >

2 1

[Conversion] Looking for a review manager
by vicente.botet 30 May '09

30 May '09

Hi there, I'm looking for a review manager for the new Conversion library. Anyone around here who would like to volunteer? "Generic explicit conversion between unrelated types: generic convert to and assign to functions which can be specialized by the user to make explicit conversion between unrelated types + partial specialization for std::complex, std::pair, boost::optional, boost::rational, boost::interval and between boost::chrono::time point and boost::ptime and between boost::chrono::duration and boost::time duration" Waiting for that any comments on the library is welcome. You can retrieve it from https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Conv… Regards, _____________________ Vicente Juan Botet Escribá

1 0

[Regex] build bug: Makefiles contain old version number (1.38 vs 1.39)
by Harald Csaszar 30 May '09

30 May '09

Hi, It seems as if the regex library makefiles have not been updated in the 1.39 release. Files like <boost>/libs/regex/build/gcc.mak and vc71.mak create libraries with version number 1_38 instead of 1_39. Regards, Harald Csaszar

2 1

Re: [boost] mingw help
by Artyom 30 May '09

30 May '09

> 1. Currently, we use the same naming on mingw as on windows > -- > foo.dll and foo.lib for shared libs and import libs, and > libfoo.lib > for static library. Is this OK? No, this is definatly not correct. This is how, autotools generate libraries: Mingw Naming convention for library "foo" with ABI version 3: Static library: libfoo.a --> installed to lib Import lubrary: libfoo.dll.a --> installed to lib Dynamic library: libfoo-3.dll --> installed to bin Cygwin Naming convention Static library: libfoo.a --> installed to lib Import lubrary: libfoo.dll.a --> installed to lib Dynamic library: cygfoo-3.dll --> installed to bin Artyom

2 1

[thread] #2636 threads and locks
by vicente.botet 30 May '09

30 May '09

Hi, "The standard includes template <class Duration> unique_lock(mutex_type& m, const Duration& rel_time); which is not in boost::threads. " Anthony, I think that this ticket is already on the released locks.hpp file (modified with 48213, 49324) : template<typename TimeDuration> unique_lock(Mutex& m_,TimeDuration const& target_time): m(&m_),is_locked(false) { timed_lock(target_time); } So it can be closed. Best, _____________________ Vicente Juan Botet Escribá

1 1

[thread] #2637 shared mutex lock
by vicente.botet 30 May '09

30 May '09

Hi, "The folowing should be added template<typename TimeDuration?> bool shared_mutex::timed_lock_shared(TimeDuration? const & relative_time); template<typename TimeDuration?> bool shared_mutex::timed_lock(TimeDuration? const & relative_time); " Anthony, I think that this ticket is already on the released shared_mutex.hpp files: template<typename TimeDuration> bool timed_lock_shared(TimeDuration const & relative_time) { return timed_lock_shared(get_system_time()+relative_time); } template<typename TimeDuration> bool timed_lock(TimeDuration const & relative_time) { return timed_lock(get_system_time()+relative_time); } So it can be closed. Best, _____________________ Vicente Juan Botet Escribá

1 0

[thread] #2741 proposal to manage portable and non portable thread attributes
by vicente.botet 30 May '09

30 May '09

Hi, Anthony, I have attached to the ticket https://svn.boost.org/trac/boost/ticket/2741 a test files and patches for the feature POSIX implementation Do you think that this is on the right way? Best, _____________________ Vicente Juan Botet Escribá

1 0

Re: [boost] [Graph] how to test/submit patch
by Tim Keitt 30 May '09

30 May '09

On Fri, May 29, 2009 at 2:08 PM, Marshall Clow <marshall(a)idio.com> wrote: > At 1:02 PM -0500 5/29/09, Tim Keitt wrote: >> >> I would like to submit a patch for the Graph library. (This is the >> iterator splitting issue I raised some time ago.) > > Same answer as on the -users list ;-) > >> So what is the procedure? >> >> 1) check out source from sourceforge SVN (done) >> 2) make changes >> 3) run tests??? (what is the best way to ensure the behavior has not >> changed?) > > Run the tests. I was trying to ascertain where they live and how to run them. > If you think that there should be more tests, write them. Should be easy to come up with a test case or two. Just checking to see if I haven't missed something standard in terms of regressions, etc. > Ideally, you should write a test that fails on the unpatched version of the > library, and succeeds after applying your patch. The goal is not to change the existing behavior. My patch should not affect algorithms called on the built-in data structures. It will make the library compatible with my own data structures that require slightly more restrictive assumptions regarding iterator pairs. > >> 4) generate the patch (use svn diff?) > > Yep. Its been a long time -- are there preferred formats/switches when calling diff? (I recall vaguely a -p argument.) > >> 5) submit somewhere > > In a Trac ticket. <http://svn.boost.org> OK. Thanks for the help. THK > >> I just want to be sure I'm pulling the correct tree and there is some >> means to run regressions on my changes. > > Sounds good to me. > -- > -- Marshall > > Marshall Clow Idio Software <mailto:marshall@idio.com> > > It is by caffeine alone I set my mind in motion. > It is by the beans of Java that thoughts acquire speed, > the hands acquire shaking, the shaking becomes a warning. > It is by caffeine alone I set my mind in motion. > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost > -- Timothy H. Keitt Associate Professor Section of Integrative Biology University of Texas at Austin http://www.keittlab.org/

2 1

profile-templates
by Stefan Seefeld 30 May '09

30 May '09

Hello, I'v just learned about your template instantiation profiler tool, and I'm very intrigued ! What is the best way to download and build it ? I tried to check out sandbox/tools/profile_templates, but it seems that is not meant to be used stand-alone. Do I really need to check out the entirety of the sandbox (which is huge !) ? Or are there better ways to do it ? (How does that question fit into the current modularization discussion ? :-) ) Many thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...

2 2

[parameter] Preventing instantiation of lazy binding operator() until default is needed
by Jeremiah Willcock 29 May '09

29 May '09

This is a subset of my previous email, with a more specific and concrete example. The following code: #include <boost/parameter/name.hpp> #include <boost/parameter/binding.hpp> BOOST_PARAMETER_NAME(my_param) template <typename T> struct s {}; template <typename T> struct bogus { typedef typename s<T>::type result_type; template <typename U> struct result: public s<U> {}; result_type operator()() const {return 0;} }; template <typename ArgPack> void f(const ArgPack& ap) { const char* cs = ap[_my_param || bogus<const char*>()]; } int main(int, char**) { f(_my_param = "foo"); return 0; } does not work because result_type is invalid when the struct bogus is instantiated when creating the default value used in operator||(). If operator()() was a template, I think the compiler would delay instantiating it until it was called. Is there a way to force operator()() to be a template in Boost.Parameter, allowing its return type to only be instantiated when Boost.Parameter knows that the default will be used? This is a simplified example from a larger piece of code where the lazy default does not have a valid return type in some cases, and the parameter must be explicitly specified in those cases. Thank you. -- Jeremiah Willcock

2 2

[random] fixing uniform_int bias
by Steven Watanabe 29 May '09

29 May '09

AMDG Given that we periodically get complaints about the non-uniformity of uniform_int, I'm going to commit that attached patch if no one objects. I had to modify one of the test cases, because it causes the modified uniform_int to loop forever. I believe that this is acceptable, because the test is giving uniform_int a generator that always returns the same value. The rejection method used currently will also loop under certain similar circumstances. The patch also fixes an operator precedence error. However, looking more closely, there appears to be another bug in that branch, which can cause a loop. Aaaaaargh. I'll probably get a complete patch sometime tomorrow, but in the meantime I'd appreciate having another pair of eyes looking at the fix I have. In Christ, Steven Watanabe

1 3

[inspect][filesystem] libs/filesystem/test/ticket_2260_test.cpp
by Jeremiah Willcock 29 May '09

29 May '09

The file libs/filesystem/test/ticket_2260_test.cpp appears in the Boost trunk inspection report at http://boost.cowic.de/rc/inspect-trunk.html but does not appear in SVN. Is that an old file in the directory where the inspections are taking place? -- Jeremiah Willcock

2 1

[1.39.0] Ready for beta?
by Beman Dawes 29 May '09

29 May '09

I've gotten badly sidetracked by non-Boost work, but would like to get the 1.39.0 beta out tomorrow if at all possible. Are there any known showstoppers? If anyone has a few spare minutes, it would help if they could download one of the current release snapshots from http://boost.cowic.de/rc/, browse around and report any problems spotted. Library authors who use Boostbook/Quickbook, but don't have time to look at the full snapshot, might want to check http://boost.cowic.de/rc/boost-docs.7z Known problems/questions: * index.html ??? needs to be replaced by new library count. * pdf docs: Do we want to do anything more for this release? Thanks, --Beman

13 29