doxygen-users — List for users of doxygen

[Doxygen-users] directory dependence graphs too spaced out / balloon-like?

[Anthony F. <ant...@gm...>]

Hi!

I've been very happy with Doxygen over the last few years -- thanks for the
great tool!

I'm asking for advice on how to improve the rendered directory dependence
graphs.

Some of my more complex directory dependence graphs are rendered by
graphviz / dot with much more spacing than needed.  Does anyone know any
tweaks that can reduce this?

Here are some files that demonstrate the symptoms:

http://foiani.com/tony/cpp/main.dot -- sample .dot file
http://foiani.com/tony/cpp/main_dot.txt -- same file, but as .txt for easy
viewing
http://foiani.com/tony/cpp/main.svg -- output

Note that the left side is way more spaced out than it needs to be.  The
right side is a bit harder to fix.

Thanks for any suggestions you can offer.

Doxygen 1.8.3.1
GraphViz 2.30.1
Fedora 19 x86-64

[Doxygen-users] C#: How to disable at(@), backslash(\) and hash sign(#) inside XML doc comments?

[David P. <qwe...@gm...>]

I would like Doxygen to not pay attention to #, \ and @ directives inside
XML doc comments (since XML comments have their own directives.) For
instance I have a class that talks about the meaning of @ and # in a
programming language I am making:

/// So #class is a keyword that is parsed like an identifier, but this is
/// different from the notation @class which already exists in plain C#.
/// @class is an ordinary identifier that has a "@" sign in front to ensure
/// that the compiler does not treat it like a keyword at all. #class is a
/// special identifier that is parsed like an identifier but then treated
like
/// a keyword after parsing is complete.

.../LNode.cs(210): warning: the name `already' supplied as the argument of
the \class, \struct, \union, or \include command is not an input file
.../LNode.cs(211): warning: the name `an' supplied as the argument of the
\class, \struct, \union, or \include command is not an input file
...

I am not sure if this is caused by @ or \ or #, but for some reason Doxygen
deletes the entire detailed description (very detailed - several pages) of
this class, i.e. the output does not have a detailed description section.

I do not want to add doxygen-specific escape sequences because anyone
reading the source code will not know what they mean, nor will Visual
Studio strip them out of the XML files it generates.

Also, does Doxygen understand that in C#, Foo<T> and Foo are two different
classes?

.../DList.cs(363): warning: Detected potential recursive class relation
between class Loyc::Collections::DList and base class
Loyc::Collections::DList< object >!

P.S. in a different file, doxygen is unable to parse this code block,
saying there is an EOF in the code block:

/// <code>
///     la0 = LA(0);
///     if (la0 == 'a' || la0 == 'b') { /* alt 1 or alt 2 */ }
/// </code>

I have to change */ to something else.

-- 
- David
http://loyc.net

[Doxygen-users] Keep comment format from source code

[Fabian N. <fab...@sc...>]

Hi everyone,

is it possible to tell Doxygen to format the descriptions in the html 
document jus the way the comment blocks are formatted in the source 
code? I.e. spaces, tabs, new lines etc...

That would make it heaps easier to use it with an already documented 
code, because you'd only have to add the '!>' instead of '!'.
Otherwise I'd have to touch all the listings and stuff I already have in 
the code.

Regards,
Fabian

Re: [Doxygen-users] documentation support for UVM code

[Ferro, A. <Ala...@me...>]

Vijaya,

There are also some extras for Doxygen that will allow the use of SystemVerilog. These, and a few other options are listed on this post - http://forums.accellera.org/topic/524-how-is-uvm-base-class-documented/

>From a documentation point of view, OVM vs. UVM makes little difference - it is all class based SystemVerilog.

BTW, I have no experience of using any of the tools linked above, but I hope they are of use to you!

Alasdair

-----Original Message-----
From: vijaya kirti [mailto:vij...@re...] 
Sent: 03 July 2014 07:31
Cc: dox...@li...
Subject: Re: [Doxygen-users] documentation support for UVM code

Alasdair,
      Thanks for information. In link, reference is made to OVM. But I 
will check this and get back.
I am looking for a something which can give pdf or doc as output.

Regards
Vijaya


