doxygen-users — List for users of doxygen

[Doxygen-users] MultiThread computing BUG

[Sima Z. S. E. <zde...@zf...>]

Hi,
I have laptop with Intel i7-4800MQ processor (4 cores, 8 threads). During Doxygen performance is my laptop totally frozen. I guess that the reason is using 9 threads by Doxygen.
Doxygen log file contains this information: generating dot graphs using 9 parallel threads

Regards
Zdenek
--
ZF Lenksysteme GmbH, Richard-Bullinger-Str. 77, 73527 Schwäbisch Gmünd, Germany
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Wolf-Henning Scheider
Geschäftsführung/Management Board: Christian Sobottka (Vorsitz/Chairman), Hanns Bernd Ketteler, Marcus Parche, Henning Wagner
Sitz der Gesellschaft/Headquarters: Schwäbisch Gmünd - Handelsregistereintrag: Amtsgericht Ulm HRB 701678/Trade register of the municipal court of Ulm HRB 701678

[Doxygen-users] Doxygen problem with C++ templates

[John H. <joh...@gm...>]

Here is a short C++ template class that generates a doxygen warning
and incorrect documentation.

Doxygen reports this error:

doxy.h:15: warning: Member assign(Other first, Other last) (function)
of class A is not documented.

In the HTML I see two listings for the assign method. One has the
correct documentation and the other does not. It seems to be confusing
the definition at the bottom of the file as a different method than
the declaration.

Ideas?

Thanks,

John


template<class T> struct enable_if<true, T> { typedef T type; };

/** A class */
template<class T>
class A {
  public:
    /** assign docs. Something else. */
    template<class Other>
    typename enable_if<true, void>::type assign(Other first, Other last);
};

template<class T>
template<class Other>
typename enable_if<true, void>::type A<T>::assign(Other first, Other last)
{ }

[Doxygen-users] Fortran module heirarchy

[W. M. <wad...@gm...>]

Hello,

I would like Doxygen to show Fortran 90 module hierarchy. For example,
module A uses module B which in turn uses module C:

A -> B -> C

Any help will be greatly appreciated.

Thanks in advance,
Wadud.

Re: [Doxygen-users] Issues with tag files

[Karl W. <kar...@gm...>]

Hi Dimitri,

Thank you for your reply. I have posted the following two bug reports
for these issues:

https://bugzilla.gnome.org/show_bug.cgi?id=743604
https://bugzilla.gnome.org/show_bug.cgi?id=743605

Both contain examples that should reproduce the issue. Please let me
know if further information is required.

Cheers, Karl


On 22 January 2015 at 21:52, Dimitri van Heesch <do...@gm...> wrote:
> Hi Karl,
>
> Sounds like an unwanted site effect of the recent restructuring of the tag file generation.
>
> Can you file a bug report for each of the issues here:
> https://bugzilla.gnome.org/enter_bug.cgi?product=doxygen
> Please include a minimal self-contained example that allows me to
> reproduce the issue.
>
> Regards,
>   Dimitri
>
>> On 22 Jan 2015, at 6:19 , Karl Wette <kar...@gm...> wrote:
>>
>> Hi,
>>
>> I am seeing two issues with tagfiles after upgrading from Doxygen
>> v1.8.6 to v1.8.9.1. I'm not sure whether they are bugs or deliberate
>> changes in behaviour, but they are causing problems for the libraries
>> I document so I need to work around them. Apologies if they are
>> already known, but I've  been unable to find any reference to them in
>> bugzilla or in the mailing list archives.
>>
>> 1st issue: in v.1.8.6 tagfiles included only documentation anchors
>> from the code being documented, whereas v1.8.9.1 also includes anchors
>> from any tagfiles included via TAGFILES. This causes problems with
>> complicated library dependencies: if libraries B and C depend on
>> library A, and library D depends on B and C, the documentation of D
>> will get two copies of the anchors in library A (via the tagfiles of B
>> and C) and Doxygen will generate a lot of warnings.
>>
>> 2nd issue: in v1.8.6 tagfiles included anchors for enumeration values
>> (<enumvalue> elements), but in v1.8.9.1 there are generated only if
>> the enum is "strong", i.e. declared as either "enum struct" or "enum
>> class". While this might be fine for C++11 code it's not helpful for
>> plain C which is the language of the libraries I document.
>>
>> Any help would be very much appreciated. Please let me know if further
>> details are required.
>>
>> Regards,
>> Karl Wette
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Doxygen-users mailing list
>> Dox...@li...
>> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

[Doxygen-users] Java examples not linking back to Classes without long name calls

[Robert W. <rw...@er...>]

All,
I hope someone can help.  I am working with Doxygen 1.8.9.1.  Using it to
document C, C++ and Java SDK and examples.  I am able to have all of my
examples show up in the Examples menu item.  The C and C++ ones work well
as calls in the examples get properly linked back to functions in the
class (after enabling BUILTIN_STL_SUPPORT).  However, my Java examples do
not get linked back unless they are called with long names.

Example:

import com.joey.admin.Administration;

