Re: comprehensive boost index (was Re: [boost] Boost.Graph missingdocs)

From: Gilles J. Seguin (segg_at_[hidden])
Date: 2002-08-31 11:46:57

David Abrahams wrote:
> 
> ----- Original Message -----
> From: "Jeremy Siek" <jsiek_at_[hidden]>
> 
> > Hi Dave,
> >
> > On Fri, 23 Aug 2002, David Abrahams wrote:
> > dave> make_iterator_property_map has no docs.
> >
> > Sure it does :)
> >
> > http://www.boost.org/libs/property_map/iterator_property_map.html
> 
> Whoops, I was grep-find'ing through the graph docs. Sorry!
> 
> > dave> Is there a comprehensive reference to all the Boost.Graph
> components
> > dave> somewhere? There should be.
> >
> > Is there an index of functions and classes? Not in the online docs.
> >
> > There is a table of contents and reference that documents all components.
> > However, to find particular functions some digging may be required.

> > Part of the problem was that you were looking in the wrong library.
> > make_iterator_property_map is in the Property Map library, not in the
> > Graph library.
> 
> I see that now.
> 
> > What you really needed was a comprehensive index for all of Boost.
> > I'd be willing to help create such an index, but not by myself.
> > Do we have volunteers?

> Ooh, wow.
> That's a great idea, but I think we'd better try to find some 
> automated tools to help us.

Does this idea, is an automated tool like Source-Navigator
<http://sourceforge.net/projects/sourcenav/>
I beleive the parser is not strong enough for parsing template.

Front end parsing can be done, see idea like
<http://www.gccxml.org/HTML/Index.html>

Is this the wright direction ?
Are such tools desirable for boost ?

If it is, we know that such a tool produces massive database.
My understanding is that we need a "view", in the data base sense.

>From there, it is easy to understand that utilities for software 
analysis tool is close.