On 07/02/2014 08:32 PM, Ferro, Alasdair wrote:
> Vijaya,
>
> The official UVM documentation is generated using a version of Natural Docs, available on the Verification Academy - https://verificationacademy.com/forums/downloads/naturaldocs-html-documentation-generator
>
> Would this suit your needs?
>
> AFAIK Doxygen does not (directly) support SystemVerilog code (c.f. http://www.stack.nl/~dimitri/doxygen/manual/features.html for the list of supported languages).
>
> Alasdair
>
> -----Original Message-----
> From: vijaya kirti [mailto:vij...@re...]
> Sent: 02 July 2014 14:34
> To: dox...@li...
> Subject: [Doxygen-users] documentation support for UVM code
>
> Hi,
>      I would like to know doxygen has support for UVM code.
>
> Regards
> Vijaya
>
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>


------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Preprocessing + different subroutine headers (FORTRAN)

[Fabian N. <fab...@sc...>]

Hi Albrecht,

 > Normal convention in the Fortran world is that lowercase extension is
 > not preprocessed and uppercase extension is preprocessed. So I don't
 > think it would be wise to do this.

Yeah, true point. However, it works for our current situation. We are 
about to rearrange a couple of things anyway, so we'll see.

Thanks,
Fabian


* From: Albert (alb...@gm...)
* To: Fabian Nick (fab...@sc...)
* Sent:  02.07.2014 at 15:46 +0200
* Subject: Re: [Doxygen-users] Preprocessing + different subroutine 
headers (FORTRAN)
> Fabian,
>
> F90 is already supported, as extension and will automatically do the
> preprocessing. The preprocessing of Fortran file is governed by the routine:
> bool FortranLanguageScanner::needsPreprocessing(const QCString &extension)
> {
>    return extension!=extension.lower(); // use preprocessor only for
> upper case extensions
> }
> in fortranscanner.l
>
> Your question regarding to do always preprocessing :
> Normal convention in the Fortran world is that lowercase extension is
> not preprocessed and uppercase extension is preprocessed. So I don't
> think it would be wise to do this.
>
> Albert
>
>
>
> On Wed, Jul 2, 2014 at 3:35 PM, Fabian Nick
> <fab...@sc... <mailto:fab...@sc...>>
> wrote:
>
>     Albert,
>
>     forget my last message.
>
>     However it would be nice if I could build a version where *.f90 is
>     preprocessed as well... Any chance to do so?!
>
>
>     Fabian
>
>
>     * From: Albert (alb...@gm... <mailto:alb...@gm...>)
>     * To: Fabian Nick (fab...@sc...aunhofer.__de
>     <mailto:fab...@sc...>)
>     * Sent:  02.07.2014 at 15:01 +0200
>     * Subject: Re: [Doxygen-users] Preprocessing + different subroutine
>     headers (FORTRAN)
>
>         Hi Fabian,
>
>
>         I see you use the extension f90, to enable preprocessing for
>         Fortran you
>         have to use F90 as extension.
>
>         Albert
>
>
>         On Wed, Jul 2, 2014 at 2:36 PM, Fabian Nick
>         <fab...@sc...aunhofer.__de
>         <mailto:fab...@sc...>
>         <mailto:fabian.nick@scai.__fraunhofer.de
>         <mailto:fab...@sc...>>>
>
>         wrote:
>
>              Hi all,
>
>              I'm using doxygen 1.8.7 and I set ENABLE_PREPROCESSING = yes.
>              However, when I parse a file with the following content
>
>              #ifndef FOO
>                     subroutine bar(arg1, arg2)
>              #else
>                     subroutine bar(arg1)
>              #endif
>                     end subroutine bar
>
>              I get a state 4 error:
>              Error in file ...doxybug.f90 line: 7, state: 4
>
>              I see why doxygen might be struggling here; is there any
>         way to work
>              aroung this? The meaning of the source code cannot be
>         changed though...
>
>              By the way: bar(arg1, arg2) in the else-section doesn't
>         work either.
>
>
>              Cheers,
>              Fabian
>
>
>         ------------------------------__------------------------------__------------------
>              Open source business process management suite built on Java
>         and Eclipse
>              Turn processes into business applications with Bonita BPM
>         Community
>              Edition
>              Quickly connect people, data, and systems into organized
>         workflows
>              Winner of BOSSIE, CODIE, OW2 and Gartner awards
>         http://p.sf.net/sfu/Bonitasoft
>              _________________________________________________
>              Doxygen-users mailing list
>         Doxygen-users@lists.__sourceforge.net
>         <mailto:Dox...@li...>
>              <mailto:Doxygen-users@lists.__sourceforge.net
>         <mailto:Dox...@li...>>
>         https://lists.sourceforge.net/__lists/listinfo/doxygen-users
>         <https://lists.sourceforge.net/lists/listinfo/doxygen-users>
>
>
>

Re: [Doxygen-users] documentation support for UVM code

[vijaya k. <vij...@re...>]

Alasdair,
      Thanks for information. In link, reference is made to OVM. But I 
will check this and get back.
I am looking for a something which can give pdf or doc as output.

Regards
Vijaya


On 07/02/2014 08:32 PM, Ferro, Alasdair wrote:
> Vijaya,
>
> The official UVM documentation is generated using a version of Natural Docs, available on the Verification Academy - https://verificationacademy.com/forums/downloads/naturaldocs-html-documentation-generator
>
> Would this suit your needs?
>
> AFAIK Doxygen does not (directly) support SystemVerilog code (c.f. http://www.stack.nl/~dimitri/doxygen/manual/features.html for the list of supported languages).
>
> Alasdair
>
> -----Original Message-----
> From: vijaya kirti [mailto:vij...@re...]
> Sent: 02 July 2014 14:34
> To: dox...@li...
> Subject: [Doxygen-users] documentation support for UVM code
>
> Hi,
>      I would like to know doxygen has support for UVM code.
>
> Regards
> Vijaya
>
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>

Re: [Doxygen-users] documentation support for UVM code

[Ferro, A. <Ala...@me...>]

Vijaya,

The official UVM documentation is generated using a version of Natural Docs, available on the Verification Academy - https://verificationacademy.com/forums/downloads/naturaldocs-html-documentation-generator

Would this suit your needs?

AFAIK Doxygen does not (directly) support SystemVerilog code (c.f. http://www.stack.nl/~dimitri/doxygen/manual/features.html for the list of supported languages).

Alasdair

-----Original Message-----
From: vijaya kirti [mailto:vij...@re...] 
Sent: 02 July 2014 14:34
To: dox...@li...
Subject: [Doxygen-users] documentation support for UVM code

Hi,
    I would like to know doxygen has support for UVM code.

Regards
Vijaya



------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Preprocessing + different subroutine headers (FORTRAN)

[Fabian N. <fab...@sc...>]

  Albert,

would it be sufficient to change filePatternList.append("*.F90"); in 
config.cpp and rebuild doxygen from source to work around this?

Thanks,
Fabian


* From: Albert (alb...@gm...)
* To: Fabian Nick (fab...@sc...)
* Sent:  02.07.2014 at 15:01 +0200
* Subject: Re: [Doxygen-users] Preprocessing + different subroutine 
headers (FORTRAN)
> Hi Fabian,
>
> I see you use the extension f90, to enable preprocessing for Fortran you
> have to use F90 as extension.
>
> Albert
>
>
> On Wed, Jul 2, 2014 at 2:36 PM, Fabian Nick
> <fab...@sc... <mailto:fab...@sc...>>
> wrote:
>
>     Hi all,
>
>     I'm using doxygen 1.8.7 and I set ENABLE_PREPROCESSING = yes.
>     However, when I parse a file with the following content
>
>     #ifndef FOO
>            subroutine bar(arg1, arg2)
>     #else
>            subroutine bar(arg1)
>     #endif
>            end subroutine bar
>
>     I get a state 4 error:
>     Error in file ...doxybug.f90 line: 7, state: 4
>
>     I see why doxygen might be struggling here; is there any way to work
>     aroung this? The meaning of the source code cannot be changed though...
>
>     By the way: bar(arg1, arg2) in the else-section doesn't work either.
>
>
>     Cheers,
>     Fabian
>
>     ------------------------------------------------------------------------------
>     Open source business process management suite built on Java and Eclipse
>     Turn processes into business applications with Bonita BPM Community
>     Edition
>     Quickly connect people, data, and systems into organized workflows
>     Winner of BOSSIE, CODIE, OW2 and Gartner awards
>     http://p.sf.net/sfu/Bonitasoft
>     _______________________________________________
>     Doxygen-users mailing list
>     Dox...@li...
>     <mailto:Dox...@li...>
>     https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>

[Doxygen-users] documentation support for UVM code

[vijaya k. <vij...@re...>]

Hi,
    I would like to know doxygen has support for UVM code.

Regards
Vijaya

Re: [Doxygen-users] Preprocessing + different subroutine headers (FORTRAN)

[Albert <alb...@gm...>]

Fabian,

F90 is already supported, as extension and will automatically do the
preprocessing. The preprocessing of Fortran file is governed by the routine:
bool FortranLanguageScanner::needsPreprocessing(const QCString &extension)
{
  return extension!=extension.lower(); // use preprocessor only for upper
case extensions
}
in fortranscanner.l

Your question regarding to do always preprocessing :
Normal convention in the Fortran world is that lowercase extension is not
preprocessed and uppercase extension is preprocessed. So I don't think it
would be wise to do this.

Albert



On Wed, Jul 2, 2014 at 3:35 PM, Fabian Nick <fab...@sc...>
wrote:

> Albert,
>
> forget my last message.
>
> However it would be nice if I could build a version where *.f90 is
> preprocessed as well... Any chance to do so?!
>
>
> Fabian
>
>
> * From: Albert (alb...@gm...)
> * To: Fabian Nick (fab...@sc...)
> * Sent:  02.07.2014 at 15:01 +0200
> * Subject: Re: [Doxygen-users] Preprocessing + different subroutine
> headers (FORTRAN)
>
>> Hi Fabian,
>>
>>
>> I see you use the extension f90, to enable preprocessing for Fortran you
>> have to use F90 as extension.
>>
>> Albert
>>
>>
>> On Wed, Jul 2, 2014 at 2:36 PM, Fabian Nick
>> <fab...@sc... <mailto:fab...@sc...>>
>>
>> wrote:
>>
>>     Hi all,
>>
>>     I'm using doxygen 1.8.7 and I set ENABLE_PREPROCESSING = yes.
>>     However, when I parse a file with the following content
>>
>>     #ifndef FOO
>>            subroutine bar(arg1, arg2)
>>     #else
>>            subroutine bar(arg1)
>>     #endif
>>            end subroutine bar
>>
>>     I get a state 4 error:
>>     Error in file ...doxybug.f90 line: 7, state: 4
>>
>>     I see why doxygen might be struggling here; is there any way to work
>>     aroung this? The meaning of the source code cannot be changed
>> though...
>>
>>     By the way: bar(arg1, arg2) in the else-section doesn't work either.
>>
>>
>>     Cheers,
>>     Fabian
>>
>>     ------------------------------------------------------------
>> ------------------
>>     Open source business process management suite built on Java and
>> Eclipse
>>     Turn processes into business applications with Bonita BPM Community
>>     Edition
>>     Quickly connect people, data, and systems into organized workflows
>>     Winner of BOSSIE, CODIE, OW2 and Gartner awards
>>     http://p.sf.net/sfu/Bonitasoft
>>     _______________________________________________
>>     Doxygen-users mailing list
>>     Dox...@li...
>>     <mailto:Dox...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/doxygen-users
>>
>>
>>

Re: [Doxygen-users] Preprocessing + different subroutine headers (FORTRAN)

[Fabian N. <fab...@sc...>]

Albert,

forget my last message.

However it would be nice if I could build a version where *.f90 is 
preprocessed as well... Any chance to do so?!

Fabian


* From: Albert (alb...@gm...)
* To: Fabian Nick (fab...@sc...)
* Sent:  02.07.2014 at 15:01 +0200
* Subject: Re: [Doxygen-users] Preprocessing + different subroutine 
headers (FORTRAN)
> Hi Fabian,
>
> I see you use the extension f90, to enable preprocessing for Fortran you
> have to use F90 as extension.
>
> Albert
>
>
> On Wed, Jul 2, 2014 at 2:36 PM, Fabian Nick
> <fab...@sc... <mailto:fab...@sc...>>
> wrote:
>
>     Hi all,
>
>     I'm using doxygen 1.8.7 and I set ENABLE_PREPROCESSING = yes.
>     However, when I parse a file with the following content
>
>     #ifndef FOO
>            subroutine bar(arg1, arg2)
>     #else
>            subroutine bar(arg1)
>     #endif
>            end subroutine bar
>
>     I get a state 4 error:
>     Error in file ...doxybug.f90 line: 7, state: 4
>
>     I see why doxygen might be struggling here; is there any way to work
>     aroung this? The meaning of the source code cannot be changed though...
>
>     By the way: bar(arg1, arg2) in the else-section doesn't work either.
>
>
>     Cheers,
>     Fabian
>
>     ------------------------------------------------------------------------------
>     Open source business process management suite built on Java and Eclipse
>     Turn processes into business applications with Bonita BPM Community
>     Edition
>     Quickly connect people, data, and systems into organized workflows
>     Winner of BOSSIE, CODIE, OW2 and Gartner awards
>     http://p.sf.net/sfu/Bonitasoft
>     _______________________________________________
>     Doxygen-users mailing list
>     Dox...@li...
>     <mailto:Dox...@li...>
>     https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>

Re: [Doxygen-users] Preprocessing + different subroutine headers (FORTRAN)

[Albert <alb...@gm...>]

Hi Fabian,

I see you use the extension f90, to enable preprocessing for Fortran you
have to use F90 as extension.

Albert


On Wed, Jul 2, 2014 at 2:36 PM, Fabian Nick <fab...@sc...>
wrote:

> Hi all,
>
> I'm using doxygen 1.8.7 and I set ENABLE_PREPROCESSING = yes.
> However, when I parse a file with the following content
>
> #ifndef FOO
>       subroutine bar(arg1, arg2)
> #else
>       subroutine bar(arg1)
> #endif
>       end subroutine bar
>
> I get a state 4 error:
> Error in file ...doxybug.f90 line: 7, state: 4
>
> I see why doxygen might be struggling here; is there any way to work
> aroung this? The meaning of the source code cannot be changed though...
>
> By the way: bar(arg1, arg2) in the else-section doesn't work either.
>
>
> Cheers,
> Fabian
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

[Doxygen-users] Preprocessing + different subroutine headers (FORTRAN)

[Fabian N. <fab...@sc...>]

Hi all,

I'm using doxygen 1.8.7 and I set ENABLE_PREPROCESSING = yes.
However, when I parse a file with the following content

#ifndef FOO
      subroutine bar(arg1, arg2)
#else
      subroutine bar(arg1)
#endif
      end subroutine bar

I get a state 4 error:
Error in file ...doxybug.f90 line: 7, state: 4

I see why doxygen might be struggling here; is there any way to work 
aroung this? The meaning of the source code cannot be changed though...

By the way: bar(arg1, arg2) in the else-section doesn't work either.


Cheers,
Fabian

[Doxygen-users] Question about Table

[Robert M. <rm...@or...>]

Hi

It's the first time I'm using doxygen for c++ documentation.

I want to insert a table but I don't have the same result in html output 
and in rtf output :

1/ Declaration in c++ header

*|31-------------------------------------------16|15-------------------------------------------00| 

*|:---------------------------------------------:|:---------------------------------------------:|
*|CHANNELID|PACKETSYNCPATTERN|
*|PACKETLENGTH||
*

2/HTML output :


3/ RTF output :


==> How can I replace the "----" by whitespace ?
==> How can I obtain the same result in HTML than in RTF without using 
HTML code ?

Thanks

Bob

Re: [Doxygen-users] How to disable automatic lists?

[Christoph L. <chr...@li...>]

As far as I know this kind of automatic numbering is part of Doxygen's 
markdown support, so MARKDOWN_SUPPORT=NO should turn it off. You'll 
still be able to create numbered lists by using "-#" markers.

Alternatively, you might want to use a different numbering format, such as:

     //! (1.3) Save pointers internally
     //! (1.4) Call init => set test patterns
     //! (2) EXECUTE


Am 02.07.2014 06:19, schrieb vok...@gm...:
> Hello,
>
> i use this kind of numbering my comments inside my code:
>
>     //! 1.3 Save pointers internally
>     if (eResult == eHWT_OK)
>     {
>       pulIntOvStartAdr = pulOvStartAdr;
>       pulIntOvEndAdr = pulOvEndAdr;
>       pulIntUvAdr = pulUfAdr;
>       //! 1.4 Call init => set test patterns
>       (void)HwtStackInit( pulIntOvStartAdr, pulIntOvEndAdr, pulIntUvAdr);
>     }
>     //lint +e920
>     break;
>   case eSTACK_TEST_EXECUTE:
>     //! 2. EXECUTE
>
> But doxygen produces this:
>
> 1.3 Save pointers internally
>
> 1.4 Call init => set test patterns
>
>  1. EXECUTE
>
> How can i disable this feature?
>
> Best regards
>
> vokuit00
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
>
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] How to disable automatic lists?

[<vok...@gm...>]

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>&nbsp;</div>

<div class="signature"><font face="Arial">Hello,<br/>
<br/>
i use this kind of numbering my comments inside my code:<br/>
<br/>
<font face="Courier New">&nbsp;&nbsp;&nbsp; //! 1.3 Save pointers internally<br/>
&nbsp;&nbsp;&nbsp; if (eResult == eHWT_OK)<br/>
&nbsp;&nbsp;&nbsp; {<br/>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pulIntOvStartAdr = pulOvStartAdr;&nbsp;&nbsp;<br/>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pulIntOvEndAdr = pulOvEndAdr;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br/>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pulIntUvAdr = pulUfAdr;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br/>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //! 1.4 Call init =&gt; set test patterns<br/>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (void)HwtStackInit( pulIntOvStartAdr, pulIntOvEndAdr, pulIntUvAdr);<br/>
&nbsp;&nbsp;&nbsp; }<br/>
&nbsp;&nbsp;&nbsp; //lint +e920<br/>
&nbsp;&nbsp;&nbsp; break;<br/>
&nbsp; case eSTACK_TEST_EXECUTE:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br/>
&nbsp;&nbsp;&nbsp; //! 2. EXECUTE</font><br/>
<br/>
But doxygen produces this:</font><br/>
&nbsp;
<p>1.3 Save pointers internally</p>

<p>1.4 Call init =&gt; set test patterns</p>

<ol type="1">
	<li>EXECUTE</li>
</ol>
How can i disable this feature?<br/>
<br/>
Best regards<br/>
<br/>
vokuit00</div></div></body></html>

[Doxygen-users] Is Doxigen easily support in javascript?

[Hananya B. <han...@ka...>]

Is Doxigen easily support in javascript?

Re: [Doxygen-users] show directory list

[Dimitri v. H. <do...@gm...>]

Hi Clemens,

The directory and file lists have been merged into one hierarchical list showing both.

Regards,
  Dimitri

On 23 Jun 2014, at 12:05 , Clemens Feige <c....@os...> wrote:

> Hello.
> 
> I am missing a "List of directories" in doxygen HTML output. For complex 
> source code repositories it is desired to see what directories exist.
> 
> According to release notes since version 1.8.1 the "SHOW_DIRECTORIES" is 
> no longer used. But where is the directory list?
> 
> If I remember right, then older Doxygen version (e.g. 1.5.0) offered 
> such "Directory list" very similar to the "File list".
> 
> I am using doxygen 1.8.5 on .NET code under Windows.
> 
> Clemens
> 
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] line numbers in \code blocks

[Fabio M. <fa...@vi...>]

hi everybody,
how can I add line numbers in \code ... \endcode blocks? I can't find an 
option neither in the config file or the online documentation.

it is possible to do that?

thank you all

-- 
*Fabio Mosti*
titolare - direzione produzione
fa...@vi... <mailto:fa...@vi...>
cell. +39.329.434.90.95
skype fabio.massimo.mosti

*Videoarts Webdesign*
via Floriano Ambrosini 2/b
40131 Bologna BO
tel. +39.051.098.08.21
fax +39.051.199.31.222
in...@vi... <mailto:in...@vi...>
www.videoarts.eu <http://www.videoarts.eu>
skype videoarts.webdesign

p.iva 02263631208
cod.fisc. MSTFBA79B26A944C

[Doxygen-users] LaTeX layout: unexpected new page: bug?

[Frédéric D. <Fre...@or...>]

Hello,

I have a problem with the layout of a pdf file generated by Doxygen (v. 
1.8.7) through LaTeX: a table is placed at the top a page while the 
previous page has a large empty space (large enough for this table).

It is difficult for me to send you a minimal example because of the 
complexity of the LaTeX file generated by Doxygen. Anyway, I could 
reproduce the problem by including several times in a row (\input{}) a 
file containing the following structure:
%%%%%%%%%%%%%%%%%%%%
\subsection{Here a title which is several lines long}

A short paragraph (single line)

A DoxyParams Table
%%%%%%%%%%%%%%%%%%%%

I also noticed that:
- the table, which appears several times in the document, is generally 
well-placed (sometimes starting at the bottom of a page and ending at 
the top of the next page, but this is not an issue).
- the unexpected new page disappears if a second short paragraph is 
inserted between the subsection title and the table.
- the LaTeX logfile does not seem to report any problem, with very few 
differences between the pathologic case and the 2-short-paragraph case.


I am wondering if this is a Doxygen bug.


Cheers.

Frédéric Darboux


	
-- 
.......................................................
UR Science du Sol
INRA
2163 Avenue de la Pomme de Pin
CS 40001 - Ardon
F-45075 Orléans Cedex 2
France
  Ph:   +33 2 38 41 48 23
  Fax:  +33 2 38 41 78 69
  Email: <Fre...@or...>
  WebPage: <http://tinyurl.com/DarbouxInraFr>
  Lab.: <http://www6.val-de-loire.inra.fr/ur-sols/>

Re: [Doxygen-users] Multiple external search databases

[Keith R. <Kei...@ne...>]

I think I've found an answer myself.

The key is having multiple cgi directories configured on the webserver, using the ScriptAlias directive, one for each 'product' and then putting (or using a symlink) a copy of the doxysearch.cgi binary in each one along with the product specific search database. Then you need some way (script) to manipulate the Doxyfile for each component, for example to insert the correct SEARCHENGINE_URL setting when building the components documentation.

Keith



Hi,

We're playing around with using the External Indexing and Searching facility of Doxygen, and have a question regarding the doxysearch.db generation and usage. What we would ideally like (I think) is the ability to have multiple doxysearch.db files, one per product (version). So for example:

Product A-1.0 depends on Library foo-1.0 and Library bar-1.0
Product B-2.0 depends on Library foo-2.0 and Library qux-2.2

For Product A there would be a doxysearch-A-1.0.db, and for Product B a doxysearch-B-2.0.db (using the Multi project index method of generating the db). These would need to live 'somewhere' on the webserver, and the right one chosen depending on what Product/Library (with version) was being accessed.

Is this currently possible? Apologies if some of this is webserver configuration related, but I'm a bit of a novice with webservers!

Keith

[Doxygen-users] Print a string from a file to "output produced by doxygen" (i.e. log)

[Lorenzo R. <lor...@gm...>]

Hi everyone,
is it possible to print a string to the output produced by doxygen during
the run? (i.e. the log of the run)

All the best,
Lorenzo

[Doxygen-users] show directory list

[Clemens F. <c....@os...>]

Hello.

I am missing a "List of directories" in doxygen HTML output. For complex 
source code repositories it is desired to see what directories exist.

According to release notes since version 1.8.1 the "SHOW_DIRECTORIES" is 
no longer used. But where is the directory list?

If I remember right, then older Doxygen version (e.g. 1.5.0) offered 
such "Directory list" very similar to the "File list".

I am using doxygen 1.8.5 on .NET code under Windows.

Clemens

[Doxygen-users] Multiple external search databases

[Keith R. <Kei...@ne...>]

Hi,

We're playing around with using the External Indexing and Searching facility of Doxygen, and have a question regarding the doxysearch.db generation and usage. What we would ideally like (I think) is the ability to have multiple doxysearch.db files, one per product (version). So for example:

Product A-1.0 depends on Library foo-1.0 and Library bar-1.0
Product B-2.0 depends on Library foo-2.0 and Library qux-2.2

For Product A there would be a doxysearch-A-1.0.db, and for Product B a doxysearch-B-2.0.db (using the Multi project index method of generating the db). These would need to live 'somewhere' on the webserver, and the right one chosen depending on what Product/Library (with version) was being accessed.

Is this currently possible? Apologies if some of this is webserver configuration related, but I'm a bit of a novice with webservers!

Keith

[Doxygen-users] Feature request: call graph annotations

[Ph. M. <phi...@ma...>]

Hi,

I'd like to post a feature request here.

I'd like to have some doxygen directive that says that some specific
function is run in some (named) thread(s), perhaps giving some color code
there, too.

This color (as a bar, or stripe, or dot, or whatever) and/or the thread
name(s) should be used in the call and caller graphs to see in which threads
each function might get called.

(I'm well aware that currently only simple "inheritance" is possible, ie. if
a function runs as thread X, then all functions called by it are marked for
x, too; implementing some static code path analysis like LLVM does would be
nice, but is much more work.
[Static analysis might show that not _all_ sub-functions are called by a
thread, so the call graph thread flags could be reduced.])


Thank you for considering that idea!


Regards,

Phil