public class Java_ACLAdmin_ACLTemplate_Add {
     private String m_strServerName;
     private int m_nPort;
     private String m_strUsername;
     private String m_strPasswd;
     private AgentConnection m_conn;
public void test_addACLTemplate() throws AgentException, AdminException {
     Administration admin = new Administration();
..
Does not link
However...

import com.joey.admin.Administration;

public class Java_ACLAdmin_ACLTemplate_Add {
     private String m_strServerName;
     private int m_nPort;
     private String m_strUsername;
     private String m_strPasswd;
     private AgentConnection m_conn;
public void test_addACLTemplate() throws AgentException, AdminException {
     Administration admin = new
com.joey.admin.Administration.Administration();
..
Links correctly to the Administration() function.

Is there some sort of setting that needs to be changed to correctly
process Java examples?

RW

Re: [Doxygen-users] CALL_GRAPH and CALLER_GRAPH

[Richard D. <Ri...@Da...>]

On 1/26/15 4:28 PM, W. Miah wrote:
> Hello,
>
> I am getting a bit confused with the difference between CALL_GRAPH and
> CALLER_GRAPH. Can someone give me an example to illustrate the effects
> of setting both of them to YES and NO?
>
> Thanks in advance,
> Wadud.
A CALL_GRAPH is a listing of everything that you might call, and that 
those routines might call, and so on. These are those things the routine 
uses to complete its operation.

A CALLER_GRAPH is a listing of everything that might call you, or might 
call someone who calls you. This gives you an idea of how widely used a 
function might be.

[Doxygen-users] CALL_GRAPH and CALLER_GRAPH

[W. M. <wad...@gm...>]

Hello,

I am getting a bit confused with the difference between CALL_GRAPH and
CALLER_GRAPH. Can someone give me an example to illustrate the effects
of setting both of them to YES and NO?

Thanks in advance,
Wadud.

Re: [Doxygen-users] Doxygen 1.8.9 on Win8.1 "Error: Reference source not found" in refman.rtf :-(

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

Rolf,

Could you be a bit more specific, looks like a source file for showing the
source code cannot be found but I'm not sure from the description.
Could you create a small project showing this problem (and post it her or
in bugzilla)?

Albert

On Sat, Jan 24, 2015 at 7:46 PM, Rolf Hemmerling <hem...@gm...> wrote:

> Hello,
>
> a)
> with RTF output of Doxygen 1.8.9 on english Windows 8.1, there is the
> problem in the file refman.rtf
>
> > File Index
> >       File List
> > Here is a list of all documented files with brief descriptions:
> >
> C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/getline.c
> (Line Edited Character Input for the application "Paketwendeanlage" )
>   Error: Reference source not found
>
> while of course Doxygen was/is processing all the mentioned files,
> successfully ( as shown by the HTML output, and the logging ).
>
> If I move the "refman.rtf" file to another *german* Windows 7, the error
> message even changes to German language "Fehler: Referenz nicht gefunden".
>
> There is nothing special with the files, or the file location. I did not
> include special informations in the parsed files to handle the "File
> list" section.
>
> b)
> I found a description of this kind of bug here
>
> "Don’t Let Word Get You Down, With “Error! Reference Source Not Found”
>
> http://www.turbolaw.com/blog/2007/10/05/dont-let-word-get-you-down-with-error-reference-source-not-found/
>
>
> So I would be pleased about an improved software update :-).
>
> Sincerely
> Rolf
>
> --
> http://www.hemmerling.com
> SCADA Expertness - Quality Intensification for IT + Automation
> Member of Texas Instruments Expert Advisory Panel
> CeBIT Competence Store Partner
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] Doxygen 1.8.9 on Win8.1 is "swallowing" some (expected) characters in the log

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

Rolf,

Looks indeed a bit like a conflict between stdout and stderr.
- Is the output that you showed from a terminal window or from a file?
- can you write the warnings to a file (WARN_LOGFILE in your Doxyfile) and
catch stdout and stderr in separate files to check if there are missing
characters or not.

Albert

On Sat, Jan 24, 2015 at 7:45 PM, Rolf Hemmerling <hem...@gm...> wrote:

> Hello,
>
> Some output of Doxygen 1.8.9 on Win8.1 is "missing", see
>
> **************
> > Combining RTF output...
> > lookup cache used 44/65536 hits=71 misses=44
> > finished...
> > irq.c is not documented.
> --^
> There is never a file "irq.c" in the directory, but just "sioirq.c".
> >
> C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/sioirq.c:50:
> warning: Member oend (variable) of file sioirq.c is not documented.
> --^
> Here and everyelse, "sioirq.c" is properly displayed.
> *************
>
> This means that Doxygen at that point is "swallowing" some characters in
> the output to the log file.
>
> Maybe it is a typical "buffer problem", as known from such legacy
> software ( 1997 was initial release according to Wikipedia ), and so
> maybe the indication of much bigger fault.
>
> I didn´t check the Doxygen source code for the bug.
> I would be pleased if you can fix it, anyhow.
>
> ** Anyhow I think Doxygen is really-great software, thanks for
> development + free license **
>
> Sincerely
> Rolf
>
> Complete output of Doxygen:
> ************************************
>
> C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/sioirq.c:37:
> warning: Member S0BUF (macro definition) of file sioirq.c is not
> documented.
>
> C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/sioirq.c:38:
> warning: Member RI0 (macro definition) of file sioirq.c is not documented.
>
> ...
>
> finalizing index lists...
> writing tag file...
> Combining RTF output...
> lookup cache used 44/65536 hits=71 misses=44
> finished...
> irq.c is not documented.
>
> C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/sioirq.c:50:
> warning: Member oend (variable) of file sioirq.c is not documented.
> ...
> *** Doxygen has finished
> ************************************
> --
> http://www.hemmerling.com
> SCADA Expertness - Quality Intensification for IT + Automation
> Member of Texas Instruments Expert Advisory Panel
> CeBIT Competence Store Partner
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] char_varying type in VOS C and doxygen

[Ron W <ron...@gm...>]

>
> On Sat, Jan 24, 2015 at 1:46 PM, <
> dox...@li...> wrote:
> Date: Sat, 24 Jan 2015 17:32:34 +0100
> From: Uwe Scholz <u.s...@gm...>
> Subject: Re: [Doxygen-users] char_varying type in VOS C and doxygen
>
> @Ron, thank you, too! Your perl script looks also nice, maybe I'll need
> it in the future for other purposes. :) But Dmitri's one-liner solved
> this issue for me.
>

Thanks.

I had forgotten about the C preprocessor's ## operator because the coding
rules where I work forbid its use (along with other "advanced" features of
the preprocessor). So I am in the habit of creating filters (usually in
Perl) to perform tasks that the preprocessor could otherwise handle quite
well.

[Doxygen-users] Doxygen 1.8.9 on Win8.1 "Error: Reference source not found" in refman.rtf :-(

[Rolf H. <hem...@gm...>]

Hello,

a)
with RTF output of Doxygen 1.8.9 on english Windows 8.1, there is the 
problem in the file refman.rtf

> File Index
> 	File List
> Here is a list of all documented files with brief descriptions:
> C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/getline.c (Line Edited Character Input for the application "Paketwendeanlage" ) 	Error: Reference source not found

while of course Doxygen was/is processing all the mentioned files, 
successfully ( as shown by the HTML output, and the logging ).

If I move the "refman.rtf" file to another *german* Windows 7, the error 
message even changes to German language "Fehler: Referenz nicht gefunden".

There is nothing special with the files, or the file location. I did not 
include special informations in the parsed files to handle the "File 
list" section.

b)
I found a description of this kind of bug here

"Don’t Let Word Get You Down, With “Error! Reference Source Not Found”
http://www.turbolaw.com/blog/2007/10/05/dont-let-word-get-you-down-with-error-reference-source-not-found/


So I would be pleased about an improved software update :-).

Sincerely
Rolf

-- 
http://www.hemmerling.com
SCADA Expertness - Quality Intensification for IT + Automation
Member of Texas Instruments Expert Advisory Panel
CeBIT Competence Store Partner

[Doxygen-users] Doxygen 1.8.9 on Win8.1 is "swallowing" some (expected) characters in the log

[Rolf H. <hem...@gm...>]

Hello,

Some output of Doxygen 1.8.9 on Win8.1 is "missing", see

**************
> Combining RTF output...
> lookup cache used 44/65536 hits=71 misses=44
> finished...
> irq.c is not documented.
--^
There is never a file "irq.c" in the directory, but just "sioirq.c".
> C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/sioirq.c:50: warning: Member oend (variable) of file sioirq.c is not documented.
--^
Here and everyelse, "sioirq.c" is properly displayed.
*************

This means that Doxygen at that point is "swallowing" some characters in 
the output to the log file.

Maybe it is a typical "buffer problem", as known from such legacy 
software ( 1997 was initial release according to Wikipedia ), and so 
maybe the indication of much bigger fault.

I didn´t check the Doxygen source code for the bug.
I would be pleased if you can fix it, anyhow.

** Anyhow I think Doxygen is really-great software, thanks for 
development + free license **

Sincerely
Rolf

Complete output of Doxygen:
************************************
C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/sioirq.c:37: 
warning: Member S0BUF (macro definition) of file sioirq.c is not documented.
C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/sioirq.c:38: 
warning: Member RI0 (macro definition) of file sioirq.c is not documented.

