Doxygen

Hi,

I have a C++ file N.cc similar to the following:

  //! @namespace N my namespace
  namespace N {
   
    //! It does not matter whether I put here a doc-comment
    namespace { // anonymous

      //! @class A some class inside an anonymous namespace
      class A {
        // ...
      };

    }

    //! Some function accessing members of the anonymous namespace
    void f() {
      A a;
      // ...
    }

  }

The HTML page for N.cc (generated by Doxygen 1.3.8) lists A as
  class N::A
ignoring that it belongs to a nested (though unnamed) namespace. I'd
expected something like:
  class N::<anonymous>::A
(The same holds for the class list and class hierarchy.)

Is it possible to make Doxygen not suppress the information about the
anonymous namespace?


FWIW, if I change above in the following program:

  //! @namespace N my namespace
  namespace N {
   
    //! It does not matter whether I put here a doc-comment
    namespace { // anonymous

      //! @class A some class inside an anonymous namespace
      class A {
        // ...
      };

    }

    //! Some function accessing members of the anonymous namespace
    void f() {
      A a;
      // ...
    }

    //! @class A Another class A hiding the one above
    class A {
      // ...
    };

    //! Another function accessing class A in namespace N
    void g() {
      A a;
      // ...
    }

  }

then doxygen complains that class N::A is already documented. Note
that this is still a conformant program (modulo any typos).

Regards

Christoph
-- 
http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html
LiDIA: http://www.informatik.tu-darmstadt.de/TI/LiDIA/Welcome.html

Hello!

I just want to ask what way is recomended when including code fragments 
in my documentation. Up till now I have been using this:

/**
  * <code>
  *   int i = foo();
  * </code>
  */

This works fine when generating html docs but will it work ok with other 
document formats? When I look at the generated latex documentation it 
doesn't look nice at all.

Any thoughts on this?

Regards,
Mattias

Hi all,

I've filed a new bug of doxygen to Bugzilla (id#148761), whose subject is 
"Perl module produced by doxygen results in syntax error".

I am seeking for help from you all to tackle the problem. 

I am also wondering are there some guys who have experience using doxygen 
to generate perl module or xml. And do they work fine at your side?

Thanks & Best Regards,

Doug Wang(王 景文)
Globalization Certification Lab, CSDL, IBM China
E-mail:jwwang@...
Please visit GCL website: http://gcl.cn.ibm.com
===================================================================================
Creativity is allowing yourself to make mistakes. Art is knowing which 
ones to keep

