doxygen-users — List for users of doxygen

RE: [Doxygen-users] Resetting indent after \param etc.?

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

You probably use some specific output format
(like HTML, LaTeX, RTF, etc.).  Could you post more details?

Generally, the problem is that some visual attributes of 
the generated text are related to the meaning of the text.
The text rendering is related to the generated output, and
can be also related to the expected output media (like paper
or screen).  For example, there are some typographic
rules that LaTeX tries to follow (say) implicitly.  Indenting
rules may be the example.  Another example, <li> elements
of HTML lists are rendered in some way.  They are the parts
of some list.  To typeset one paragraph so as if it was not
the part of the list, or you have to break the list around the
paragraph to two lists, or you have to do some really weird
things (read it "not recommended").

While there are some attributes that can be set on the level
of the chosen output format, they may be very different for
each of the format.  For example, it may be better to 
produce \param descriptions as the table in HTML.  In LaTeX
generator, other constructs may be prefered.

As a rule of thumb, you should never try to adjust visual
appearance by doing some special things inside your sources.
In my opinion, doxygen should not even allow this.  All the 
formating information should be related only to the meaning
of the text while allowing possible style changes on the 
generator level (i.e. by adding some Doxyfile configuration
options), or by changing the style of rendering of the generated
output later by (e.g.) modifying doxygen.css for the HTML
output, by adding some special style package or commands to
the LaTeX output, etc.

So, your request should be reformulated from the "formating
style" point of view.  

With regards, 
  Petr
-- 
Petr Prikryl, SKIL, spol. s r.o., pri...@sk...

> -----Original Message-----
> From:	Christopher Brewster [SMTP:bre...@ya...]
> Sent:	Friday, October 05, 2001 4:31 PM
> To:	dox...@li...
> Subject:	[Doxygen-users] Resetting indent after \param etc.?
> 
> I often need to put normal (unindented) \par text
> after indented paragraphs such as \param and \li. I
> finally noticed that those \par's are indented. (Sure
> enough, that's what the manual says it does!) The only
> way I've found to resume the unindented \par's is to
> have a "heading" consisting of "." only, on the first
> unindented \par following a \param. The dot is pretty
> unnoticeable but still a kluge. Is there a better way
> to reset the indent?
> 
> Christopher Brewster
> 
> __________________________________________________
> Do You Yahoo!?
> NEW from Yahoo! GeoCities - quick and easy web site hosting, just
> $8.95/month.
> http://geocities.yahoo.com/ps/info1
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] Behaviors of `gcc -E -C'

[Roberto B. <ba...@cs...>]

Hi there,

here is a problem I have encountered that may be of interest to both
the GCC and the DOXYGEN communities.
Consider the following 4 non-empty lines of C text:

#if 0
/* I would like not to see this. */
int x;
#endif

Put these 4 lines into a file called foo.c and then
try

    gcc -E -P -C foo.c

Here is the behavior I observe with different (official and unofficial)
versions of gcc:

egcs-2.91.66 (kgcc)  produces a blank line
egcs-2.95.3          produces a blank line
gcc 2.96-85 (RedHat) produces the comment I would like not to see
gcc 3.0.1            produces the comment I would like not to see
gcc 3.1 20011006     prints nothing (GOOD!)

This issue is quite relevant if one uses doxygen
(http://www.doxygen.org/), since there comments are relevant (whence
the use of `-C').  A situation where the behavior of gcc 2.96-85 and
gcc 3.0.1 may byte you is the following:

#if 0
/*! A comment referring to x. */
int x;
#endif
int y;

Doxygen uses special comments like the above (notice the exclamation
mark) for documentation.  When using doxygen is fed with text coming
from the GCC preprocessor, gcc 2.96-85 (RedHat) and gcc 3.0.1
cause a comment for (disregarded) x to be applied to y.
There are other tools that look inside comments to derive useful
information: these are also affected as well.