...

finalizing index lists...
writing tag file...
Combining RTF output...
lookup cache used 44/65536 hits=71 misses=44
finished...
irq.c is not documented.
C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/sioirq.c:50: 
warning: Member oend (variable) of file sioirq.c is not documented.
...
*** Doxygen has finished
************************************
-- 
http://www.hemmerling.com
SCADA Expertness - Quality Intensification for IT + Automation
Member of Texas Instruments Expert Advisory Panel
CeBIT Competence Store Partner

Re: [Doxygen-users] char_varying type in VOS C and doxygen

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

> On 24 Jan 2015, at 17:32 , Uwe Scholz <u.s...@gm...> wrote:
> 
> Hi Dimitri,
> 
> great, that looks good! I didn't know that one could parse the numbers
> in that way. Is this style documented somewhere?

It is a standard C preprocessor feature, see also
https://gcc.gnu.org/onlinedocs/cpp/Concatenation.html

Regards,
  Dimitri

Re: [Doxygen-users] char_varying type in VOS C and doxygen

[Uwe S. <u.s...@gm...>]

Hi Dimitri,

great, that looks good! I didn't know that one could parse the numbers
in that way. Is this style documented somewhere?

Thanks again for your quick help!

@Ron, thank you, too! Your perl script looks also nice, maybe I'll need
it in the future for other purposes. :) But Dmitri's one-liner solved
this issue for me.

Ciao,
Uwe

Dimitri van Heesch <do...@gm...> schrieb am [Fri, 23.01.2015 20:56]:
> Hi Uwe,
> 
> You could use
> 
> PREDEFINED = char_varying(n)="char_varying_##n"
> 
> To expand char_varying(256) to char_varying_256 and then during post processing replace it back to char_varying(256).
> 
> Regards,
>   Dimitri
> 
> > On 22 Jan 2015, at 13:47 , Uwe Scholz <u.s...@gm...> wrote:
> > 
> > Imagine this file is given:
> > ----------------------
> > /** @file foo.c
> > */
> > char_varying(256) var;
> > main(){}
> > ----------------------(1)
> >
> > [...]
> >
> > What I tried already: 
> > 
> > MACRO_EXPANSION = YES
> > EXPAND_ONLY_PREDEF = YES
> > PREDEFINED = char_varying()=
> > 
> > [...] What I would like to see here is:
> > ----------------------
> > foo.c File Reference
> > Functions
> > 	main ()
> > 
> > Variables
> > 	char_varying(256) var
> > ----------------------(4)
> > 
> > It would be great if someone can help me out here.
> > 
> > Best wishes
> > Uwe

[Doxygen-users] Maximizing warnings for missing doxygen

[Barnes, P. D. <bar...@ll...>]

Hello Folks,

I need help configuring Doxygen to generate warnings on *any* undocumented items.  

There are a few cases which seem to pass without warnings, despite the obvious Doxyfile config options.  There are other cases which generate warnings for parameters and return values, but only if the brief description ends with '.' (We have autobrief enabled).  See below for examples.

I think the relevant Doxyfile config parameters are:
> EXTRACT_ALL            = NO
> EXTRACT_PRIVATE        = YES
> EXTRACT_PACKAGE        = NO
> EXTRACT_STATIC         = yes
> EXTRACT_LOCAL_CLASSES  = YES
> EXTRACT_LOCAL_METHODS  = NO
> EXTRACT_ANON_NSPACES   = YES
> HIDE_UNDOC_MEMBERS     = NO
> HIDE_UNDOC_CLASSES     = NO
> HIDE_FRIEND_COMPOUNDS  = NO
> HIDE_IN_BODY_DOCS      = NO
> INTERNAL_DOCS          = YES
> JAVADOC_AUTOBRIEF      = YES
> QT_AUTOBRIEF           = YES
> 
> QUIET                  = NO
> WARNINGS               = YES
> WARN_IF_UNDOCUMENTED   = YES
> WARN_IF_DOC_ERROR      = YES
> WARN_NO_PARAMDOC       = YES
> WARN_FORMAT            = "$file:$line: $text"
> WARN_LOGFILE           = doxygen.log

Are there other configuration variables I should look at?  Or different values of these variables?

Thanks,
Peter

----------
Below are some examples which fail to generate warnings.  Where partial documentation is given, it doesn't matter whether it's JavaDoc style ('/** ... */'), Qt style ('/*! ... */') or C++ style ('/// ...').

> // Undoc'd named namespace.                       // NO WARN
> namespace undoc {
>   
> // Undoc'd func.
> void unsFuncUndoc (void);                         // warn function
> 
> /** Doc'd func with undoc'd param */              // NO WARN
> void unsFuncUndocArg (int foo);
> 
> /** Doc'd func with undoc'd return value */       // NO WARN
> int unsFuncUndocReturn (void);
>  
> }  // namespace undoc


The undocumented function gets a warning, but undocumented parameters or return value don't.  If the namespace itself is documented, all of these cases generate warnings.

Another namespace example:

> // Undoc'd anonymous namespace.                   // NO WARN
> namespace  {
>   …
> }  // anonymous namespace


Undocumented namespaces, either named or anonymous, don't seem to generate any warnings ever.


> // Undoc'd default constructor
> class Foo {
>     Foo (void);                                  // NO WARN

> };


Constructors with parameters do generate a warning (but see below).


Here's another set which fail to generate warnings *unless the brief description ends with '.'*

> /** \file */  // Required to trigger warnings at global scope:
> 

> /** Doc'd func with undoc'd param */              // DOT WARN parameters
> void FuncUndocArg (int foo);
> 
> /** Doc'd func with undoc'd return */             // DOT WARN return
> int FuncUndocReturn (void);


> // Undoc'd anonymous namespace or doc'd named namespace
> // (See above for undoc'd named namespace)
> namespace  {
> 
> /** Doc'd func with undoc'd param */              // DOT WARN parameters
> void ansFuncUndocArg (int foo);
> 
> /** Doc'd func with undoc'd return */             // DOT WARN return
> int ansFuncUndocReturn (void);
>  
> }  // anonymous namespace



