doxygen-users — List for users of doxygen

Re: [Doxygen-users] Building Doxygen-1.2.14 with gcc on Solaris 7

[Dimitri v. H. <di...@st...>]

On Tue, Mar 26, 2002 at 09:18:25AM -0000, Al Slater wrote:
> Which is the right Bison version?

Versions 1.30 to 1.34 are broken as far as I know, older or newer
versions should work. This is not a doxygen only problem by the
way, it happens with most C++ based bison files. Look at the bison mailing
list for more info on this topic.

Regards,
  Dimitri

RE: [Doxygen-users] TechPubs Tools...

[Glenn M. <gle...@vo...>]

Sorry. I forgot to include a common package needed by the conversion =
tool.

> -----Original Message-----
> From: Glenn Maxey=20
> Sent: Tuesday, March 26, 2002 8:31 AM
> To: Tadhg MacCarthy
> Cc: dox...@li...
> Subject: RE: [Doxygen-users] TechPubs Tools...
>=20
>=20
> Your wish is my command.=20
>=20
> [Dimitri, you might want to put this link and the attached=20
> perl file into your tools page, as well.]
>=20
> http://www.better-homepage.com/java/java-applets-toc.html
>=20
> I ended up contacting the system administrator, because the=20
> credit card processing company he was using for that old web=20
> page is no longer in business. Eventually we were able to pay=20
> the $99 and get the source code and unlimited distribution=20
> rights. (As it stands, you can get a freebie, evaluation version.)
>=20
> It really is a pretty slick application.
>=20
> Also, attached is a Perl script that will convert from the=20
> tree.js that Doxygen produces (when you have TREEVIEW turned=20
> on) to the script format needed by the Java applet. No=20
> disrespect intended to the writers of Doxygen, but I found=20
> that the TREEVIEW javascript to be seriously underpowered=20
> when confronted with larger systems -- underpowered by the=20
> browsers. (I tried manipulating tree.js files to combine them=20
> from multiple projects into one. I'd get memory complaints=20
> from IE, but it'd eventually load; NE would just hang.)=20
>=20
> At any rate, this little baby is awesome. More importantly,=20
> it supports nested script files. Hence, it is really easy to=20
> take the tree.js/tree.script files from multiple doxygen runs=20
> (and other output) and make a complete system.
>=20
> Enjoy.
>=20
> Glenn Maxey
> Technical Writer
> Voyant Technologies, Inc.
> 1765 West 121st Avenue
> Westminster, CO 80234-2301
> Tel. +1 303.223.5164
> Fax. +1 303.223.5275
> gle...@vo...
>=20
>=20
>=20
> > -----Original Message-----
> > From: Tadhg MacCarthy [mailto:tma...@bl...]
> > Sent: Monday, March 25, 2002 6:14 PM
> > To: Glenn Maxey
> > Subject: Re: [Doxygen-users] TechPubs Tools...
> >=20
> >=20
> > Hi Glenn,
> >=20
> > If you don't mind, can you send me a link to the Java applet=20
> > you are using
> > for TOC?
> >=20
> > Currently we are using a rather crude method of generating=20
> > TOC using a perl
> > script. A dynamic method would be much nicer.
> >=20
> > Thanks in Advance,
> > Tadhg
> >=20
> > TadhgMacCarthy
> > wwww.bhsoftware.com
> >=20
> >=20
>=20

RE: [Doxygen-users] TechPubs Tools...

[Glenn M. <gle...@vo...>]

Your wish is my command.=20

[Dimitri, you might want to put this link and the attached perl file =
into your tools page, as well.]

http://www.better-homepage.com/java/java-applets-toc.html

I ended up contacting the system administrator, because the credit card =
processing company he was using for that old web page is no longer in =
business. Eventually we were able to pay the $99 and get the source code =
and unlimited distribution rights. (As it stands, you can get a freebie, =
evaluation version.)

It really is a pretty slick application.

Also, attached is a Perl script that will convert from the tree.js that =
Doxygen produces (when you have TREEVIEW turned on) to the script format =
needed by the Java applet. No disrespect intended to the writers of =
Doxygen, but I found that the TREEVIEW javascript to be seriously =
underpowered when confronted with larger systems -- underpowered by the =
browsers. (I tried manipulating tree.js files to combine them from =
multiple projects into one. I'd get memory complaints from IE, but it'd =
eventually load; NE would just hang.)=20

At any rate, this little baby is awesome. More importantly, it supports =
nested script files. Hence, it is really easy to take the =
tree.js/tree.script files from multiple doxygen runs (and other output) =
and make a complete system.

Enjoy.

Glenn Maxey
Technical Writer
Voyant Technologies, Inc.
1765 West 121st Avenue
Westminster, CO 80234-2301
Tel. +1 303.223.5164
Fax. +1 303.223.5275
gle...@vo...



> -----Original Message-----
> From: Tadhg MacCarthy [mailto:tma...@bl...]
> Sent: Monday, March 25, 2002 6:14 PM
> To: Glenn Maxey
> Subject: Re: [Doxygen-users] TechPubs Tools...
>=20
>=20
> Hi Glenn,
>=20
> If you don't mind, can you send me a link to the Java applet=20
> you are using
> for TOC?
>=20
> Currently we are using a rather crude method of generating=20
> TOC using a perl
> script. A dynamic method would be much nicer.
>=20
> Thanks in Advance,
> Tadhg
>=20
> TadhgMacCarthy
> wwww.bhsoftware.com
>=20
>=20

Re: [Doxygen-users] Building Doxygen-1.2.14 with gcc on Solaris 7

[Claus-Peter K. <pet...@un...>]

Hi,

on http://www.stack.nl/~dimitri/doxygen/install.html#install it says
1.29, which i installed just a minute ago, but i don't now how to tell
g++ to use the version.

 Tschau, Peter.

-- 
Find scientific documents for computer science: http://www.daffodil.de

University of Dortmund | email : kl...@ls...
Informatik VI          | www   : http://ls6-www.cs.uni-dortmund.de/~klas
Claus-Peter Klas       | phone : +49 231 755 5863
D-44221 Dortmund       | fax   : +49 231 755 2405           

RE: [Doxygen-users] Building Doxygen-1.2.14 with gcc on Solaris 7

[Al S. <al....@sc...>]

Which is the right Bison version?

Al

> -----Original Message-----
> From: kl...@fr...
> [mailto:kl...@fr...]On Behalf Of Claus-Peter Klas
> Sent: 26 March 2002 09:11
> To: al....@sc...
> Cc: dox...@li...
> Subject: Re: [Doxygen-users] Building Doxygen-1.2.14 with gcc 
> on Solaris
> 7
> 
> 
> Sorry, just found the error with the wrong bison version.
> 
>  Tschau, Peter.
> 
> 

Re: [Doxygen-users] Building Doxygen-1.2.14 with gcc on Solaris 7

[Claus-Peter K. <pet...@un...>]

Sorry, just found the error with the wrong bison version.

 Tschau, Peter.

Re: [Doxygen-users] Building Doxygen-1.2.14 with gcc on Solaris 7

[Claus-Peter K. <pet...@un...>]

"Al Slater" <al....@sc...> writes:

> From: "Al Slater" <al....@sc...>
> Subject: [Doxygen-users] Building Doxygen-1.2.14 with gcc on Solaris 7
> To: <dox...@li...>
> Date: Tue, 26 Mar 2002 08:15:39 -0000
> Reply-To: <al....@sc...>
>
> Hi
>
> I am trying to build Doxygen-1.2.14 with gcc on Solaris 7 and I get the the
> following error message:
>
> g++ -c -Wall -W -O2 -I../qtools -o ../objects/ce_parse.o ce_parse.cpp
> ce_parse.cpp:348: member `class CPPValue
I have the same problem with the current cvs repository and
gcc 2.95.4 on a debian woody with kernel 2.4.18.

 Tschau, Peter.

[Doxygen-users] Building Doxygen-1.2.14 with gcc on Solaris 7

[Al S. <al....@sc...>]

Hi

I am trying to build Doxygen-1.2.14 with gcc on Solaris 7 and I get the the
following error message:

g++ -c -Wall -W -O2 -I../qtools -o ../objects/ce_parse.o ce_parse.cpp
ce_parse.cpp:348: member `class CPPValue yyalloc::yyvs' with constructor not
allowed in union


Any ideas?

regards

Al Slater

Support Supervisor
Stanton Consultancy
al....@sc...
+44 (0)1273 666607

[Doxygen-users] TechPubs Tools...

[Glenn M. <gle...@vo...>]

Servus Claus-Peter,

I cannot attest to whether or not you can have classes with the same
name in the package.

However, I can attest to the fact that your life will be much easier if
you break your project up. Smaller builds are better. Have separate
configuration files for different areas of the code; have them dump to
their own (parallel) directories. The TAGFILES and GENERATE_TAGFILES (my
spelling might be off) options in the configuration file will aid you in
establishing dependencies between the projects. If you have mutual or
two-way dependencies, you may need to run doxygen twice so that it
generate the tag files and then use them. Not a big deal.

I guess I'm the culprit for the TechPubs Tools, also available at
www.voyanttech.com/tp_tools.zip (1.8 MB). Unzip and launch
tp_tools/_start_here.zip. Sie durfen Fragen auch auf Deutsch stellen.

I've taken the tools to the next level since then, but I'm not sure that
I'll be able to release them (all). Aside from having too much to do at
work, I'm now using a really cool Java applet for doing the table of
contents. We purchased the source, but that doesn't mean that we can
freely distribute it or the compiled applets for others to then use.
Still, for $100 bucks, it is way cool and better than the crude TOC's in
my tp_tools.

I do have some enhancements to the navigation and index program.
Basically, I'm now finding ALL doxytags and am exporting them as index
tokens during my post-processing. On one of my assignments composed of
multiple projects, I get 25634 index tokens mostly from doxygen, which I
expand into 69409... It's not as bad as it sounds. (The next version of
the index also fixes some special perl character problems, such as
happens with "operator++" or "operator[]".) Another cool tool I've been
working on grep's through the code for known items or prefixes of known
items (assuming that developer's were consistent in naming things.) It
extracts that definition along with any doxygen comments from the source
and dumps it into a temporary file. I then run doxygen on the temporary
file and thereby eliminate lots of "noise" for the reader.

In Microsoft-speak, you can expect me to publish the newer versions in
Q3 2002. :)

