_______________________________________________
Boost-users mailing list
Boost...@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users
The documentation isn't uploaded to the site until the final release.
You can see the property tree documentation in the download. The beta
site isn't really meant for general use.
Daniel
> http://beta.boost.org/users/news/version_1_41_0 for details.
This page doesn't include the updates to boost.thread. Can you remind me
which file I need to modify to fix that?
Also, I've made some doc changes on trunk. Is it OK to merge them to
release?
Anthony
--
Author of C++ Concurrency in Action | http://www.manning.com/williams
just::thread C++0x thread library | http://www.stdthread.co.uk
Just Software Solutions Ltd | http://www.justsoftwaresolutions.co.uk
15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976
Ok, but where users can find beta-state documentation?
Beta site isn't really meant for general use, so everybody will
understand that your docs are beta.
I vote for PropertyTree docs on beta.boost.org :)
Ok, but where users can find beta-state documentation?
Beta site isn't really meant for general use, so everybody will
understand that your docs are beta.
I vote for PropertyTree docs on beta.boost.org :)
In the download. I also upload the trunk documentation whenever I
generate it, and subversion redirects to that. So if you start with
the link below you'll get redirected to a fairly recent version of the
trunk documentation.
http://svn.boost.org/svn/boost/trunk/libs/libraries.htm
> Beta site isn't really meant for general use, so everybody will
> understand that your docs are beta.
> I vote for PropertyTree docs on beta.boost.org :)
Vote away, although opening a ticket on trac is more effective. The
problem is that the way the site's designed, it's a bit of pain to do
that just for the sake of putting the beta documentation up for a week
or so.
Daniel
We're not google, our beta period really is for testing. You should
probably wait the release, which won't be long.
Daniel