> class Foo
> {
> 
>   // public or private:
> 
>   /** Doc'd (public) ctor with undoc'd param */   // DOT WARN parameters
>   ClassUndoc (int foo);
>   
>   /** Doc'd member func with undoc'd param */     // DOT WARN parameters
>   void pubMemFuncUndocArg (int foo);
> 
>   /** Doc'd member func with undoc'd return */    // DOT WARN return
>   int pubMemFuncUndocReturn (void);


(These are from a longer test file, which marks each statement with the type of warning, or lack thereof, on the same line as reported by doxygen.  I can forward that if it would be helpful.)

Thanks,
Peter

In case versions matter:   doxygen 1.8.9.1, Mac 10.8.5, gcc 4.2.1.
_______________________________________________________________________
Dr. Peter D. Barnes, Jr.                Physics Division
Lawrence Livermore National Laboratory  Physical and Life Sciences
7000 East Avenue, L-50                  email:  pdb...@ll...
P. O. Box 808                           Voice:  (925) 422-3384
Livermore, California 94550             Fax:    (925) 423-3371

Re: [Doxygen-users] char_varying type in VOS C and doxygen

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

Hi Uwe,

You could use

PREDEFINED = char_varying(n)="char_varying_##n"

To expand char_varying(256) to char_varying_256 and then during post processing replace it back to char_varying(256).

Regards,
  Dimitri

> On 22 Jan 2015, at 13:47 , Uwe Scholz <u.s...@gm...> wrote:
> 
> Hi,
> 
> I have a new issue to solve with doxygen: In VOS C there exists the type 
> char_varying(n), where n is the number of characters of the variable. 
> Basically, this type is nearly the same as a char array, but there exist
> some differences, especially regarding assignments[*].
> 
> A typical variable declaration looks like this:
> char_varying(10) foo;
> 
> and a definition looks like this:
> char_varying(10) foo = "string";
> 
> where "10" is just an arbitrary choice for this example.
> 
> Imagine this file is given:
> ----------------------
> /** @file foo.c
> */
> char_varying(256) var;
> main(){}
> ----------------------(1)
> 
> Doxygen assumes that char_varying is a function here, but as said above, 
> this is just the type, and var is the variable. The doxygen html output 
> in this case is just:
> ----------------------
> foo.c File Reference
> Functions
> 	char_varying (256)
> ----------------------(2)
> 
> Is there any possibility to solve this somehow?
> 
> What I tried already: 
> 
> MACRO_EXPANSION = YES
> EXPAND_ONLY_PREDEF = YES
> PREDEFINED = char_varying()=
> 
> This leads to the following html output:
> ----------------------
> foo.c File Reference
> Functions
> 	main ()
> 
> Variables
> 	var
> ----------------------(3)
> 	
> This is much better, but the type of "var" is missing now. What I would 
> like to see here is:
> ----------------------
> foo.c File Reference
> Functions
> 	main ()
> 
> Variables
> 	char_varying(256) var
> ----------------------(4)
> 
> It would be great if someone can help me out here.
> 
> Best wishes
> Uwe
> 
> [*] Following the link below, you can find the char_varying documentation 
>    from Stratus
> http://stratadoc.stratus.com/vos/15.1.1/r040-02/wwhelp/wwhimpl/js/html/wwhelp.htm?context=r040-02&file=ch4r040-02ae.html
> 
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] char_varying type in VOS C and doxygen

[Ron W <ron...@gm...>]

On Thu, Jan 22, 2015 at 11:14 PM, <
dox...@li...> wrote:

> Date: Thu, 22 Jan 2015 13:47:52 +0100
> From: "Uwe Scholz" <u.s...@gm...>
> Subject: [Doxygen-users] char_varying type in VOS C and doxygen
>
> I have a new issue to solve with doxygen: In VOS C there exists the type
> char_varying(n), where n is the number of characters of the variable.
>
> Imagine this file is given:
> ----------------------
> /** @file foo.c
>  */
> char_varying(256) var;
> main(){}
> ----------------------(1)
>
> Doxygen assumes that char_varying is a function here, but as said above,
> this is just the type, and var is the variable. The doxygen html output
> in this case is just:
> ----------------------
> foo.c File Reference
> Functions
>         char_varying (256)
> ----------------------(2)
>
> Is there any possibility to solve this somehow?
>
> What I tried already:
>
> MACRO_EXPANSION = YES
> EXPAND_ONLY_PREDEF = YES
> PREDEFINED = char_varying()=
>

Try:

 PREDEFINED = char_varying()=char_varying

If want the length to be captured, you would need a custom filter to
preprocess your VOS C sources.

In Perl, something like the following should work:

#!perl -w
use strict;
use warnings;
while (<>)
{

s/char_varying\s*[(]\s*(\d+)\s*[)]\s+([_A-Za-z][_A-Za-z0-9]*)\s*[;]/char_varying
$2[$1];/;
    print $_;
}

Note that the above will expect an actual, decimal (or octal) number
between the parenthesis after char_varying.

For it to accept a number or symbol, try replacing:

    (\d+)

with:

    ([_A-Za-z0-9]+)

This alternate expression will also match hexadecimal numbers.

[Doxygen-users] issue with java element name

[xyisly <xyi...@ho...>]

hi,

I had issue when analysis some java packages with doxygen. There is a class
named "CUP$XPathParser$actions", while doxygen regard this class as
"$acgtion".
The constructor of this function is translated in to "CUP $XPathParser
$actions(...)", a function with return value "$XPathParser". 

<http://doxygen.10944.n7.nabble.com/file/n6996/name.png> 

There may be something wrong in doxygen when reading java code, since the
{ID} in scanner.l is defined without considering java element name with
multi special character like '$' and ‘￥’.

Another possible reason is that my configuration file has problems. My
doxygen configuration file is shown below.
Best wishes.

----------------------------------------------------------------
# Doxyfile 1.8.9.1

#---------------------------------------------------------------------------
# Project related configuration options
#---------------------------------------------------------------------------
DOXYFILE_ENCODING      = UTF-8
PROJECT_NAME           = "My Project"
PROJECT_NUMBER         = 
PROJECT_BRIEF          = 
PROJECT_LOGO           = 
OUTPUT_DIRECTORY       = 
CREATE_SUBDIRS         = YES
ALLOW_UNICODE_NAMES    = NO
OUTPUT_LANGUAGE        = English
BRIEF_MEMBER_DESC      = YES
REPEAT_BRIEF           = YES
ABBREVIATE_BRIEF       = "The $name class" \
                         "The $name widget" \
                         "The $name file" \
                         is \
                         provides \
                         specifies \
                         contains \
                         represents \
                         a \
                         an \
                         the