I wrote this message because I believe it is important not to
overlook the issue.  I have quickly checked the standard documents,
but I have not found anything that prescribes the behavior
that I consider "desirable".  I have also checked the documentation
of the `-C' option but this is also somewhat ambiguous on the subject.

A last question: even though the CVS HEAD version is OK
(for my purposes, at least), what will gcc 3.0.2 do?
All the best,

    Roberto

-- 
Roberto Bagnara
Computer Science Group
Department of Mathematics, University of Parma, Italy
http://www.cs.unipr.it/~bagnara/
mailto:ba...@cs...

[Doxygen-users] Doxygen-1.2.11.1 in CVS

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

Hi,

Here are the changes since last update:
--------------------------------------------------------------------
+ BUG: Links to members in undocumented groups were broken.
+ BUG: Deep class hierarchies caused "nested too deep" error in LaTeX output.
+ BUG: Providing one documentation block for grouped, related members did
       not work.
+ BUG: Documentation pages for documented classes nested inside
       undocumented classes or namespaces were not generated.
--------------------------------------------------------------------
Enjoy,
  Dimitri

Re: [Doxygen-users] Bug with enclosed classes and Alphabetical List?

[Luis I. <ib...@ch...>]

Hi,

We are experiencing the same problem with the alphabetical list.

As far as we have seen, the whole index is in the correct order,
but "extra" incorrect header are added when dealing with internal
classes.

For example:

   class Cell {
       class Mitochondria {
       };
    };

Produce a correct entry "Cell" in the "C" group.
Produce a correct entry "Cell::Mitochondria" in the "M" group,
but for this last one, an extra "C" header is introduced.

That make the list look like: M, C, N...

Classes in the  index are correctly ordered, but the extra
header produce the wrong impression.



Examples can be seen in VTK and ITK documentation sites:

1) http://public.kitware.com/VTK/doc/nightly/html/classes.html

   See for example:     vtkFieldData::BasicIterator

   It is correctly ordered under "B" but has an extra "F"
   header.


2) http://public.kitware.com/Insight/Doxygen/html/classes.html

   See for example:     VectorContainer::ConstIterator

   It is correctly ordered under "C" but has an extra "V"
   header.




Is there any way to get around this ?


Thanks



Luis

-- 
Luis Ibanez                                      CB#:   7060
Research Assistan Professor                      phone: (919) 843 5436
Division of Neurosurgery                         fax:   (919) 966 6627
University of North Carolina at Chapel Hill      email: ib...@cs...
Chapel Hill, NC 27599-7060                       http://www.cs.unc.edu/~ibanez

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


On Sat, 29 Sep 2001, Pablo Alvarado wrote:

> Hello everybody,
>
> I have a problem sorting the classes in the "Alphabetical List".
>
> I get the labels of A, B, A, B, A, B, A, where I expected something like
> A, B, P.
> A short example is included as attachment.  In our proyect with about
> two hundred classes this "interesting" sorting is very confusing...  Am
> I missing something in the configuration file or is this a bug?
>
> Regards,
>
> Pablo
>
>

[Doxygen-users] Labels for friend relation swapped in gviz diagrams?

[Dan M. <dm...@Cr...>]

doxygen 1.2.11, GraphVis 1.7.6 beta 1, Win2k Pro

I have at least one class collaboration diagram with an arrow labelled
"CTable" (one of my classes) and the target box labelled "friend". These two
labels appear to be swapped! CTable is in fact a friend of the class at the
beginning of the arrow. Anyone else seen something like this?

[Doxygen-users] Grouping file members

[Dan M. <dm...@Cr...>]

I'm having trouble getting grouping to work the way I'd expect for some
non-member operators defined in a namespace. Following is a test case with
the same problematic elements as my code. I've actually run this test
through doxygen and replicated the problem. I'm using doxygen 1.2.11 on
Win2k Pro.

/**
 * @file test.h
 * This is the file.
 */

/**
 * Foo is a namespace.
 */
namespace Foo {
  class TR;
  /**
   * Docs for Rel
   */
  class Rel { /*...*/ };

  //@{
  /**
   * Yadda yadda yadda.
   * @param r This is a Rel
   * @param t This is a TR.
   * @return Returns a result of type Rel.
   * @relates Rel
   */
  Rel operator&&(const Rel& r, const TR& t);
  Rel operator&&(const TR& t, const Rel& r);
  //@}

}

Because of my build setup, the configuration is built in pieces. I've
attached all the parts (test.cfg is the file actually given to doxygen on
the command line). The parts of my config which I think might be relevant
are:

EXTRACT_ALL     = NO
HIDE_UNDOC_CLASSES = YES
HIDE_UNDOC_MEMBERS = YES
DISTRIBUTE_GROUP_DOC = YES

My situation seems to correspond to the last part of the last example in the
"Grouping" section of the doxygen manual. But the behavior doesn't seem to
match what's described there. I tried changing the operators to regular
functions, but that doesn't help.

I'd really like a single documentation block in the HTML output that applies
to both variations of the operator&&, since they do the same thing, but
showing both prototypes so the reader can see the symmetry that's provided.
I'd settle for each prototype listed separately with the documentation
replicated. But the second operator prototype seems to be ignored by
doxygen. If I omit @relates, then i get the latter behavior (two entries
with replicated docs), but on the namespace page. 

Any suggestions? Is @relates just incompatible with grouping? Is there any
way to get the kind of grouping I'd actually like, i.e. multiple function
prototypes documented together?


 <<all.doxy>>  <<CsiDb.doxy>>  <<test.cfg>> 

[Doxygen-users] New doxygen-like PL/SQL hypermap generator

[Phillips, J. <Jam...@El...>]

All,

     At http://sourceforge.net/projects/hypersql/ I have
a new doxygen-like PL/SQL hypermap generator.  From
the sourceforge project page:

HyperSQL is like a doxygen for SQL, hypermapping SQL views,
packages, procedures, and functions to HTML source code 
listings and showing all code locations where these are used.
The internal "where used" functionality also scans C++ and 
Java source files.

Source code is at:
http://prdownloads.sourceforge.net/hypersql/HyperSQL.py

     Randy Phillips



******************************************************************
This email and any files transmitted with it from the ElPaso 
Corporation 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 the 
sender.
******************************************************************

[Doxygen-users] Resetting indent after \param etc.?

[Christopher B. <bre...@ya...>]

I often need to put normal (unindented) \par text
after indented paragraphs such as \param and \li. I
finally noticed that those \par's are indented. (Sure
enough, that's what the manual says it does!) The only
way I've found to resume the unindented \par's is to
have a "heading" consisting of "." only, on the first
unindented \par following a \param. The dot is pretty
unnoticeable but still a kluge. Is there a better way
to reset the indent?

Christopher Brewster

__________________________________________________
Do You Yahoo!?
NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

Re: [Doxygen-users] Doxygen-1.2.11-20011003 in CVS

[Luigi B. <bal...@ma...>]

At 10:06 PM 10/3/01 +0200, Dimitri van Heesch wrote:
>Since there were some bugs in the latest release, I have committed some
>fixed to CVS. Please test this version if you can, so I can release a new
>binary over the weekend that is actually tested ;-)

Here's the usual test case. A strange behavior will be triggered by running 
through Doxygen a fresh doxyfile with INPUT = test.cpp

Bye,
         Luigi

[Doxygen-users] Tcl too?

[<pgp...@te...>]

Hi everybody,

I'm newbbie in use doxygen. I'm creating a project in Vtk and I'd like to
know if I could use it to generate my on-line documentation from a tcl
sources.

Thank you in advance,

*******************************
Pedro García Patrón
e-mail: pgp...@te...
tlfno: +34 985 16 03 83

E.U.I.T.I. Gijón
Universidad de Oviedo - Spain
*******************************

Re: [Doxygen-users] first question

[Rodrigo A. R. C. <rca...@ev...>]

Txs!  

The error when executing 'installdox' stopped.
However, I could not find any link in the html pages of 'thread' project to hml pages of 'thread_test' project.
Also interesting, I run the 'tag' and 'example' projects that came with doxygen documentation, and there were clear references in 'tag' html pages to 'example' pages, and I did not run 'installdox'.
I am trying to read again the doxygen manual, but I can not see what I am doing wrong....

txs again for your help!

---------- Original Message ----------------------------------
From: John Sturton <joh...@se...>
Date: Thu, 04 Oct 2001 08:05:19 +0200

>Try specifying PERL_PATH in both config files.
>
>Cheers,
>
>John
>

--
Rodrigo Canellas
www.EverSystems.com.br
--

[Doxygen-users] first question

[Rodrigo A. R. C. <rca...@ev...>]

Hi!

First question in this list!

I am just starting to use doxygen and it is really great!

However, I am trying to create an external reference between 2 projects, but I am not making it.

Here are the configuration files:

thread.doxy:

#---------------------------------------------------------------------------
# Configuration::addtions related to external references   
#---------------------------------------------------------------------------
TAGFILES               = $(WEB_PAGES_DIR)/thread/html/example/teste_thread.tag=../html/examples
GENERATE_TAGFILE       = $(WEB_PAGES_DIR)/thread/thread.tag
ALLEXTERNALS           = YES
PERL_PATH              = 

thread_test.doxy:

#---------------------------------------------------------------------------
# Configuration::addtions related to external references   
#---------------------------------------------------------------------------
TAGFILES               = 
GENERATE_TAGFILE       = $(WEB_PAGES_DIR)/thread/html/examples/thread_test.tag
ALLEXTERNALS           = NO
PERL_PATH              = /usr/bin/perl

Here is the directory structure:

$(WEB_PAGES_DIR)
	/thread
		thread.tag
		/html
		/examples
			thread_test.tag
			html

The installdox program reports this error:
./installdox: line 3: syntax error near unexpected token `('
./installdox: line 3: `%subst = ( "teste_thread.tag", "");'

And here it is:


#!

%subst = ( "teste_thread.tag", "");
$quiet   = 0;

if (open(F,"search.cfg"))
{
  $_=<F> ; s/[ \t\n]*$//g ; $subst{"_doc"} = $_;
  $_=<F> ; s/[ \t\n]*$//g ; $subst{"_cgi"} = $_;
}

while ( @ARGV ) {
  $_ = shift @ARGV;
  if ( s/^-// ) {
    if ( /^l(.*)/ ) {
      $v = ($1 eq "") ? shift @ARGV : $1;
      ($v =~ /\/$/) || ($v .= "/");
      $_ = $v;
      if ( /(.+)\@(.+)/ ) {
        if ( exists $subst{$1} ) {
          $subst{$1} = $2;
        } else {
          print STDERR "Unknown tag file $1 given with option -l\n";
          &usage();
        }
      } else {
        print STDERR "Argument $_ is invalid for option -l\n";
        &usage();
      }
    }
    elsif ( /^q/ ) {
      $quiet = 1;
    }
    elsif ( /^\?|^h/ ) {
      &usage();
    }
    else {
      print STDERR "Illegal option -$_\n";
      &usage();
    }
  }
  else {
    push (@files, $_ );
  }
}

foreach $sub (keys %subst)
{
  if ( $subst{$sub} eq "" ) 
  {
    print STDERR "No substitute given for tag file `$sub'\n";
    &usage();
  }
  elsif ( ! $quiet && $sub ne "_doc" && $sub ne "_cgi" )
  {
    print "Substituting $subst{$sub} for each occurence of tag file $sub\n"; 
  }
}

