Commit db36de70 authored by dimitri's avatar dimitri
Browse files

Release-1.4.4-20050918

parent 3b98221d
Loading
Loading
Loading
Loading
+2 −2
Original line number Diff line number Diff line
DOXYGEN Version 1.4.4-20050817
DOXYGEN Version 1.4.4-20050918

Please read the installation section of the manual 
(http://www.doxygen.org/install.html) for instructions.

--------
Dimitri van Heesch (17 August 2005)
Dimitri van Heesch (18 September 2005)
+2 −2
Original line number Diff line number Diff line
DOXYGEN Version 1.4.4_20050817
DOXYGEN Version 1.4.4_20050918

Please read INSTALL for compilation instructions.

@@ -17,4 +17,4 @@ to subscribe to the lists or to visit the archives.

Enjoy,

Dimitri van Heesch (dimitri@stack.nl) (17 August 2005)
Dimitri van Heesch (dimitri@stack.nl) (18 September 2005)
+1 −1
Original line number Diff line number Diff line
1.4.4-20050817
1.4.4-20050918
+6 −4
Original line number Diff line number Diff line
@@ -276,20 +276,22 @@ Here is an example of the use of these comment blocks:

\section structuralcommands Documentation at other places

So far we have assumed that the documentation blocks are always located in 
front of the declaration or definition of a file, class or namespace or in
So far we have assumed that the documentation blocks are always located \e in 
\e front of the declaration or definition of a file, class or namespace or in
front or after one of its members. 
Although this is often comfortable, there may sometimes be reasons to put the 
documentation somewhere else. For documenting a file this is even 
required since there is no such thing as "in front of a file". 

Doxygen allows you to put your documentation blocks practically 
anywhere (the exception is inside the body of a function or inside a 
normal C style comment block). 

The price you pay for not putting the
documentation block before (or after) an item is the need to put a  
documentation block directly before (or after) an item is the need to put a  
structural command inside the documentation block, which leads to some
duplication of information.
duplication of information. So in practice you should \e avoid the use of
structural commands \e unless other requirements force you to do so.

Structural commands (like all other commands) start with a backslash 
(<tt>\\</tt>), or an at-sign (<tt>\@</tt>) if you prefer JavaDoc style, 
+1 −0
Original line number Diff line number Diff line
@@ -93,6 +93,7 @@ ClassDef::ClassDef(
  m_isAbstract = FALSE;
  m_isStatic = FALSE;
  m_isObjC = FALSE;
  m_isTemplArg = FALSE;
  m_membersMerged = FALSE;
  m_categoryOf = 0;
  QCString ns;
Loading