ALWAYS_DETAILED_SEC    = NO
INLINE_INHERITED_MEMB  = NO
FULL_PATH_NAMES        = YES
STRIP_FROM_PATH        = 
STRIP_FROM_INC_PATH    = 
SHORT_NAMES            = NO
JAVADOC_AUTOBRIEF      = YES
QT_AUTOBRIEF           = NO
MULTILINE_CPP_IS_BRIEF = NO
INHERIT_DOCS           = YES
SEPARATE_MEMBER_PAGES  = NO
TAB_SIZE               = 4
ALIASES                = 
TCL_SUBST              = 
OPTIMIZE_OUTPUT_FOR_C  = NO
OPTIMIZE_OUTPUT_JAVA   = YES
OPTIMIZE_FOR_FORTRAN   = NO
OPTIMIZE_OUTPUT_VHDL   = NO
EXTENSION_MAPPING      = 
MARKDOWN_SUPPORT       = YES
AUTOLINK_SUPPORT       = YES
BUILTIN_STL_SUPPORT    = NO
CPP_CLI_SUPPORT        = NO
SIP_SUPPORT            = NO
IDL_PROPERTY_SUPPORT   = YES
DISTRIBUTE_GROUP_DOC   = NO
SUBGROUPING            = YES
INLINE_GROUPED_CLASSES = YES
INLINE_SIMPLE_STRUCTS  = YES
TYPEDEF_HIDES_STRUCT   = YES
LOOKUP_CACHE_SIZE      = 0
#---------------------------------------------------------------------------
# Build related configuration options
#---------------------------------------------------------------------------
EXTRACT_ALL            = YES
EXTRACT_PRIVATE        = YES
EXTRACT_PACKAGE        = YES
EXTRACT_STATIC         = YES
EXTRACT_LOCAL_CLASSES  = YES
EXTRACT_LOCAL_METHODS  = YES
EXTRACT_ANON_NSPACES   = YES
HIDE_UNDOC_MEMBERS     = NO
HIDE_UNDOC_CLASSES     = NO
HIDE_FRIEND_COMPOUNDS  = NO
HIDE_IN_BODY_DOCS      = NO
INTERNAL_DOCS          = YES
CASE_SENSE_NAMES       = YES
HIDE_SCOPE_NAMES       = NO
HIDE_COMPOUND_REFERENCE= NO
SHOW_INCLUDE_FILES     = YES
SHOW_GROUPED_MEMB_INC  = NO
FORCE_LOCAL_INCLUDES   = YES
INLINE_INFO            = YES
SORT_MEMBER_DOCS       = YES
SORT_BRIEF_DOCS        = NO
SORT_MEMBERS_CTORS_1ST = NO
SORT_GROUP_NAMES       = NO
SORT_BY_SCOPE_NAME     = NO
STRICT_PROTO_MATCHING  = NO
GENERATE_TODOLIST      = YES
GENERATE_TESTLIST      = YES
GENERATE_BUGLIST       = YES
GENERATE_DEPRECATEDLIST= YES
ENABLED_SECTIONS       = 
MAX_INITIALIZER_LINES  = 30
SHOW_USED_FILES        = YES
SHOW_FILES             = YES
SHOW_NAMESPACES        = YES
FILE_VERSION_FILTER    = 
LAYOUT_FILE            = 
CITE_BIB_FILES         = 
#---------------------------------------------------------------------------
# Configuration options related to warning and progress messages
#---------------------------------------------------------------------------
QUIET                  = NO
WARNINGS               = YES
WARN_IF_UNDOCUMENTED   = YES
WARN_IF_DOC_ERROR      = YES
WARN_NO_PARAMDOC       = NO
WARN_FORMAT            = "$file:$line: $text"
WARN_LOGFILE           = 
#---------------------------------------------------------------------------
# Configuration options related to the input files
#---------------------------------------------------------------------------
INPUT                  = 
INPUT_ENCODING         = UTF-8
FILE_PATTERNS          = *.c \
                         *.cc \
                         *.cxx \
                         *.cpp \
                         *.c++ \
                         *.java \
                         *.ii \
                         *.ixx \
                         *.ipp \
                         *.i++ \
                         *.inl \
                         *.idl \
                         *.ddl \
                         *.odl \
                         *.h \
                         *.hh \
                         *.hxx \
                         *.hpp \
                         *.h++ \
                         *.cs \
                         *.d \
                         *.php \
                         *.php4 \
                         *.php5 \
                         *.phtml \
                         *.inc \
                         *.m \
                         *.markdown \
                         *.md \
                         *.mm \
                         *.dox \
                         *.py \
                         *.f90 \
                         *.f \
                         *.for \
                         *.tcl \
                         *.vhd \
                         *.vhdl \
                         *.ucf \
                         *.qsf \
                         *.as \
                         *.js
