doxygen-users

RE: [Doxygen-users] Bug related to grouping and namespaces.

[Dalton, B. <Bar...@ra...>]

I didn't get the attachment but I think I have experienced a similar
problem. The case I had was grouping functions defined at namespace scope
(as opposed to member fns of a class). I found that if I did a @ingroup in
both the header and implementation file then the function was documented
properly.

Barney

> -----Original Message-----
> From: Carlo Wood [mailto:ca...@al...]
> Sent: 21 November 2001 12:59 AM
> To: Dimitri van Heesch
> Cc: dox...@li...
> Subject: [Doxygen-users] Bug related to grouping and namespaces.
> 
> 
> I am having problems with grouping.
> The need is to create a seperate page for certain stuff,
> and everything in a certain group goes onto that page
> (I thought that was the intention of groups anyway).
> 
> However, instead the group page only contains the
> general documentation, the functions that I added to
> the group only appear on the namespace page and their
> Detailed Information disappears completely...
> 
> I've attached a small tar ball called 'doxybug.tar.gz'.
> Extract it and it will create a directory 'doxybug'.
> cd into doxybug/documentation/ and type 'make'.
> 
> Next look at doxybug/documentation/html/namespacelibcw_1_1debug.html
> and you will find that it contains the two functions,
> which SHOULD have gone into 
> doxybug/documentation/html/group__demangle.html
> 
> Looking at doxybug/documentation/html/group__demangle.html you'll
> see that it only contains the data from demangle3.cc.
> The detailed info is no where (although this is the page that we
> get to when you click 'more...' after the functions).
> 
> Note that if you remove the *code* (namespace libcw {... etc)
> in demangle3.cc, then everything works as I want it to work.
> 
> -- 
> Carlo Wood <ca...@al...>
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
> 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
pos...@ra....

This footnote also confirms that this email message has been scanned
for the presence of computer viruses known at the time of sending.

www.radioscape.com
**********************************************************************

RE: [Doxygen-users] Bug related to grouping and namespaces.

[Dalton, B. <Bar...@ra...>]

> I found another bug by the way: the order of reading the input
> files matters for addtogroup and defgroup.  I had one single
> defgroup in one file, and used addtogroup everywhere else.
> But doxygen refused to process the defgroup because it already
> (first) saw an addtogroup.  I think that the order in which
> input files are read shouldn't matter here.

I had this problem too. I had to replace the defgroup by an addtogroup.
Barney


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
pos...@ra....

This footnote also confirms that this email message has been scanned
for the presence of computer viruses known at the time of sending.

www.radioscape.com
**********************************************************************

Re: [Doxygen-users] Bug related to grouping and namespaces.

['Carlo W. <ca...@al...>]

On Wed, Nov 21, 2001 at 09:16:29AM -0000, Dalton, Barnaby wrote:
> 
> I didn't get the attachment but I think I have experienced a similar
> problem. The case I had was grouping functions defined at namespace scope
> (as opposed to member fns of a class). I found that if I did a @ingroup in
> both the header and implementation file then the function was documented
> properly.
> 
> Barney

Argh - I forgot the attachment :).
I'll attach it now.  But you're right, that solved the problem.
Nevertheless, this is a bug.  I suggest to solve it as follows:

When a function (prototype, definition and/or extern declaration)
is marked as belonging to a group, then that should take
precedence over a (previously read) definition without any
comment.

I found another bug by the way: the order of reading the input
files matters for addtogroup and defgroup.  I had one single
defgroup in one file, and used addtogroup everywhere else.
But doxygen refused to process the defgroup because it already
(first) saw an addtogroup.  I think that the order in which
input files are read shouldn't matter here.

-- 
Carlo Wood <ca...@al...>