SGkgRGltaXRyaSENCiANClRoYW5rcyBmb3IgeW91ciBhbnN3ZXIhIEkndmUgdHJpZWQgYWdhaW4g
d2l0aCB5b3VyIGV4YW1wbGUgYW5kIG5vdyBpdCB3b3Jrcy4uLiBubyBpZGVhIHdoYXQgd2FzIHdy
b25nIGJlZm9yZSBJIHdyb3RlIHRoZSBtZXNzYWdlLg0KIA0KQW5kcmVhcw0KIA0KDQoJLS0tLS1V
cnNwcsO8bmdsaWNoZSBOYWNocmljaHQtLS0tLSANCglWb246IERpbWl0cmkgdmFuIEhlZXNjaCBb
bWFpbHRvOmRpbWl0cmlAc3RhY2submxdIA0KCUdlc2VuZGV0OiBNaSAyOC4wNy4yMDA0IDE5OjUy
IA0KCUFuOiBTY2hyZWliZXIsIEFuZHJlYXMgDQoJQ2M6IGRveHlnZW4tdXNlcnNAbGlzdHMuc291
cmNlZm9yZ2UubmV0IA0KCUJldHJlZmY6IFJlOiBbRG94eWdlbi11c2Vyc10gTWVtYmVyIGdyb3Vw
IHdpdGggaGVhZGVyIGJ1dCB3aXRob3V0IGRldGFpbHMNCgkNCgkNCg0KCU9uIFdlZCwgSnVsIDI4
LCAyMDA0IGF0IDEwOjQ3OjE4QU0gKzAyMDAsIFNjaHJlaWJlciwgQW5kcmVhcyB3cm90ZToNCgk+
IEhhbGxvIQ0KCT4gDQoJPiBJIHdvdWxkIGxpa2UgdG8gZ3JvdXAgc29tZSBtZW1iZXIgdmFyaWFi
bGVzIGFuZCBnaXZlIHRoZW0gYSBoZWFkZXIsIGJ1dCBuZWl0aGVyIGRldGFpbGVkIGluZm9ybWF0
aW9uIGluIHRoZSBoZWFkZXIgbm9yIGFueSBkZXNjcmlwdGlvbiBmb3IgdGhlIHBhcnRpY3VsYXIg
bWVtYmVycy4gSSBoYXZlIG9ubHkgYmVlbiBzdWNjZXNzZnVsIGluIGdyb3VwaW5nIHRoZW0gd2l0
aCB0aGUgZm9sbG93aW5nIGNvZGUsIGJ1dCB3aGljaCBjb250YWlucyBhIGRldGFpbGVkIGdyb3Vw
IGRlc2NyaXB0aW9uLiBXaGVuIEkgcmVtb3ZlIHRoaXMgbGluZSwgb25seSB0aGUgaGVhZGVyIGFw
cGVhcnMsIGJ1dCB0aGUgbWVtYmVycyBhcmUgbm90IHNob3duLg0KCT4gDQoJPiAgICAgLyoqIEBu
YW1lIEJ1dHRvbiBwb2ludGVycw0KCT4gICAgICAgKiAgRGV0YWlsZWQgZ3JvdXAgZGVzY3JpcHRp
b24NCgk+ICAgICAgICpAew0KCT4gICAgICAgKi8gICANCgk+ICAgICBRUHVzaEJ1dHRvbiogbV9w
YnRuQWNjZXB0Ow0KCT4gICAgIFFQdXNoQnV0dG9uKiBtX3BidG5EaXNjYXJkOw0KCT4gICAgIFFC
dXR0b25Hcm91cCogbV9wYnRuZ3JwQ2xlYXI7DQoJPiAgICAgUUJ1dHRvbkdyb3VwKiBtX3BidG5n
cnBBZGQ7ICAgDQoJPiAgICAgLypAfSovDQoJPiANCgk+IElzIHRoZXJlIGEgcG9zc2liaWxpdHkg
b2YgYWNoaWV2aW5nIHRoZSBzYW1lIHJlc3VsdCBidXQgd2l0aG91dCB0aGUgZGV0YWlsZWQgZ3Jv
dXAgZGVzY3JpcHRpb24/DQoJDQoJU2hvdWxkIHdvcmsgbGlrZSBleHBlY3RlZCwgaW4gZmFjdCB0
aGUgZm9sbG93aW5nIHdvcmtzIGZpbmUgZm9yIG1lOg0KCQ0KCS8qKiBBIHRlc3Qgd2l0aCBtZW1i
ZXIgZ3JvdXBpbmcgKi8NCgljbGFzcyBUZXN0DQoJew0KCSAgcHVibGljOg0KCSAgLyoqIEBuYW1l
IEJ1dHRvbiBwb2ludGVycw0KCSAgICogIEB7DQoJICAgKi8NCgkgIFFQdXNoQnV0dG9uKiBtX3Bi
dG5BY2NlcHQ7DQoJICBRUHVzaEJ1dHRvbiogbV9wYnRuRGlzY2FyZDsNCgkgIFFCdXR0b25Hcm91
cCogbV9wYnRuZ3JwQ2xlYXI7DQoJICBRQnV0dG9uR3JvdXAqIG1fcGJ0bmdycEFkZDsNCgkgIC8q
IEB9ICovDQoJfTsNCgkNCglTbywgcGxlYXNlIGNvbnN0cnVjdCBhbiBleGFtcGxlIHRoYXQgZG9l
c24ndCB3b3JrLg0KCQ0KCVJlZ2FyZHMsDQoJICBEaW1pdHJpDQoJDQoJDQoJDQoNCg==

Hi all,
 