RECURSIVE              = YES
EXCLUDE                = 
EXCLUDE_SYMLINKS       = NO
EXCLUDE_PATTERNS       = 
EXCLUDE_SYMBOLS        = 
EXAMPLE_PATH           = 
EXAMPLE_PATTERNS       = *
EXAMPLE_RECURSIVE      = NO
IMAGE_PATH             = 
INPUT_FILTER           = 
FILTER_PATTERNS        = 
FILTER_SOURCE_FILES    = NO
FILTER_SOURCE_PATTERNS = 
USE_MDFILE_AS_MAINPAGE = 
#---------------------------------------------------------------------------
# Configuration options related to source browsing
#---------------------------------------------------------------------------
SOURCE_BROWSER         = YES
INLINE_SOURCES         = YES
STRIP_CODE_COMMENTS    = YES
REFERENCED_BY_RELATION = YES
REFERENCES_RELATION    = YES
REFERENCES_LINK_SOURCE = YES
SOURCE_TOOLTIPS        = YES
USE_HTAGS              = NO
VERBATIM_HEADERS       = YES
#---------------------------------------------------------------------------
# Configuration options related to the alphabetical class index
#---------------------------------------------------------------------------
ALPHABETICAL_INDEX     = YES
COLS_IN_ALPHA_INDEX    = 5
IGNORE_PREFIX          = 
#---------------------------------------------------------------------------
# Configuration options related to the HTML output
#---------------------------------------------------------------------------
GENERATE_HTML          = YES
HTML_OUTPUT            = html
HTML_FILE_EXTENSION    = .html
HTML_HEADER            = 
HTML_FOOTER            = 
HTML_STYLESHEET        = 
HTML_EXTRA_STYLESHEET  = 
HTML_EXTRA_FILES       = 
HTML_COLORSTYLE_HUE    = 220
HTML_COLORSTYLE_SAT    = 100
HTML_COLORSTYLE_GAMMA  = 80
HTML_TIMESTAMP         = YES
HTML_DYNAMIC_SECTIONS  = NO
HTML_INDEX_NUM_ENTRIES = 100
GENERATE_DOCSET        = NO
DOCSET_FEEDNAME        = "Doxygen generated docs"
DOCSET_BUNDLE_ID       = org.doxygen.Project
DOCSET_PUBLISHER_ID    = org.doxygen.Publisher
DOCSET_PUBLISHER_NAME  = Publisher
GENERATE_HTMLHELP      = NO
CHM_FILE               = 
HHC_LOCATION           = 
GENERATE_CHI           = NO
CHM_INDEX_ENCODING     = 
BINARY_TOC             = NO
TOC_EXPAND             = NO
GENERATE_QHP           = NO
QCH_FILE               = 
QHP_NAMESPACE          = org.doxygen.Project
QHP_VIRTUAL_FOLDER     = doc
QHP_CUST_FILTER_NAME   = 
QHP_CUST_FILTER_ATTRS  = 
QHP_SECT_FILTER_ATTRS  = 
QHG_LOCATION           = 
GENERATE_ECLIPSEHELP   = NO
ECLIPSE_DOC_ID         = org.doxygen.Project
DISABLE_INDEX          = NO
GENERATE_TREEVIEW      = NO
ENUM_VALUES_PER_LINE   = 4
TREEVIEW_WIDTH         = 250
EXT_LINKS_IN_WINDOW    = NO
FORMULA_FONTSIZE       = 10
FORMULA_TRANSPARENT    = YES
USE_MATHJAX            = NO
MATHJAX_FORMAT         = HTML-CSS
MATHJAX_RELPATH        = http://cdn.mathjax.org/mathjax/latest
MATHJAX_EXTENSIONS     = 
MATHJAX_CODEFILE       = 
SEARCHENGINE           = YES
SERVER_BASED_SEARCH    = NO
EXTERNAL_SEARCH        = NO
SEARCHENGINE_URL       = 
SEARCHDATA_FILE        = searchdata.xml
EXTERNAL_SEARCH_ID     = 
EXTRA_SEARCH_MAPPINGS  = 
#---------------------------------------------------------------------------
# Configuration options related to the LaTeX output
#---------------------------------------------------------------------------
GENERATE_LATEX         = NO
LATEX_OUTPUT           = latex
LATEX_CMD_NAME         = latex
MAKEINDEX_CMD_NAME     = makeindex
COMPACT_LATEX          = NO
PAPER_TYPE             = a4
EXTRA_PACKAGES         = 
LATEX_HEADER           = 
LATEX_FOOTER           = 
LATEX_EXTRA_STYLESHEET = 
LATEX_EXTRA_FILES      = 
PDF_HYPERLINKS         = YES
USE_PDFLATEX           = YES
LATEX_BATCHMODE        = NO
LATEX_HIDE_INDICES     = NO
LATEX_SOURCE_CODE      = NO
LATEX_BIB_STYLE        = plain
#---------------------------------------------------------------------------
# Configuration options related to the RTF output
#---------------------------------------------------------------------------
GENERATE_RTF           = NO
RTF_OUTPUT             = rtf
COMPACT_RTF            = NO
RTF_HYPERLINKS         = NO
RTF_STYLESHEET_FILE    = 
RTF_EXTENSIONS_FILE    = 
RTF_SOURCE_CODE        = NO
#---------------------------------------------------------------------------
# Configuration options related to the man page output
#---------------------------------------------------------------------------
GENERATE_MAN           = NO
MAN_OUTPUT             = man
MAN_EXTENSION          = .3
MAN_SUBDIR             = 
MAN_LINKS              = NO
#---------------------------------------------------------------------------
# Configuration options related to the XML output
#---------------------------------------------------------------------------
GENERATE_XML           = YES
XML_OUTPUT             = xml
XML_PROGRAMLISTING     = YES
#---------------------------------------------------------------------------
# Configuration options related to the DOCBOOK output
#---------------------------------------------------------------------------
GENERATE_DOCBOOK       = NO
DOCBOOK_OUTPUT         = docbook
DOCBOOK_PROGRAMLISTING = NO
#---------------------------------------------------------------------------
# Configuration options for the AutoGen Definitions output
#---------------------------------------------------------------------------
GENERATE_AUTOGEN_DEF   = NO
#---------------------------------------------------------------------------
# Configuration options related to the Perl module output
#---------------------------------------------------------------------------
GENERATE_PERLMOD       = NO
PERLMOD_LATEX          = NO
PERLMOD_PRETTY         = YES
PERLMOD_MAKEVAR_PREFIX = 
#---------------------------------------------------------------------------
# Configuration options related to the preprocessor
#---------------------------------------------------------------------------
ENABLE_PREPROCESSING   = YES
MACRO_EXPANSION        = NO
EXPAND_ONLY_PREDEF     = NO
SEARCH_INCLUDES        = YES
INCLUDE_PATH           = 
INCLUDE_FILE_PATTERNS  = 
PREDEFINED             = 
EXPAND_AS_DEFINED      = 
SKIP_FUNCTION_MACROS   = YES
#---------------------------------------------------------------------------
# Configuration options related to external references
#---------------------------------------------------------------------------
TAGFILES               = 
GENERATE_TAGFILE       = 
ALLEXTERNALS           = NO
EXTERNAL_GROUPS        = YES
EXTERNAL_PAGES         = YES
PERL_PATH              = /usr/bin/perl
#---------------------------------------------------------------------------
# Configuration options related to the dot tool
#---------------------------------------------------------------------------
CLASS_DIAGRAMS         = YES
MSCGEN_PATH            = 
DIA_PATH               = 
HIDE_UNDOC_RELATIONS   = YES
HAVE_DOT               = NO
DOT_NUM_THREADS        = 0
DOT_FONTNAME           = Helvetica
DOT_FONTSIZE           = 10
DOT_FONTPATH           = 
CLASS_GRAPH            = YES
COLLABORATION_GRAPH    = YES
GROUP_GRAPHS           = YES
UML_LOOK               = NO
UML_LIMIT_NUM_FIELDS   = 10
TEMPLATE_RELATIONS     = NO
INCLUDE_GRAPH          = YES
INCLUDED_BY_GRAPH      = YES
CALL_GRAPH             = NO
CALLER_GRAPH           = NO
GRAPHICAL_HIERARCHY    = YES
DIRECTORY_GRAPH        = YES
DOT_IMAGE_FORMAT       = png
INTERACTIVE_SVG        = NO
DOT_PATH               = 
DOTFILE_DIRS           = 
MSCFILE_DIRS           = 
DIAFILE_DIRS           = 
PLANTUML_JAR_PATH      = 
PLANTUML_INCLUDE_PATH  = 
DOT_GRAPH_MAX_NODES    = 50
MAX_DOT_GRAPH_DEPTH    = 0
DOT_TRANSPARENT        = NO
DOT_MULTI_TARGETS      = NO
GENERATE_LEGEND        = YES
DOT_CLEANUP            = YES
----------------------------------------------------------------

I hope someone could help me out.



--
View this message in context: http://doxygen.10944.n7.nabble.com/issue-with-java-element-name-tp6996.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] Issues with tag files

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

Hi Karl,

Sounds like an unwanted site effect of the recent restructuring of the tag file generation.

Can you file a bug report for each of the issues here:
https://bugzilla.gnome.org/enter_bug.cgi?product=doxygen
Please include a minimal self-contained example that allows me to 
reproduce the issue.

Regards,
  Dimitri

> On 22 Jan 2015, at 6:19 , Karl Wette <kar...@gm...> wrote:
> 
> Hi,
> 
> I am seeing two issues with tagfiles after upgrading from Doxygen
> v1.8.6 to v1.8.9.1. I'm not sure whether they are bugs or deliberate
> changes in behaviour, but they are causing problems for the libraries
> I document so I need to work around them. Apologies if they are
> already known, but I've  been unable to find any reference to them in
> bugzilla or in the mailing list archives.
> 
> 1st issue: in v.1.8.6 tagfiles included only documentation anchors
> from the code being documented, whereas v1.8.9.1 also includes anchors
> from any tagfiles included via TAGFILES. This causes problems with
> complicated library dependencies: if libraries B and C depend on
> library A, and library D depends on B and C, the documentation of D
> will get two copies of the anchors in library A (via the tagfiles of B
> and C) and Doxygen will generate a lot of warnings.
> 
> 2nd issue: in v1.8.6 tagfiles included anchors for enumeration values
> (<enumvalue> elements), but in v1.8.9.1 there are generated only if
> the enum is "strong", i.e. declared as either "enum struct" or "enum
> class". While this might be fine for C++11 code it's not helpful for
> plain C which is the language of the libraries I document.
> 
> Any help would be very much appreciated. Please let me know if further
> details are required.
> 
> Regards,
> Karl Wette
> 
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] char_varying type in VOS C and doxygen

[Uwe S. <u.s...@gm...>]

Hi,

I have a new issue to solve with doxygen: In VOS C there exists the type 
char_varying(n), where n is the number of characters of the variable. 
Basically, this type is nearly the same as a char array, but there exist
some differences, especially regarding assignments[*].

A typical variable declaration looks like this:
char_varying(10) foo;

and a definition looks like this:
char_varying(10) foo = "string";