if ( ! @files ) {
  if (opendir(D,".")) {
    foreach $file ( readdir(D) ) {
      $match = ".html";
      next if ( $file =~ /^\.\.?$/ );
      ($file =~ /$match/) && (push @files, $file);
      ($file =~ "tree.js") && (push @files, $file);
    }
    closedir(D);
  }
}

if ( ! @files ) {
  print STDERR "Warning: No input files given and non found!\n";
}

foreach $f (@files)
{
  if ( ! $quiet ) {
    print "Editing: $f...\n";
  }
  $oldf = $f;
  $f   .= ".bak";
  unless (rename $oldf,$f) {
    print STDERR "Error: cannot rename file $oldf\n";
    exit 1;
  }
  if (open(F,"<$f")) {
    unless (open(G,">$oldf")) {
      print STDERR "Error: opening file $oldf for writing\n";
      exit 1;
    }
    if ($oldf ne "tree.js") {
      while (<F>) {
        s/doxygen\=\"([^ \"\:\t\>\<]*)\:([^ \"\t\>\<]*)\" (href|src)=\"\2/doxygen\=\"$1:$subst{$1}\" \3=\"$subst{$1}/g;
        print G "$_";
      }
    }
    else {
      while (<F>) {
        s/\"([^ \"\:\t\>\<]*)\:([^ \"\t\>\<]*)\", \"\2/\"$1:$subst{$1}\" ,\"$subst{$1}/g;
        print G "$_";
      }
    }
  } 
  else {
    print STDERR "Warning file $f does not exist\n";
  }
  unlink $f;
}