I´m using the latest version 1-3-8 of doxygen. I came
across a problem in HTML output when using
CREATE_SUBDIRS=YES and including images in my
documentation.

I included them as follows:
 
in file MyClass.h
/**
description...
 
@image html myPicture.jpg
*/
class MyClass : public MyBaseClass
{
...
}
 
in configuration file:
IMAGE_PATH=..\..\images
and myPicture.jpg is stored in "images".
 
now for HTML ouput the generated documentation file
classMyClass.html is stored in ...\html\d7\d2b and
with it the inheritance image classMyClass.png but the
picture I included (myPicture.jpg) is stored directly
under ...\html
so it is not displayed when I open classMyClass.html.

If I set CREATE_SUBDIRS=NO everything works fine.
 
Any suggestions?
Thanks
Achim


	

	
		
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

We use a cron job to build the API docs each night. It runs a makefile
to build the dox, and copy images, Javascript, etc. from a "baggage"
directory to the output directory. The cron job then e-mails the Doxygen
log file to the interested parties. This all works quite well.

Adding necessary features is important, and IMHO, you do an awesome job
of maintaining Doxygen. It is also my humble opinion that it's important
to avoid bloat with features that are useful but are easily accomplished
with scripts or another part of the process. Sometimes it's a hard call,
everyone here is "very" impressed with this tool and its continual
improvement.

Thanks Dimitri for all your good work!


-----Original Message-----
From: doxygen-users-admin@...
[mailto:doxygen-users-admin@...] On Behalf Of Dimitri
van Heesch
Sent: Wednesday, July 28, 2004 11:05 AM
To: Gill, Martin S
Cc: doxygen-users@...
Subject: Re: [Doxygen-users] Images in output


On Wed, Jul 28, 2004 at 02:57:20PM +0100, Gill, Martin S wrote:
>=20
> Hi!
> =20
> I'm trying to configure doxygen so that I can include my own images=20
> and styles in the output HTML.
> =20
> This needs to be done for multiple projects (read dozens) and I want=20
> some way of automating it.
> =20
> I've had not problems with the header and footer, and stylesheet, but=20
> what I cannot figure out is how to get doxygen to copy images I need=20
> into the output directory.
> =20
> For example, I want a logo in the header, and I want doxygen to copy=20
> this from a standard location into the output folder (like it does for

> the stylesheet, and it's own doxygen.png logo).
> =20
> Can anyone help me with this please?

This is basically a task for the "cp" command (aka "copy" on some
platforms). Just wrap it together a call to doxygen into a script and
ready you are. If you want something reusable you could extract the
output dir from the config file.

Of course I can build that functionality into doxygen via a=20
COPY_THESE_FILES_PLEASE option, but where does it end?
Next someone wants to receive a mail with the warnings generated by
doxygen, does doxygen need a built-in mail client as well?
doxygen!=3Demacs ;-)

Regards,
  Dimitri


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=3D4721&alloc_id=3D10040&op=3Dclick
_______________________________________________
Doxygen-users mailing list
Doxygen-users@...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Hi!
 
I'm trying to configure doxygen so that I can include my own images and
styles in the output HTML.
 
This needs to be done for multiple projects (read dozens) and I want some
way of automating it.
 
I've had not problems with the header and footer, and stylesheet, but what I
cannot figure out is how to get doxygen to copy images I need into the
output directory.
 