where "10" is just an arbitrary choice for this example.

Imagine this file is given:
----------------------
/** @file foo.c
 */
char_varying(256) var;
main(){}
----------------------(1)

Doxygen assumes that char_varying is a function here, but as said above, 
this is just the type, and var is the variable. The doxygen html output 
in this case is just:
----------------------
foo.c File Reference
Functions
 	char_varying (256)
----------------------(2)

Is there any possibility to solve this somehow?

What I tried already: 

MACRO_EXPANSION = YES
EXPAND_ONLY_PREDEF = YES
PREDEFINED = char_varying()=

This leads to the following html output:
----------------------
foo.c File Reference
Functions
 	main ()
 
Variables
 	var
----------------------(3)
 	
This is much better, but the type of "var" is missing now. What I would 
like to see here is:
----------------------
foo.c File Reference
Functions
 	main ()

Variables
 	char_varying(256) var
----------------------(4)

It would be great if someone can help me out here.

Best wishes
Uwe

[*] Following the link below, you can find the char_varying documentation 
    from Stratus
http://stratadoc.stratus.com/vos/15.1.1/r040-02/wwhelp/wwhimpl/js/html/wwhelp.htm?context=r040-02&file=ch4r040-02ae.html

[Doxygen-users] Issues with tag files

[Karl W. <kar...@gm...>]

Hi,

I am seeing two issues with tagfiles after upgrading from Doxygen
v1.8.6 to v1.8.9.1. I'm not sure whether they are bugs or deliberate
changes in behaviour, but they are causing problems for the libraries
I document so I need to work around them. Apologies if they are
already known, but I've  been unable to find any reference to them in
bugzilla or in the mailing list archives.

1st issue: in v.1.8.6 tagfiles included only documentation anchors
from the code being documented, whereas v1.8.9.1 also includes anchors
from any tagfiles included via TAGFILES. This causes problems with
complicated library dependencies: if libraries B and C depend on
library A, and library D depends on B and C, the documentation of D
will get two copies of the anchors in library A (via the tagfiles of B
and C) and Doxygen will generate a lot of warnings.

2nd issue: in v1.8.6 tagfiles included anchors for enumeration values
(<enumvalue> elements), but in v1.8.9.1 there are generated only if
the enum is "strong", i.e. declared as either "enum struct" or "enum
class". While this might be fine for C++11 code it's not helpful for
plain C which is the language of the libraries I document.

Any help would be very much appreciated. Please let me know if further
details are required.

Regards,
Karl Wette

Re: [Doxygen-users] doxygen-1.8.9.1 upgrade errors

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

Peter,

Your report contains a number of points:
- Joining tags when using +=, this is by design. The parser used to do the
reading for an update of the Doxyfile is the same as the parser reading the
Doxyfile when processing sources files. The parser joins all the items
belonging to one tag (e.g. the ALIASES tag), when writing out the new
Doxyfile it is not known if += have been used. Similar things happens with
include files (they are merged into Doxyfile upon update).
- Only showing the last user comment in case of using a += tag construct.
I've pushed a proposed patch to github (pull request 293)
- Moving user comments at the beginning of the file to the first tag. This
is conform the documentation, I've corrected this, so that this is
preserved now in the before mentioned proposed patch.

Albert

On Tue, Jan 20, 2015 at 10:58 PM, Barnes, Peter D. <bar...@ll...>
wrote:

> Hello Folks,
>
> I upgraded by doxygen to 1.8.9.1 from the sources.  (Mac 10.8.5, gcc
> 4.2.1).
>
> Then I protected some of my comments in our doxygen.conf using '##', for
> example:
>
> > ## -*- sh -*-
> >
> > ...
> >
>
> > ALIASES                =
> >
> > ## Link to bug tracker
> > ALIASES               += bugid{1}="<a href=\"
> http://www.nsnam.org/bugzilla/show_bug.cgi?id=\1\">Bug \1</a>"
> >
> > ## Set off \internal docs
> > ALIASES               += internal="\par \b Internal:"
> >
> > ## Typeset parameter name in docs as in the "Parameters:" list
> > ## Usage:     /** \param [in/out] tag If found, \pname{tag} is ... */
> > ALIASES               += pname{1}="<span class=\"params\"><span
> class=\"paramname\">\1</span></span>"
> >
> > ## Link to RFC's
> > ALIASES               += RFC{1}="<a href=\"
> http://datatracker.ietf.org/doc/rfc\1/\">RFC \1</a>"
>
> Finally I asked doxygen to update the config file:
>
> $ doxygen -u doxygen.conf
>
> However it modified the two regions above in undesirable ways:
>
> - The emacs mode line got moved after the doxygen opening comments.  It
> has to be on the first line for emacs to recognize it.
>
> - The aliases got bunched into a single block, and only the last comment
> was preserved:
>
> > ## Link to RFC's
> >
> > ALIASES                = "bugid{1}=<a href=\"
> http://www.nsnam.org/bugzilla/show_bug.cgi?id=\1\">Bug \1</a>" \
> >                          "internal=\par \b Internal:" \
> >                          "pname{1}=<span class=\"params\"><span
> class=\"paramname\">\1</span></span>" \
> >                          "RFC{1}=<a href=\"
> http://datatracker.ietf.org/doc/rfc\1/\">RFC \1</a>"
>
>
> Thanks,
> Peter
> _______________________________________________________________________
> Dr. Peter D. Barnes, Jr.                Physics Division
> Lawrence Livermore National Laboratory  Physical and Life Sciences
> 7000 East Avenue, L-50                  email:  pdb...@ll...
> P. O. Box 808                           Voice:  (925) 422-3384
> Livermore, California 94550             Fax:    (925) 423-3371
>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>

[Doxygen-users] doxygen-1.8.6 on CentOS 6 problem with INPUT_ENCODING

[Tomaz H. <Tom...@ba...>]

Hi All,

We are migrating the source code of an internal app and doxygen-1.8.6 from a windows server to CentOS
6.6. On the windows server everything works as expected.

I migrated the source files, altered the doxygen configs accordingly
and installed the linux static build of doxygen-1.8.6 from:

    ftp://ftp.stack.nl/pub/users/dimitri/doxygen-1.8.6.linux.bin.tar.gz

However, when I run doxygen on the CentOS server it does not recognize the
encodings in the INPUT_ENCODING parameter:

   $ export GCONV_PATH=/usr/lib/gconv
   $ /opt/doxygen-1.8.6/bin/doxygen conf/Doxyfile
   ... (output clipped)
   Reading and parsing tag files
   Parsing files
   Preprocessing /home/doxy/conf/Mainpage.dox...
   error: unsupported character conversion: 'CP1250'->'UTF-8': Invalid argument
   Check the INPUT_ENCODING setting in the config file!
   Exiting...

No matter what encoding is being set in INPUT_ENCODING it produces the same
error. Except if set it to UTF-8!