sub usage {
  print STDERR "Usage: installdox [options] [html-file [html-file ...]]\n";
  print STDERR "Options:\n";
  print STDERR "     -l tagfile\@linkName   tag file + URL or directory \n";
  print STDERR "     -q                    Quiet mode\n\n";
  exit 1;
}




I hope someone can help me!


TIA,
  Rodrigo Canellas


--
Rodrigo Canellas
www.EverSystems.com.br
--

[Doxygen-users] Doxygen-1.2.11-20011003 in CVS

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

Hi, 

Since there were some bugs in the latest release, I have committed some
fixed to CVS. Please test this version if you can, so I can release a new
binary over the weekend that is actually tested ;-)
-----------------------------------------------------------------------------
+ BUG: Fixes RTF output bugs.
+ BUG: When preprocessing was disabled, the input was truncated for sources
       containing CR's (i.e. sources edited on Windows).
+ BUG: Syntax highlighting C-style comments was broken.
+ ADD: Included update for Slovak translation (thanks to Stanislav Kudlac)
-----------------------------------------------------------------------------
Enjoy,
  Dimitri

P.S. tarballs of this release can be found at 
http://www-kp3.gsi.de/~kp3softd/doxygen/ in a about 7 hours from now.

[Doxygen-users] C++ include files problem?

