Re: [boost] [Root Pointer] Seeking a Review Manager

Subject: Re: [boost] [Root Pointer] Seeking a Review Manager
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2016-04-02 12:14:14

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Larry Evans
> Sent: 02 April 2016 13:59
> To: boost_at_[hidden]
> Subject: Re: [boost] [Root Pointer] Seeking a Review Manager
> 
> On 04/01/2016 12:25 AM, Phil Bouchard wrote:
> > Greetings,
> >
> > - "Root Pointer" is an alternative to the long unsolved problem of
> > garbage collectors which lasted for more than 70 years!
> >
> >
> > - Thanks to Paul A. Bristow for his help on the generation of the
> > documentation which is now available at the following link:
> > http://philippeb8.github.io/root_ptr/
> >
> The page:
> 
> http://philippeb8.github.io/root_ptr/root_ptr/howtouse.html
> 
> contains the sentence:
> 
> The information given is derived from Doxygen-syntax comments in the
> include files, mainly root_ptr.hpp.
> 
> with the link, _root_ptr.hpp_, which, when clicked, results in:
> 
> 404
> 
> File not found
> 
> If there's some way to check the links in the docs, it would be
> a good idea to use it.

That's disappointing as I've run the Boost inspect tool that should check for all missing links (and it said all was well), but I'm
sure it is a mistake by me and I'll try to correct it.

(At least you've done better than me - when I clock on the link I get only

"GitHub Pages is temporarily down for maintenance."!)

Meanwhile, I'm hope you can manage without this root_ptr.hpp link.

Paul

PS Providing documentation for a library under discussion isn't as easy as for a finished library.
There is no 'right' place to put the documentation, as normally Boost documentation is a separate item.