I checked if doxygen can read the glibc iconv settings (glibc-2.12 is installed), and everything seems
ok: it finds and reads the gconv settings, loads to CP1250.so when trying to
convert the first file but then suddenly bails out:

    $ export GCONV_PATH=/usr/lib/gconv
    $ strace /opt/doxygen-1.8.6/bin/doxygen conf/Doxyfile
    ...
    getcwd("/home/doxy/src", 4096) = 46
    open("/usr/lib/gconv/gconv-modules", O_RDONLY|O_CLOEXEC) = 3
    fstat(3, {st_mode=S_IFREG|0644, st_size=56103, ...}) = 0
    mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f81dabaf000
    read(3, "# GNU libc iconv configuration.\n"..., 4096) = 4096
    read(3, "B1.002//\nalias\tJS//\t\t\tJUS_I.B1.0"..., 4096) = 4096
    read(3, "59-3\t1\nmodule\tINTERNAL\t\tISO-8859"..., 4096) = 4096
    read(3, "859-14//\nalias\tISO-IR-199//\t\tISO"..., 4096) = 4096
    read(3, "CDIC-DK-NO-A//\tEBCDIC-DK-NO-A\t1\n"..., 4096) = 4096
    read(3, "\t\tIBM281//\t\tIBM281\t\t1\n\n#\tfrom\t\t\t"..., 4096) = 4096
    read(3, "\tIBM863\t\t1\n\n#\tfrom\t\t\tto\t\t\tmodule"..., 4096) = 4096
    read(3, "//\t\tIBM937//\nalias\tCSIBM937//\t\tI"..., 4096) = 4096
    read(3, "JAPANESE//\tEUC-JP//\nalias\tOSF000"..., 4096) = 4096
    read(3, "MACINTOSH//\t\tMACINTOSH\t1\n\n#\tfrom"..., 4096) = 4096
    read(3, "367-BOX//\nalias\tISO_10367BOX//\t\t"..., 4096) = 4096
    brk(0x2bbd000)                          = 0x2bbd000
    read(3, "EUC-JISX0213//\t\tINTERNAL\t\tEUC-JI"..., 4096) = 4096
    read(3, "/\t\tIBM1130//\nalias\tCSIBM1130//\t\t"..., 4096) = 4096
    read(3, "\t1\n\n#\tfrom\t\t\tto\t\t\tmodule\t\tcost\na"..., 4096) = 2855
    read(3, "", 4096)                       = 0
    close(3)                                = 0
    munmap(0x7f81dabaf000, 4096)            = 0
    open("/usr/lib/x86_64-linux-gnu/gconv/gconv-modules", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
    ...
    lstat("/home/doxy/conf/Mainpage.dox", {st_mode=S_IFREG|0640, st_size=56981, ...}) = 0
    access("/home/doxy/conf/Mainpage.dox", F_OK) = 0
    open("/home/doxy/conf/Mainpage.dox", O_RDONLY) = 5
    fstat(5, {st_mode=S_IFREG|0640, st_size=56981, ...}) = 0
    lstat("/home/doxy/conf/Mainpage.dox", {st_mode=S_IFREG|0640, st_size=56981, ...}) = 0
    fstat(5, {st_mode=S_IFREG|0640, st_size=56981, ...}) = 0
    mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f81daa66000
    read(5, "/*! \\mainpage\n\n  \\subpage toc_db"..., 53248) = 53248
    read(5, " pg_CMS_XPROD_ECM_DATA_PACKAGE_S"..., 4096) = 3733
    close(5)                                = 0
    munmap(0x7f81daa66000, 4096)            = 0
    open("/usr/lib/gconv/CP1250.so", O_RDONLY|O_CLOEXEC) = 5
    read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P\3\0\0004\0\0\0"..., 832) = 832
    close(5)                                = 0
    ...
    write(2, "error: unsupported character con"..., 130error: unsupported character conversion: 'CP1250'->'UTF-8': Invalid argument
    Check the INPUT_ENCODING setting in the config file!
    ) = 130
    ...

It looks like the list of available encodings is not being read correctly from
gconv? 

Kind regards,
Tomaz

==========================================================================================
To elektronsko sporočilo in vse morebitne priloge so poslovna skrivnost in namenjene izključno naslovniku. Če ste sporočilo prejeli pomotoma, Vas prosimo, da obvestite pošiljatelja, sporočilo pa takoj uničite. Kakršnokoli razkritje, distribucija ali kopiranje vsebine sporočila je izrecno prepovedano. Ni nujno, da to sporočilo odraža uradno stališče družbe.
Elektronsko sporočilo je pregledano z antivirusnim programom.

This e-mail and any attachments may contain confidential and/or privileged information and is intended solely for the addressee. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. This e-mail may not necessarily reflect the official viewpoint of the company.
E-mail message is scanned by Anti-Virus Software.

[Doxygen-users] doxygen-1.8.9.1 upgrade errors

[Barnes, P. D. <bar...@ll...>]

Hello Folks,

I upgraded by doxygen to 1.8.9.1 from the sources.  (Mac 10.8.5, gcc 4.2.1).

Then I protected some of my comments in our doxygen.conf using '##', for example:

> ## -*- sh -*-
> 
> ...
> 

> ALIASES                = 
> 
> ## Link to bug tracker
> ALIASES               += bugid{1}="<a href=\"http://www.nsnam.org/bugzilla/show_bug.cgi?id=\1\">Bug \1</a>"
> 
> ## Set off \internal docs
> ALIASES               += internal="\par \b Internal:"
> 
> ## Typeset parameter name in docs as in the "Parameters:" list
> ## Usage:     /** \param [in/out] tag If found, \pname{tag} is ... */
> ALIASES               += pname{1}="<span class=\"params\"><span class=\"paramname\">\1</span></span>"
> 
> ## Link to RFC's
> ALIASES               += RFC{1}="<a href=\"http://datatracker.ietf.org/doc/rfc\1/\">RFC \1</a>"

Finally I asked doxygen to update the config file:

$ doxygen -u doxygen.conf

However it modified the two regions above in undesirable ways:

- The emacs mode line got moved after the doxygen opening comments.  It has to be on the first line for emacs to recognize it.

- The aliases got bunched into a single block, and only the last comment was preserved:

> ## Link to RFC's
> 
> ALIASES                = "bugid{1}=<a href=\"http://www.nsnam.org/bugzilla/show_bug.cgi?id=\1\">Bug \1</a>" \
>                          "internal=\par \b Internal:" \
>                          "pname{1}=<span class=\"params\"><span class=\"paramname\">\1</span></span>" \
>                          "RFC{1}=<a href=\"http://datatracker.ietf.org/doc/rfc\1/\">RFC \1</a>"


Thanks,
Peter
_______________________________________________________________________
Dr. Peter D. Barnes, Jr.                Physics Division
Lawrence Livermore National Laboratory  Physical and Life Sciences
7000 East Avenue, L-50                  email:  pdb...@ll...
P. O. Box 808                           Voice:  (925) 422-3384
Livermore, California 94550             Fax:    (925) 423-3371

[Doxygen-users] Suppressing "More..." in brief descriptions

[Moshe K. <MO...@il...>]

Is it possible to suppress the "More..." at the end of brief descriptions?
I don't mean removing the brief descriptions. Also, I would like to keep 
the link to the longer descriptions below.
Only, I think "More..." is somewhat outdated and I would like to remove 
it.
Is there any way to do that?

Moshe Kruger | Information Developer
IBM Worklight | Tel +972-952-5658 | M +972-52-7707387