[Simon A W. <sim...@ma...>]

I am in the process of adding doxygen docs to the make system for a 
moderate sized project (C/C++).

I was expecting that by setting:
    ENABLE_PREPROCESSING = YES
    SEARCH_INCLUDES = YES
    INCLUDE_PATH = TOP1/include TOP2/include  
    INCLUDE_FILE_PATTERNS = *.h

...then the header files containing the C++ class definitions would be 
incorporated, and their documentation included.  But all I get is the 
.cc source files, and no class structures.

Can I get the stuff in the header files brought into the doc?


Note that in this case the class headers are in subdirs off 
"TOP2/include", eg "TOP2/include/proj1" and "TOP2/include/proj2".  They 
are included as "#include "proj1/thing.h" etc.

When I add the include subdirs to the INPUT list, I get the desired 
documentation (all the class structures and inheritance, all the member 
function definitions etc).

Why is this undesirable?  Because the author of the Makefile will have 
to know all the include dependancies of the source being documented.  I 
already automate this for compilation (using g++ -MM).  We really dont 
want to blindly INPUT all the super-projects include files, since we are 
only documenting a sub-project at a time.

I suppose I could do something to manipulate the existing dependancy 
lists (from g++ -MM), to accumulate a list of all quoted header 
dependancies on the source in the sub-project directories...  Messy.

I am using Doxygen 1.2.1 which came with RH7.0.  If I have to rely on an 
u/grade, then all machines intending to use our make system would have 
to u/g as well (ie, at least a compatible RPM).


Si.

-- 
Simon A Watts
Software Engineer
Marconi Medical Systems
mailto:sim...@ma...
tel: +44(0) 1252 747 311

Re: [Doxygen-users] Testing RTF

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