For example, I want a logo in the header, and I want doxygen to copy this
from a standard location into the output folder (like it does for the
stylesheet, and it's own doxygen.png logo).
 
Can anyone help me with this please?
 
thanks,
 
      Martin
 


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

SGFsbG8hDQogDQpJIHdvdWxkIGxpa2UgdG8gZ3JvdXAgc29tZSBtZW1iZXIgdmFyaWFibGVzIGFu
ZCBnaXZlIHRoZW0gYSBoZWFkZXIsIGJ1dCBuZWl0aGVyIGRldGFpbGVkIGluZm9ybWF0aW9uIGlu
IHRoZSBoZWFkZXIgbm9yIGFueSBkZXNjcmlwdGlvbiBmb3IgdGhlIHBhcnRpY3VsYXIgbWVtYmVy
cy4gSSBoYXZlIG9ubHkgYmVlbiBzdWNjZXNzZnVsIGluIGdyb3VwaW5nIHRoZW0gd2l0aCB0aGUg
Zm9sbG93aW5nIGNvZGUsIGJ1dCB3aGljaCBjb250YWlucyBhIGRldGFpbGVkIGdyb3VwIGRlc2Ny
aXB0aW9uLiBXaGVuIEkgcmVtb3ZlIHRoaXMgbGluZSwgb25seSB0aGUgaGVhZGVyIGFwcGVhcnMs
IGJ1dCB0aGUgbWVtYmVycyBhcmUgbm90IHNob3duLg0KIA0KICAgIC8qKiBAbmFtZSBCdXR0b24g
cG9pbnRlcnMNCiAgICAgICogIERldGFpbGVkIGdyb3VwIGRlc2NyaXB0aW9uDQogICAgICAqQHsN
CiAgICAgICovICAgIA0KICAgIFFQdXNoQnV0dG9uKiBtX3BidG5BY2NlcHQ7DQogICAgUVB1c2hC
dXR0b24qIG1fcGJ0bkRpc2NhcmQ7DQogICAgUUJ1dHRvbkdyb3VwKiBtX3BidG5ncnBDbGVhcjsN
CiAgICBRQnV0dG9uR3JvdXAqIG1fcGJ0bmdycEFkZDsgICAgDQogICAgLypAfSovDQogDQpJcyB0
aGVyZSBhIHBvc3NpYmlsaXR5IG9mIGFjaGlldmluZyB0aGUgc2FtZSByZXN1bHQgYnV0IHdpdGhv
dXQgdGhlIGRldGFpbGVkIGdyb3VwIGRlc2NyaXB0aW9uPw0KIA0KVGhhbmtzIGZvciB5b3VyIGFu
c3dlcnMhDQogDQpBbmRyZWFzDQogDQo=

Hi...

I am having a bit of a problem with the @addtogroup command.  What I
would like to do is have a separate page containing the documentation
for the whole group, and add the function definitions and so on to the
end of this documentation with @addtogroup.  (The main documentation
might easily run to 10 or 20 pages, so I have strong incentive not to
paste it to the top of one of my *.c or *.h files.)  

Let's say I have a page called aaa_docpage.doc:

--------------------------------------------------

/**
 * \addtogroup Foo2 Foo2 module

Main documentation goes here...

*/
/*@{*/
/*@}*/

--------------------------------------------------

Even though I add an @addtogroup command to the top of each file whose
functions I want in the Foo2 group, they are not added to the end of the
"Foo2 module" page. Instead, this contains the main documentation and
nothing else.  However, if I delete the page aaa_docpage.doc or make it
empty, the "Foo2 module" page contains all of the functions I wanted
(but is of course lacking the main documentation).

Things I have tried without success:

* using @defgroup instead of @addtogroup in aaa_docpage.doc
* adding a dummy #define between the brackets on aaa_docpage.doc
* tweaking the file order in the INPUT list in the configuration file

Help would be gratefully appreciated.

By the way, if the maintainers are listening, I have a feature request.
It would be nice to include @section commands in the documentation for a
group.

Thanks,

Ron Hale-Evans

--
Ron Hale-Evans | ron.hale-evans@...
Open Interface North America, Inc.
http://www.oi-us.com | http://www.openinterface.com | 
http://www.oi-direct.com

Is there a configuration switch, or some method in which one can =
preserve the formating of the source code documentation (ie: the new =
lines) when producing the html documentation?

eg:
could you please
preserve=20
this formating?

should remain that way, and not turn into:
could you please preserve this formating?

I do not wish to have to manually change all the documentation in some =
way in order to create new lines with doxygen.

Thanks.

Hi,

consider following simplified situation:

  //! My documented class.
  class MyClass {
  
    //! A vector of positive values.
    std::vector<int> v;
  
    //! The sup-norm of #v.
    /** The maximum of all members of #v.
     **
     ** @invariant max_v == std::max(v.begin(), v.end())
     **/
    int max_v;
  
  public:
    // ...
  };

I'd like to link from the `v' in v.begin() and v.end() to the
documentation of the member v. But all my attempts failed except for
"brute force": 

  std::max(@link #v v.begin()@endlink, @link #v v.end()@endlink)

For some reason, however, I'd like to restrict the link to the name of
the data member. (I actually want to link somewhere else from the
member function name.)

I first tried `#v.begin()' but that was copied verbatim to the
documentation - I guess doxygen treats it as a filename due to the dot
in front of `begin()'.

My second attemp `@link #v v@...()' also failed since
`@endlink' was not recognized. It works if I write 
`@link #v v@... .begin()', but then there is an unmotivated extra
blank in front of `.begin()' in the documentation.

Is it possible to make doxygen restrict the hyperlink to `v'?

Regards

Christoph
-- 
http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html
LiDIA: http://www.informatik.tu-darmstadt.de/TI/LiDIA/Welcome.html

Hi all,

I've read about doxygen and other langages : it seems that people use 
either INPUT_FILTER, flex or preprocessing.

I would like to comment
    - script files :
            I've already do a script to transform the original files 
into files readable by doxygen. But is there                         
something better ? Should I put my transformation script in the 
INPUT_FILTER ? Do I have to treat in                 this script the 
different file type if I want that my script applies only to certain 
file type ?

    - idl :
            NOT idl (intrface definition langage) for CORBA, but idl 
(interactive data langage) like Yorick or Matlab             langage. Is 
there some INPUT_FILTER available ? or do you know on flex ?

    - fortran :
             Is there some INPUT_FILTER available ? or something else ?

Thank you.

Laurence Gluck.

Hi all,

I´m trying to use the file distribution via
CREATE_SUBDIRS and the possibility to introduce my own
html stylesheet via HTML_STYLESHEET together.
I think I came across some minor bug here.

1. THATS OK
If I use CREATE_SUBDIRS=YES and no personal stylesheet
(HTML_STYLESHEET=empty) the files are distibuted
correctly in the subdirectories and the default
stylesheet doxygen.css is used. doxygen.css is stored
directly under ../html. The stylesheet is called in
the distributed files via
<link href="../../doxygen.css" rel="stylesheet"
type="text/css">
doxygen.css is found via this relative path correctly.

2. NOW THE PROBLEM/BUG
If I use CREATE_SUBDIRS=YES and my personal stylesheet
(HTML_STYLESHEET=../myStyles.css) the files are
distibuted correctly in the subdirectories and my
stylesheet myStyles.css is used. myStyles.css is
stored directly under ../html. Now the call in the
distributed files looks like
<link href="myStyles.css" rel="stylesheet"
type="text/css">
SO NO RELATIVE PATH HERE AND THEREFORE myStyles.css
can´t be found by the distributed files.

3. A WORKAROUND
Use proceding in 1. and then rename myStyles.css to
doxygen.css and store it under .../html.

Just don´t know whether thats a minor bug or not.

Regards
Achim


	

	
		
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

Hello,

I recently started using doxygen. It's a great tool for documenting cpp 
sources. And the created html files look quite good.
Now I have a little (?) problem with creating a documentation from flex/bison 
files.
I use the same doxygen comment style for functions and vars as in cpp. But 
only the file description is shown in html. After looking through the doxygen 
docs I found a way to exclude code which caused the problem (e.g. %{ etc.) by 
using defines for preprocessing. The html files shows now all functions and 
vars as wanted. But I'm not able to compile the flex/bison files because flex 
and bison don't know the define syntax (e.g. #ifndef ...).
Is there a way to create a documentation for flex/bison files without defines?

Regards,
Ivica

---------------------------------
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!

Hi all,

as Dimitri suggested I migrated to version 1-3-8
and the problem with the formulas and inheritance
diagrams vanished :-)

but the problem with images that I included myself
still exists...

I included them as follows:

in file MyClass.h
/**
description...

@image html myPicture.jpg
*/
class MyClass : public MyBaseClass
{
...
}

in configuration file:
IMAGE_PATH=..\..\images
and myPicture.jpg is stored in "images".

now the generated documentation file classMyClass.html
is stored in ...\html\d7\d2b and with it the
inheritance image classMyClass.png
but the picture I included (myPicture.jpg) is stored
directly under ...\html
so it is not displayed when I open classMyClass.html.

Any suggestions?
Thanks
Achim

> > Hi all,
> > 
> > I?m using doxygen 1-3-7.
> > I?m using a lot of formulas and pictures in
> > documentation and as long as I don?t use
> > CREATE_SUBDIRS they all show up nicely in the HTML
> > version of the documentation.
> > 
> > As I have a large codebase I?m thinking about
> using
> > CREATE_SUBDIRS to distribute the files.
> > When I set CREATE_SUBDIRS=YES the generated files
> get
> > distributed correctly but the pictures and
> formulas
> > don?t show up anymore. All I see is the according
> > placeholder.
> > 
> > What am I doing wrong?
> > Do I have to use anything else besides
> CREATE_SUBDIRS?
> 
> Please upgrade to 1.3.8 were these problems should
> be fixed...
> 
> Regards,
>   Dimitri



	
		
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

Dnia 2004-07-20 22:54, Użytkownik Marcin Zajączkowski napisał:
> I have little old C code for embedded machine to document and last time 
> I found:
> patch/file.h:55: Problem during constant expression evaluation: parse error
> 
> This is in lines like:
> #error (C_SCR_W != L_SCR_W) || (C_SCR_H != L_SCR_H)
> #error file.c : Some text
> 
> Is #error something prohibited in use with Doxygen or it's some bug?
> I tested with latest CVS build (20040718).

Could somebody confirm this? If it's bug I'll submit it to bugzilla.

Regards
Marcin

I will be out of the office starting  23-07-2004 and will not return until
16-08-2004.

I will respond to your message when I return. Please contact Geoff Burns,
G.Burns@... in case of urgency.

Best Regards,

--Marco

#error means that the parser should exit in normal C/C++ code.  It is
usually used after #if's to make sure that certain #defines exist =
(possibly
in sane combinations).=20
It is usually a sign that you haven't given the pre-processor the right
combination of header files or command line "-D" arguments.

If you fed this same code to the compiler, it would also not produce =
any
valid executable, so I'm not sure that Doxygen should ignore the =
#error.

In this case, you should look at defining "C_SCR_W", "C_SCR_H", etc. =
either
by including the correct header file or by the command line/config =
file, and
I think your problem will go away.

Keith

-----Original Message-----
From: Marcin Zajaczkowski [mailto:mszpak@...]
Sent: Monday, July 26, 2004 6:54 PM
To: Doxygen-users@...
Subject: Re: [Doxygen-users] Parse error


Dnia 2004-07-20 22:54, U=BFytkownik Marcin Zaj=B1czkowski napisa=B3:
> I have little old C code for embedded machine to document and last =
time=20
> I found:
> patch/file.h:55: Problem during constant expression evaluation: parse
error
>=20
> This is in lines like:
> #error (C_SCR_W !=3D L_SCR_W) || (C_SCR_H !=3D L_SCR_H)
> #error file.c : Some text
>=20
> Is #error something prohibited in use with Doxygen or it's some bug?
> I tested with latest CVS build (20040718).

Could somebody confirm this? If it's bug I'll submit it to bugzilla.

Regards
Marcin


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=3D4721&alloc_id=3D10040&op=3Dclick
_______________________________________________
Doxygen-users mailing list
Doxygen-users@...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

I have a class of the form:

Class foo {
	void bar(unsigned int);
	void bar(float);
	void bar(char);
};

When doxygen makes the html reference, in the "class reference" page for
foo, it shows all three instances of bar with the associated comments.
In the "file reference" page for foo.cpp (and foo.h), it only shows one
instance of bar despite the fact that there is only one .cpp (and one
.h) file being processed and it has all three functions inside it.=20

This is probably a FAQ somewhere.  Can some kind soul mail me a pointer?

Thanks.

Chris