Glenn Maxey
Technical Writer
Voyant Technologies, Inc.
1765 West 121st Avenue
Westminster, CO 80234-2301
Tel. +1 303.223.5164
Fax. +1 303.223.5275
gle...@vo...


> -----Original Message-----
> From: Martin Bosticky [mailto:MBo...@op...]
> Sent: Monday, March 25, 2002 3:35 PM
> To: dox...@li...
> Subject: RE: [Doxygen-users] Newbie Question about java classes with
> same name
>=20
>=20
> My understanding is that you can't have class names with same=20
> name. I recall
> reading it somewhere in documentation. you are not supposed=20
> to be creating
> large packages like that. instead you can create a multiple=20
> of small ones
> and then join them up using a tool such as The TechPubs Tools=20
> (TPT) (see
> helper tools scripts on dimiti's=20
> website (http://www.stack.nl/~dimitri/doxygen/download.html#helpers)
>=20
> I ran into similar problem a short while ago.
>=20
> Please anyone correct me if i am wrong.
>=20
>=20
> Martin.
>=20
>=20
>=20
> -----Original Message-----
> From: Claus-Peter Klas [mailto:pet...@un...]
> Sent: Tuesday, 26 March 2002 0:29
> To: dox...@li...
> Subject: [Doxygen-users] Newbie Question about java classes with same
> name
>=20
>=20
> Hello,
>=20
> i try to doxy out project, which is quite large by now and we have
> some classes with the same name in different packages. But doxygen
> seems to mix these up in one classClass.html  file. Is it a bug or do
> i have to change some config parameters.
>=20
>  Tschau, Peter.
>=20
> --=20
> Find scientific documents for computer science: http://www.daffodil.de
>=20
> University of Dortmund | email : kl...@ls...
> Informatik VI          | www   :=20
> http://ls6-www.cs.uni-dortmund.de/~klas
> Claus-Peter Klas       | phone : +49 231 755 5863
> D-44221 Dortmund       | fax   : +49 231 755 2405          =20
>=20
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>=20
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>=20

Re: [Doxygen-users] Doxygen Source Documentation Problems

[Scot W. <sc...@wi...>]

> I'm trying to build the documentation to doxygen, I noticed it's not
> built into the source code, I can't imagine why, the source DEFINIETLY needs
> documenting, external documentation like this just isnt enough I find,
> but anyway.

Doxygen is for documenting variables and functions, not programs.
Doxygen is a program.

You'll first need to expand Doxygen as previously mentioned to support things 
such as program flow documentation.  ("This is an IF statement.  See the IF 
statement run over here when the array gets too full.  Run, IF, Run!")

Well, the source code HTML creator does understand some language keywords and 
puts "IF" in a pretty color, but there's no way to attach documentation to 
code, only to declarations.

RE: [Doxygen-users] Newbie Question about java classes with same name

[Martin B. <MBo...@op...>]

My understanding is that you can't have class names with same name. I recall
reading it somewhere in documentation. you are not supposed to be creating
large packages like that. instead you can create a multiple of small ones
and then join them up using a tool such as The TechPubs Tools (TPT) (see
helper tools scripts on dimiti's 
website (http://www.stack.nl/~dimitri/doxygen/download.html#helpers)

I ran into similar problem a short while ago.

Please anyone correct me if i am wrong.


Martin.



-----Original Message-----
From: Claus-Peter Klas [mailto:pet...@un...]
Sent: Tuesday, 26 March 2002 0:29
To: dox...@li...
Subject: [Doxygen-users] Newbie Question about java classes with same
name


Hello,

i try to doxy out project, which is quite large by now and we have
some classes with the same name in different packages. But doxygen
seems to mix these up in one classClass.html  file. Is it a bug or do
i have to change some config parameters.

 Tschau, Peter.

-- 
Find scientific documents for computer science: http://www.daffodil.de

University of Dortmund | email : kl...@ls...
Informatik VI          | www   : http://ls6-www.cs.uni-dortmund.de/~klas
Claus-Peter Klas       | phone : +49 231 755 5863
D-44221 Dortmund       | fax   : +49 231 755 2405           

_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] Newbie Question about java classes with same name

[Claus-Peter K. <pet...@un...>]

Hello,

i try to doxy out project, which is quite large by now and we have
some classes with the same name in different packages. But doxygen
seems to mix these up in one classClass.html  file. Is it a bug or do
i have to change some config parameters.

 Tschau, Peter.

-- 
Find scientific documents for computer science: http://www.daffodil.de

University of Dortmund | email : kl...@ls...
Informatik VI          | www   : http://ls6-www.cs.uni-dortmund.de/~klas
Claus-Peter Klas       | phone : +49 231 755 5863
D-44221 Dortmund       | fax   : +49 231 755 2405           

RE: [Doxygen-users] Doxygen Source Documentation Problems

[Prikryl,Petr <PRI...@sk...>]

Hi (is Evil really your name? :)

Evil Kosh wrote...

> I'm trying to build the documentation to doxygen, I noticed it's not built

> into the source code, I can't imagine why, the source DEFINIETLY needs 
> documenting, external documentation like this just isnt enough I find, but

> anyway.

Basically, documenting the doxygen source and the doxygen documentation
are apparently two different things.  You are right that it would be nice to

have the doxygen sources documented using itself.  On the other hand,
the doxygen documentation has a different purpose.  At the very beginning of
the documentation (Introduction) Dimitri says:

  "3.	You can even `abuse' doxygen for creating normal documentation
		(as I did for this manual)."

> I've disabled the Latex/Man page/XML output in the doxyfile configuration 
> file and when I try to make the documentation it STILL asks me for dvips 
> and latex, even though I only want HTML output, why is this?

It's because the documentation explicitly states that the LaTeX must be
used for generating the "LaTeX" logo (at least).  There is a fragment that
must be processed by LaTeX (producing DVI) and the result is processed
by other tools to get png version of the result.  You will not need LaTeX
if you do not use LaTeX fragments inside your documentation.

> anyway, I was thinking of cracking open the source more and attempting to 
> document it inline, rather than have an external set of documentation
which 
> is what we have now, what do people think, good idea? bad idea?  I did 
> originally want to help with doxygen myself, but I've found the lack of 
> documentation offputting, I have no idea what certain things do or why Qt 
> is required for a command line tool, wasnt STL enough?

I would recommend to contact Dimitri if you want to document the doxygen
sources.  For QT, I would prefer Standard C++ library instead of STL.
Well, we probably are talking about the same thing (STL was at the begining
of Standard C++).  My guess is that there was not a good implementation
of STL or Standard C++ Library portable to that many platforms and
compilers.
I do not know the QT, but it seems that it is more capable when working with
ASCII/some encoding/Unicode, for example.  Anyway, I would also like 
to know whether QT has some major advantages.

See you,
  Petr

[Doxygen-users] Doxygen Source Documentation Problems

[Evil K. <evi...@ya...>]

Hello,

I'm trying to build the documentation to doxygen, I noticed it's not built 
into the source code, I can't imagine why, the source DEFINIETLY needs 
documenting, external documentation like this just isnt enough I find, but 
anyway.

I've disabled the Latex/Man page/XML output in the doxyfile configuration 
file and when I try to make the documentation it STILL asks me for dvips 
and latex, even though I only want HTML output, why is this?

anyway, I was thinking of cracking open the source more and attempting to 
document it inline, rather than have an external set of documentation which 
is what we have now, what do people think, good idea? bad idea?  I did 
originally want to help with doxygen myself, but I've found the lack of 
documentation offputting, I have no idea what certain things do or why Qt 
is required for a command line tool, wasnt STL enough?  Anyway, enough rambling

kosh 



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[Doxygen-users] Doxygen-1.2.14-20020324 in CVS

[Dimitri v. H. <di...@st...>]

Hi,

This week's changelog looks as follows:
------------------------------------------------------------------------------
+ BUG: The argument of commands like \c did not produce a link to
       external documentation if possible, while links to local
       documentation were generated.
+ ADD: Improved support for Java. Packages are now treated like
       C++ namespaces and there is a new option OPTIMIZE_OUTPUT_JAVA
       that, when enabled, provides more Java-oriented output. Please
       report any Java-related problems that remain.
+ BUG: Improved source cross referencing for members inside
       (nested) classes/namespaces.
+ ADD: Made inheritance/collaboration diagrams accessible via the
       XML parser API (see addon/doxmlparser/include/doxmlintf.h).
------------------------------------------------------------------------------
Enjoy,
  Dimitri

Re: [Doxygen-users] Macro Expansion Problem

[Dimitri v. H. <di...@st...>]

On Fri, Mar 22, 2002 at 11:37:15AM -0800, Scott Inglis wrote:
> I have a macro that doesnt seem to expand. 
> 

> Any ideas on how to fix this warning? Is there anyway
> to see the macro expansion that doxygen creates? Maybe
> seeing the code could fix this.

You can run doxygen with the "-d Preprocessor" option to see
the output of the preprocessor.

Regards,
  Dimitri

AW: [Doxygen-users] Macro Expansion Problem

[<Kla...@it...>]

Don't know if this is your problem, but in the definition of a macro
with parameter(s), there must be no space between the macro name and the
opening parenthesis, so try
  #define CLASS_DECLARATION(ClassName)
instead of=20
  #define CLASS_DECLARATION (ClassName)

- Klaus

> -----Urspr=FCngliche Nachricht-----
> Von: Scott Inglis [mailto:gri...@ya...]
> Gesendet: Freitag, 22. M=E4rz 2002 20:37
> An: dox...@li...
> Betreff: [Doxygen-users] Macro Expansion Problem
>=20
>=20
> I have a macro that doesnt seem to expand.=20
>=20
> Here is the macro definition:
> #define CLASS_DECLARATION (ClassName)          \
> class ClassName : public UberTest::TestCase    \
> {                                              \
> public:                                        \
>    ClassName()                         {   }   \
>    ~ClassName()                        {   }   \
>                                                \
>    void run(void);                             \
> };                                             \
>=20
> Then I will declare a class like so in the header
> file.
> namespace Test
> {
>    CLASS_DECLARATION(TestClass);
> }
>=20
> The function declaration for run looks like this:
> void Test::TestClass::run(void)
> {
> }
>=20
> When I run doxygen, it gives me this warning:
> Warning: no matching class member found for
>   void Test::TestClass::run(void)
>=20
> I am guessing because it never expands the
> CLASS_DECLARATION macro.
>=20
> Here are my settings for the config:
> ENABLE_PREPROCESSING   =3D YES
> MACRO_EXPANSION        =3D YES
> EXPAND_ONLY_PREDEF     =3D YES
> SEARCH_INCLUDES        =3D=20
> INCLUDE_PATH           =3D=20
> INCLUDE_FILE_PATTERNS  =3D=20
> PREDEFINED             =3D=20
> EXPAND_AS_DEFINED      =3D CLASS_DECLARATION
> TEST_CASE_DECLARATION
> SKIP_FUNCTION_MACROS   =3D NO
>=20
>=20
> Any ideas on how to fix this warning? Is there anyway
> to see the macro expansion that doxygen creates? Maybe
> seeing the code could fix this.
>=20
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Movies - coverage of the 74th Academy Awards=AE
> http://movies.yahoo.com/
>=20
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>=20

[Doxygen-users] Macro Expansion Problem

[Scott I. <gri...@ya...>]

I have a macro that doesnt seem to expand. 

Here is the macro definition:
#define CLASS_DECLARATION (ClassName)          \
class ClassName : public UberTest::TestCase    \
{                                              \
public:                                        \
   ClassName()                         {   }   \
   ~ClassName()                        {   }   \
                                               \
   void run(void);                             \
};                                             \

Then I will declare a class like so in the header
file.
namespace Test
{
   CLASS_DECLARATION(TestClass);
}

The function declaration for run looks like this:
void Test::TestClass::run(void)
{
}

When I run doxygen, it gives me this warning:
Warning: no matching class member found for
  void Test::TestClass::run(void)

I am guessing because it never expands the
CLASS_DECLARATION macro.

Here are my settings for the config:
ENABLE_PREPROCESSING   = YES
MACRO_EXPANSION        = YES
EXPAND_ONLY_PREDEF     = YES
SEARCH_INCLUDES        = 
INCLUDE_PATH           = 
INCLUDE_FILE_PATTERNS  = 
PREDEFINED             = 
EXPAND_AS_DEFINED      = CLASS_DECLARATION
TEST_CASE_DECLARATION
SKIP_FUNCTION_MACROS   = NO


Any ideas on how to fix this warning? Is there anyway
to see the macro expansion that doxygen creates? Maybe
seeing the code could fix this.

__________________________________________________
Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards®
http://movies.yahoo.com/

Re: [Doxygen-users] Documenting file members....

[Johan E. <joh...@ua...>]

Dimitri van Heesch wrote:

> On Thu, Mar 21, 2002 at 10:31:19AM +0100, Johan Eriksson wrote:
> 
>>Hi,
>>    I thought it was necessary to explict document the file members 
>>using   a structural command even if the corresponding C++ entity is 
>>declared immediatelly after the documentation block. 
>>
> 
> No that is not true. _only_ if the documentation is not in front of
> either the declaration or the definition of a file member, there should
> be a structural command. What part of doxygen's documentation made you
> think this was always required? 


I am not sure, but somewhere along the line I got the feeling that this 
was necessary. I thought that I've tested this in some early release of 
version 1.2.x but now I don't know..........

Anyway,
        in the documentation chapter 2.3, the sentence: "Files can only 
be documented using the second option." I interpreted that as 'Files and 
its members can ...." maybe since the examples described in chapter 3.1 
and 3.2 also makes an division between documenting class members and 
file members.


 >> snip <<

.
Thanks for all the quick replies,
                                  Johan

Re: [Doxygen-users] Documenting file members....

[Dimitri v. H. <di...@st...>]

On Thu, Mar 21, 2002 at 10:31:19AM +0100, Johan Eriksson wrote:
> Hi,
>     I thought it was necessary to explict document the file members 
> using   a structural command even if the corresponding C++ entity is 
> declared immediatelly after the documentation block. 

No that is not true. _only_ if the documentation is not in front of
either the declaration or the definition of a file member, there should
be a structural command. What part of doxygen's documentation made you
think this was always required? 

> For example, in 
> header file foo.h:
> 
> /** \file
>    * Some desc of file foo.h.....
>    */
> 
> /** \enum AnEnum
>    * Some desc...
>    */
> enum AnEnum
> {
>     Value0,
>     Value1
> };
> 
> However, in version 1.2.14 this seems not to be necessary anymore. 

I don't remember this was required in any earlier version either...

> It is 
> just to do:
> 
> /** \file
>    * Some desc of file foo.h.....
>    */
> 
> /**
>    * Some desc...
>    */
> enum AnEnum
> {
>     Value0,
>     Value1
> };
> 
> Is this right or is it a bug??? Personally I like the latter better, 
> less to type and it is more consistent when documenting compound members.

Not a bug, but a feature ;)

Regards,
  Dimitri

Re: [Doxygen-users] package Java

[Dimitri v. H. <di...@st...>]

On Thu, Mar 21, 2002 at 09:18:53PM +0100, Benoit Cerrina wrote:
> Yes, this is a question I asked earlier and I did not get any answer.
> Benoit
> ----- Original Message -----
> From: "Elsa" <els...@if...>
> To: <dox...@li...>
> Sent: Thursday, March 21, 2002 5:30 PM
> Subject: [Doxygen-users] package Java
> 
> 
> Hi,
>  I'd like to know if it is possible to configure doxygen in order to
> have information about the current package in the class documentation?
> Thanks
> 
> Elsa

This is not possible because doxygen does not treat packages as 
`namespaces' like it should. This is serious limitation for Java code, 
which I hope to remove in a future release.

Regards,
  Dimitri

Re: [Doxygen-users] package Java

[Benoit C. <b.c...@wa...>]

Yes, this is a question I asked earlier and I did not get any answer.
Benoit
----- Original Message -----
From: "Elsa" <els...@if...>
To: <dox...@li...>
Sent: Thursday, March 21, 2002 5:30 PM
Subject: [Doxygen-users] package Java


Hi,
 I'd like to know if it is possible to configure doxygen in order to
have information about the current package in the class documentation?
Thanks

Elsa


____________________________________________________________________________
__
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif



_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] Another question about dot

[Elsa <els...@if...>]

Hi,
is there a way to change generated UML graphs? Indeed, there=
 is the same
notation for inheritance and implementation (entends and imp=
lements),
and this can be confused for the reader.
Thanks,
Elsa=20

=20
____________________________________________________________=
__________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur l=
e WAP...
http://www.ifrance.com/_reloc/email.emailif

[Doxygen-users] package Java

[Elsa <els...@if...>]

Hi,
 I'd like to know if it is possible to configure doxygen in =
order to
have information about the current package in the class docu=
mentation?
Thanks

Elsa

=20
____________________________________________________________=
__________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur l=
e WAP...
http://www.ifrance.com/_reloc/email.emailif

[Doxygen-users] RTF Questions

[Zvi M. <zv...@ga...>]

Hi all,

I have some questions regarding the RTF file generated by doxygen:

1. Is it possible that each parameters in the function prototype will
appear
    in different line (as it presented in the HTML) ? Seems that the
HTML
    use tables to implement that, however in RTF, all parameters are in
one
    long line.

2. RTF book title is not updated with the title given in the
configuration file
    (in the HTML it appears correctly) . Is this purposely or a bug?

3. Where I can find an example of RTF Style Sheet file ? can somebody
    point to an example?

4. How can I force fix font for paragraph text ? (This question also
apply
    to HTML format as well. I could not find a way to do it in the CSS
file

Many thanks for the great support of this mailing list!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Zvika Mizrahi
Galileo Technology Ltd - a Marvell Company
Tel : +972-4-9999555 ext. 1177
Fax : +972-4-9999334
zv...@ga...
www.marvell.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~