On Tue, Oct 02, 2001 at 03:32:17PM -0400, Martin Vuille wrote:
> I would be willing to help with the RTF side of
> things.

Great!

> I am in the process of documenting three projects,
> for external documentation only (i.e., only header
> files, only public members.)
> 
> I don't think this will be a very comprehensive
> test but since, as it stands, I can't make it work
> in .10 or .11 (in .11 I have problems with too-deep
> nesting) the testing would have some value.
> 
> What tools would I need to build doxygen under
> Windows? My environment is NT + VC++ 6.0.

See the "Compiling from source on Windows" section of
the manual (an online version can be found here:
http://www.stack.nl/~dimitri/doxygen/install.html#install)

Regards,
  Dimitri

[Doxygen-users] Missing HTML table data vertical align

[Christian W. <chr...@ho...>]

In the HTML output for "Member Function Documentation": If 
a method takes just one parameter and also is 
declared "pure virtual", "const" etc (additional text is 
places to the right of the member function), the parameter 
is vertically aligned wrong (is it defaulted to center?). 
It can be seen if the browser window is made smaller.

The output is correct for a method that takes more than one 
parameter (the html table is done differently there).


Using: doxygen 1.2.11, MS Windows


Here is an example class showing this:

/**
 * My Test class
 */
class Test
{
public:
    /**
     * Override this function
     */
    virtual void myFunction(const std::string& myParameter) 
const = 0;

    /**
     * Override this function
     */
    virtual void myFunction(const std::string& myParameter, 
const std::string& refId) const = 0;
};

Re: [Doxygen-users] Comment style bug

[James R. <ja...@sh...>]

Dimitri van Heesch wrote:
> 
> On Tue, Oct 02, 2001 at 01:40:12PM -0400, James Roth wrote:
> > Hello,
> >
> >       I just noticed a problem with multi-line C style comments.
> >
> >       <font class="comment">/******************</font>
> >        * Test comment   *
> >        ******************/
> >
> >       It appears that only the first line has the style class applied.
> 
> Please send a more complete bug report!
> 

Ok.

This happens with doxygen-1.2.11 and recent CVS versions.

--== INPUT foo.c as an @example file ==--
 
/*
 * Hello world
 */

--== OUTPUT foo_8c-example.html ==--

<!-- header -->
<!-- Generated by Doxygen 1.2.11 -->
<h1>foo.c</h1>
<p>
<div class="fragment"><pre>
<font class="comment">/*</font>
 * Hello world
 */
</pre></div><!-- footer -->

--
As you can see, the <font> tag is closed prematurely.  This results in
broken syntax coloring.

Thanks, 
James Roth <ja...@sh...>
Shugyo Design Technologies

[Doxygen-users] Testing RTF

[Martin V. <ma...@no...>]

I would be willing to help with the RTF side of
things.

I am in the process of documenting three projects,
for external documentation only (i.e., only header
files, only public members.)

I don't think this will be a very comprehensive
test but since, as it stands, I can't make it work
in .10 or .11 (in .11 I have problems with too-deep
nesting) the testing would have some value.

What tools would I need to build doxygen under
Windows? My environment is NT + VC++ 6.0.

MV

Re: [Doxygen-users] Comment style bug

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

On Tue, Oct 02, 2001 at 01:40:12PM -0400, James Roth wrote:
> Hello,
> 
> 	I just noticed a problem with multi-line C style comments.
> 
> 	<font class="comment">/******************</font>
> 	 * Test comment   *
> 	 ******************/
> 
> 	It appears that only the first line has the style class applied.

Please send a more complete bug report!

In general, bug reports like the above are useless, if they do not include
an example that allows me to reproduce the bug, along with the version
of doxygen and the platform used.

Regards,
  Dimitri

Re: [Doxygen-users] HTML lists failing (<OL>)

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

On Tue, Oct 02, 2001 at 09:51:32AM -0700, Christopher Brewster wrote:
> I added a simple ordered list to my help, but only the
> first item is numbered. The rest of the table is
> left-indented and unnumbered, and the </OL> prints in
> the output. So something is making the list stop at
> the end of the first item. Any suggesions? Here's a
> slightly shortened reproduction:
> 
>  * <OL>
>  * <LI>  A logical_watchpoint with both read and write
> access was registered.
>  *
>  * <LI>  A logical_watchpoint with read access.
>  *
>  * <LI>  A logical_watchpoint with write access.
>  *
>  * </OL>

The above works for me. So, please provide a more detailed bug report!

Regards,
  Dimitri

[Doxygen-users] RTF tester/developer/maintainer needed. was: Problems with RTF

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

On Tue, Oct 02, 2001 at 01:42:23PM -0400, Martin Vuille wrote:
> Hello,
> 
> I'm trying to use Doxygen 1.2.10 to generate documentation
> in RTF format and running into a couple of issues.
> 
> I'm hoping that these are due to something I've done or
> failed to do rather than bugs.

I'm afraid they are caused by bugs. Doxygen 1.2.10 had RTF bugs,
so has 1.2.11 (only different bugs this time).

The problem is that I do not test RTF enough, because I do not use Windows
if unless I have to. 

To resolve this problem, someone has to help me test and maintain
the RTF generator. In the past Parker Waechter and Alexander Bartolich
(and some others) have contibuted code from time to time (thanks guys), 
but apparantly no one tries and tests new releases when they appear in CVS
on a regular basis. 

If you want to help me to test and improve the RTF output please let me 
know. It would be the easiest if you can compile doxygen on Windows yourself, 
and have a reasonbly sized and documented project that you can test the output
with.

If nobody is interested I might be forced to drop RTF support 
altogether in the future!

Regards,
  Dimitri

Re: [Doxygen-users] Buffer Overflow

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

On Tue, Oct 02, 2001 at 06:15:26AM +0800, Stephen Morrison wrote:
> I would say it would be from an autogenerated file, there are 100s of them
> in the source tree.  Is there a config option or something I can do as a
> work around?  Alternatively for the future, is it possible for Doxygen to
> just ignore errors of these type and keep processing rather than throwing a
> fatal?

It is generated code (from flex) that produces this fatal error, so it is
difficult to fix. I suggest to either remove these autogenerated files from the
input (there is no point to include them anyway, is there?) or send me
problematic files so I can fix the scanner.

Regards,
  Dimitri

[Doxygen-users] Problems with RTF

[Martin V. <ma...@no...>]

Hello,

I'm trying to use Doxygen 1.2.10 to generate documentation
in RTF format and running into a couple of issues.

I'm hoping that these are due to something I've done or
failed to do rather than bugs.

First problem is that, during processing, doxygen generates
two instances of the diagnostic "Warning: Negative indent
level while generating RTF output!". Unfortunately, no
indication is provided as to where or why this happens.
Does anyone know what might bring this about?

The second problem is that the RTF file seems to be complete
(if I open the RTF file as a text file, I can see that all the
information is there) but, when opened in Word 2000, it is
truncated after the description of the constructors and
destructors of the very first class. Perhaps this is related
to the above?

Finally, in the TOC, the places that should contain page
numbers have the string "pagenum" instead.

Help!
MV

[Doxygen-users] Comment style bug

[James R. <ja...@sh...>]

Hello,

	I just noticed a problem with multi-line C style comments.

	<font class="comment">/******************</font>
	 * Test comment   *
	 ******************/

	It appears that only the first line has the style class applied.

Thanks, 
James Roth <ja...@sh...>
Shugyo Design Technologies

[Doxygen-users] HTML lists failing (<OL>)

[Christopher B. <bre...@ya...>]

I added a simple ordered list to my help, but only the
first item is numbered. The rest of the table is
left-indented and unnumbered, and the </OL> prints in
the output. So something is making the list stop at
the end of the first item. Any suggesions? Here's a
slightly shortened reproduction:

 * <OL>
 * <LI>  A logical_watchpoint with both read and write
access was registered.
 *
 * <LI>  A logical_watchpoint with read access.
 *
 * <LI>  A logical_watchpoint with write access.
 *
 * </OL>






__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com