doxygen-develop — List for discussing new features, submitting patches, etc.

[Doxygen-develop] [Fwd: Re: CVS still not updated: copy script running?]

[Kevin M. <ke...@pl...>]

I am forwarding this e-mail to the public doxygen-develop mailing list
due to the fact that my e-mail server appears to other servers as being
on a dynamic IP.

- KJM

-------- Original Message --------
Subject: Re: CVS still not updated: copy script running?
Date: Fri, 27 Jul 2007 07:52:04 -0400
From: Kevin McBride <ke...@pl...>
To: Dimitri van Heesch <di...@st...>,  Pri...@sk...
References: <200...@st...>

Dimitri van Heesch wrote:
> Hi Kevin,
> 
> Seems that the CVS commit I did does not get copied to the public 
> repository.
> 
> Can you have a look?

I wanted the process to start up at midnight of my time (EST), which
apparently didn't happen because I forgot to launch it before going to
work.  The crond on the system won't run, so I keep a small C program
running on tty1 to handle the copy and backup tasks.  I am going to
write a time check in that program so that I can start the process
anytime, without having to worry about forgetting to launch the process
before going to work.

I am also going to look into replacing the hardware and rebuilding the
operating system, as the system seems to need a reboot every two weeks.
  According to the logs, most of these problems requiring a reboot are
being caused by DVD drives.  My latest DVD drive in the system is
starting to fail after only six months of usage.  A few problems could
be problems with the Linux drivers, or IDE hardware issues.  In any
case, I think my first approach would be to allocate time on my schedule
to rebuild the operating system.  I am still running Fedora Core 3, with
some software compiled directly from source.  I am quite hesitant to
upgrade because, for instance, when I attempted to upgrade to Fedora
Core 4 at one time, my tty's became useless.  I did come across an old
8GB hard drive I can use to test Fedora Core 7, before I use the new
operating system to run the CVS live.

Dimitri, since I will be going through upgrades, do you think we're
ready to start using Subversion in place of CVS after the operating
system rebuild on cvs.planetsaphire.com?

I will let you all know when I will be taking the server down for the OS
rebuild and hardware upgrades.

> 
> ----- Forwarded message from Petr Prikryl <Pri...@sk...> -----
> 
> From: Petr Prikryl <Pri...@sk...> To: Dimitri van Heesch 
> <di...@st...>
> 
> Hi Dimitri,
> 
> For your information. The configure file in CVS still contains the 
> old version.
> 
> Regards, Petr
> 
> ----- End forwarded message -----
> 

- KJM

[Doxygen-develop] new release of moritz the nassi-shneiderman generator for doxygen is available

[<Eck...@t-...>]

Hello Everybody.

Since yesterday a new release of moritz the nassi-shneiderman generator 
for doxygen is available under https://sourceforge.net/projects/moritz/.

Due to a bug-report (thanks to Mr. M.-A. Hohm) the analysis of 
compiler-switches is improved. Moritz is able to generate for every 
variant of a function a single diagram-script. This process will be 
controlled by the default-configuration and special-commands in the source.

Please try it out and use the forum on the sourceforge-side of moritz to 
ask question or to post comments.

If you have questions or suggestions please don't hesitate to post them 
in the forum under: https://sourceforge.net/forum/?group_id=167738 
<https://sourceforge.net/projects/moritz/>

Kind Regards,
                        Eckard Klotz

PS: Dear Mr. van Haesch.

What are the next steps for me to do, to make it possible that moritz 
will be mentioned as official helper-tool on the doxygen-side?

Kind Regards,
                        Eckard Klotz

[Doxygen-develop] XML output

[Alexandre R. <ale...@bl...>]

Hi,

=20

I'm planning on parsing the XML output with xsl but I didn't found any
documentation on what tag does what.

=20

I guess some (like  <emphasys> =3D italic) but I was wandering if there =
is
any documentation on this.

=20

Thanks

Alexandre Roy

Re: [Doxygen-develop] Bounds error in util.cpp

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

Hi Alexander,

I guess you meant this part:

    if ((csp==0 && (i==0 || !isId(constScope[i-1])) || (csp>0 && csp<6)) &&
        c==constScope[csp]
       ) csp++; else csp=0;

After a closer look it turns out to be wrong indeed. This was what was
intended:

    if (csp<6 && c==constScope[csp] && // character matches substring
"const"
         (csp>0 ||                     // if it is the first character
          i==0  ||                     // the previous may not be a digit
          !isId(s.at(i-1))
         )
       )
      csp++;
    else // reset counter
      csp=0;

Thanks for reporting this, I'll fix it in the next CVS update.
If you find more of these please report them.
Seems like a very useful tool you are working on ;-)

Regards,
   Dimitri


On 6/9/07, Alexander Lamaison <aw...@do...> wrote:
>
>  Hello,
>
>
>
> I have been developing a bounds-checker for C++.  I tested it using
> Doxygen and it finds a bounds error in util.cpp on line 1427 when running
> the define example.
>
>
>
> I went through the code by hand and it does, indeed, seem that the use of
> 'constScope[]' in '!isId(constScope[i-1])' can go out-of-bounds if the
> string passed in as parameter 's' is longer than 6 and, I assume, similarly
> with 'virtualScope[]' on line 1430.
>
>
>
> I realise that this is a very minor bounds error but I'm very curious
> whether this behaviour is intended.
>
>
>
> Alex Lamaison
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop
>
>

[Doxygen-develop] Add-on for Actionscript 2.0

[Alexandre R. <ale...@bl...>]

I add the Actionscript 2.0 parsing and I was wandering where I submit my
code

=20

Thanks

Alex

=20

P.S. If I was not suppose to send via this list -> sorry for the spam!

[Doxygen-develop] helpstring

[Tomasz G. <to...@gr...>]

Suppose we define a class in IDL (MS flavour):
[
  coclass,
  helpstring("This is MyClass that does MyThings"),
  uuid(12EA4908-7233-1E52-056A-00E04F17BCFE)
]
class MyClass
{
  ...
};

Can doxygen include helpstring attribute content in class documentation? Same 
applies to methods/interfaces/properties/etc. If it is not currently possible 
would such a functionality be hard to add? Does doxygen parse such constructs 
and it would only be a matter of adding it to output or is it a more 
complicated task? TIA,
-- 
Regards,
Tomasz Grobelny

[Doxygen-develop] Bounds error in util.cpp

[Alexander L. <aw...@do...>]

Hello,

 

I have been developing a bounds-checker for C++.  I tested it using Doxygen
and it finds a bounds error in util.cpp on line 1427 when running the define
example.  

 

I went through the code by hand and it does, indeed, seem that the use of
'constScope[]' in '!isId(constScope[i-1])' can go out-of-bounds if the
string passed in as parameter 's' is longer than 6 and, I assume, similarly
with 'virtualScope[]' on line 1430.

 

I realise that this is a very minor bounds error but I'm very curious
whether this behaviour is intended.

 

Alex Lamaison

 

[Doxygen-develop] [doxygen] updated translate file for cn

[LI D. <lid...@gm...>]

Hello,

an updated  chinese translatation file for doxygen in attachment.

translate "Namespaces" to chinese

thanks

-- 
LI Daobing

[Doxygen-develop] Generate UML XML?

[Bill Z. <bil...@gm...>]

I'm looking into the use of doxygen to generate an XML representation of
my team's public APIs (C and C++ only), specifically based on (a version
of) the UML DTD.

That way, in theory, I could use doxygen to generate a UML-ized library
of public APIs that I could then import into a UML modelling tool for
re-use in future designs.

If I had the right UML modelling tool, I might just be better off using
it to generate the UML components from the source, but I'd like to
explore whether I could do this with doxygen (or if it already exists),
since my team already uses doxygen to generate HTML documentation.

So, a few questions...

- firstly, obviously, does this capability already exist... i.e. the
  capability to use doxygen to generate UML XML output of my public
  classes & APIs?

- assuming this capability doesn't exist, I think I would have to write
  an app that generates UML XML from the XML that doxygen generates now,
  which makes me ask...

  - what schema does doxygen use by default when generating the
    intermediate XML files?

  - can someone explain the purpose of the XML_DTD config
    parameter... if I use this, does doxygen try to match the XML output
    to the schema defined in the DTD (I assume not)

Thanks, Bill...

Re: [Doxygen-develop] Patch: Aliases with Arguments (TODO #28)

[Iain B. <ia...@pc...>]

On Sun, 2007-05-20 at 11:44 +0200, Dimitri van Heesch wrote:
> 
> I'm working on official support for aliases with arguments at the
> moment. 

cool, thanks!

> To give you an idea about the syntax, here are some examples of
> aliases:

I found that example slightly confusing :) but I'll wait to play when
the "official" one is released.

thanks again,
-- 
Iain Buchanan <iain at pcorp dot com dot au>

You got to be very careful if you don't know where you're going,
because you might not get there.
		-- Yogi Berra

Re: [Doxygen-develop] [ATTN Dimitri] status of bug 418615?

[Matthew W. <mw_...@us...>]

Dimitri van Heesch wrote:
> On 5/16/07, Matthew Woehlke wrote:
>> A while back I submitted a patch to fix parsing of multiple style
>> commands (i.e. '\c \e foo bar', which should make 'foo' command and
>> emphasized, and leave 'bar' normal style). What ever happened with this?
>> Has it been fixed?
>>
>> old post: http://permalink.gmane.org/gmane.text.doxygen.devel/801
>
> It is still on my todo list.

Ok, thanks for the update.

> I have to understand your fix (or "ugly hack" as you call it) and it see
> what implications it has.

Ok, feel free to ask questions :-). IIRC the ugliness is mostly that 
deciding if the token should be eaten or not (so that the first of a 
nested directive pops correctly) wasn't straight-forward. Although I 
would argue that as long as single directives don't break, it's still an 
improvement. ;-)

> Since there is a workaround for the limitation, I do not 
> consider it of the highest priority.

Do you mean using html?

-- 
Matthew
When in doubt, duct tape!

Re: [Doxygen-develop] Patch: Aliases with Arguments (TODO #28)

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

On 5/10/07, Iain Buchanan <ia...@pc...> wrote:
>
> On Thu, 2007-05-10 at 17:38 +1000, Robbie Gates wrote:
> > > Did this patch ever get into the doxygen tree?  Is anyone using
> it?  I'm
> > > about to try it out, but I think I will have to patch the source
> > > still...
> >
> > As far as i can see from my copy of the sources (the 1.5.2 release) it
> > hasn't been - replaceAliases in commentcnv.l has the old QRegExp cmd
> > ctor argument, and the updated lex action looks like the old version.
>
> Hm, this is strange, since it is still on the TODO list.  I don't know
> how anyone can use aliases effectively without it!



I'm working on official support for aliases with arguments at the moment.

To give you an idea about the syntax, here are some examples of aliases:

ALIASES        = xreflist{3}="\xrefitem \1 \"\2\" \"\3\" " \
                 reminder="\xreflist{reminders,Reminder,Reminders}" \
                 l{1}="\ref \1" \
                 l{2}="\ref \1 \"\2\"" \
                 table{1}="<table border=0 cellspacing=2
cellpadding=0>\theader{\1}"  \
                 theader{1}="<tr><th bgcolor=\"FFFF00\" colspan=3>\1" \
                 row3{3}="<tr><td>\1 <td>\2 <td>\3 </tr>" \
                 endtable="</table>" \
                 Bold{1}="<b>\1</b>" \
                 Emph{1}="<em>\1</em>"

And some code using the aliases:

/** \reminder This needs to be renamed
 *  \reminder Also a redesign would be handy
 *  See \l{Base} or \l{Base,the other class}.
 *  A nice table:
 *  \table{Heading}
 *  \row3{ cell(1\,1) , cell(1\,2) , cell(1\,3) }
 *  \row3{ cell(2\,1) , cell(2\,2) , cell(2\,3) }
 *  \endtable
 *  \Bold{Some \Emph{text} here}
 */
class Test
{
};

/** Some class */
class Base
{
};



> Can you let me (via the list) know how you get on - i'm also
> > interested in this functionality.
>
> I'm actually getting an intern to do it ;) and so far he's patched 1.4.7
> successfully and made a test run ok.  1.5.x broke some latex features we
> were using, so I haven't bothered with that version yet.
>
> cya,
> --
> Iain Buchanan <iain at pcorp dot com dot au>
>
> Anyone who considers protocol unimportant has never dealt with a cat.
>                 -- R. Heinlein
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop
>

Re: [Doxygen-develop] [ATTN Dimitri] status of bug 418615?

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

It is still on my todo list.

I have to understand your fix (or "ugly hack" as you call it) and it see
what implications
it has. Since there is a workaround for the limitation, I do not consider it
of the highest priority.

Regards,
   Dimitri

On 5/16/07, Matthew Woehlke <mw_...@us...> wrote:
>
> A while back I submitted a patch to fix parsing of multiple style
> commands (i.e. '\c \e foo bar', which should make 'foo' command and
> emphasized, and leave 'bar' normal style). What ever happened with this?
> Has it been fixed?
>
> old post: http://permalink.gmane.org/gmane.text.doxygen.devel/801
> bug*: http://bugzilla.gnome.org/show_bug.cgi?id=418615
>
> (* at least, my old post claims that's a bug report of this; gnome.org
> seems to be down ATM.)
>
> --
> Matthew
> "Nobody expects the Spanish Inquisition!" -- Monty Python
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop
>

[Doxygen-develop] Possible bug in manpage creation: Minux signs are not escaped

[Daniel L. <dan...@gm...>]

Hello,

Consider e.g.
http://mpqc.cvs.sourceforge.net/*checkout*/mpqc/mpqc/bin/sc-config.dox
as example. The created manpages do not escape the hyphens, although
they should be (to my knowledge) and the Whatis entry is created
correctly:

> .SH NAME
> sc-config \- The sc-config program is used to obtain information about MPQC's compile time environment.

I would consider this a bug in doxygen. I didn't find an info, how to
get doxygen to escape the minus here.

Regards, Daniel

[Doxygen-develop] [ATTN Dimitri] status of bug 418615?

[Matthew W. <mw_...@us...>]

A while back I submitted a patch to fix parsing of multiple style 
commands (i.e. '\c \e foo bar', which should make 'foo' command and 
emphasized, and leave 'bar' normal style). What ever happened with this? 
Has it been fixed?

old post: http://permalink.gmane.org/gmane.text.doxygen.devel/801
bug*: http://bugzilla.gnome.org/show_bug.cgi?id=418615

(* at least, my old post claims that's a bug report of this; gnome.org 
seems to be down ATM.)

-- 
Matthew
"Nobody expects the Spanish Inquisition!" -- Monty Python

[Doxygen-develop] Feature request: #include<> vs. #include "" and prefixes

[Gennaro P. <gen...@ya...>]

Hi guys,

unless I'm missing something, it seems that the only way to have
doxygen indicate the relevant include file for a class in quoted form
is to explicitly specify the header-name with a \class command.
Similarly if all the includes require a common path prefix (e.g.
"boost/"). Would it be possible to add a couple of configuration
options for this, instead?

INCLUDE_FORMAT_IS_QUOTED = {yes|no}
INCLUDE_PATH_PREFIX      = <string>

I'm not familiar with the doxygen source code but if this requires too
much time, and there's interest, I can try and prepare a patch.

Thanks in advance!

-- 
Gennaro Prota
https://sourceforge.net/projects/breeze/

Re: [Doxygen-develop] Patch: Aliases with Arguments (TODO #28)

[Iain B. <ia...@pc...>]

On Thu, 2007-05-10 at 17:38 +1000, Robbie Gates wrote:
> > Did this patch ever get into the doxygen tree?  Is anyone using it?  I'm
> > about to try it out, but I think I will have to patch the source
> > still...
> 
> As far as i can see from my copy of the sources (the 1.5.2 release) it
> hasn't been - replaceAliases in commentcnv.l has the old QRegExp cmd
> ctor argument, and the updated lex action looks like the old version.

Hm, this is strange, since it is still on the TODO list.  I don't know
how anyone can use aliases effectively without it!

> Can you let me (via the list) know how you get on - i'm also
> interested in this functionality.

I'm actually getting an intern to do it ;) and so far he's patched 1.4.7
successfully and made a test run ok.  1.5.x broke some latex features we
were using, so I haven't bothered with that version yet.

cya,
-- 
Iain Buchanan <iain at pcorp dot com dot au>

Anyone who considers protocol unimportant has never dealt with a cat.
		-- R. Heinlein 

Re: [Doxygen-develop] Patch: Aliases with Arguments (TODO #28)

[Robbie G. <ro...@m8...>]

> Did this patch ever get into the doxygen tree?  Is anyone using it?  I'm
> about to try it out, but I think I will have to patch the source
> still...
As far as i can see from my copy of the sources (the 1.5.2 release) it
hasn't been - replaceAliases in commentcnv.l has the old QRegExp cmd
ctor argument, and the updated lex action looks like the old version.

Can you let me (via the list) know how you get on - i'm also
interested in this functionality.

 - robbie

Re: [Doxygen-develop] Patch: Aliases with Arguments (TODO #28)

[Iain B. <ia...@pc...>]

Did this patch ever get into the doxygen tree?  Is anyone using it?  I'm
about to try it out, but I think I will have to patch the source
still...

thanks!

On Fri, 2006-09-29 at 17:01 -0500, Dirk Reiners wrote:
>     Hi Y'all (I've been living in Louisiana too long ;),
> 
> I wrote a little patch to support arguments in aliases. It's very simple 
> and not very elegant, but it works fine.
> 
> Usage is trivial. In the aliases arguments need to be marked with 
> ^<number>^, like this:
>  
> ALIASES      = "al1=*AL1*" \
>                "al2=*AL2:^1^*" \
>                "al3=*AL3:^1^ -> ^2^*"
> 
> When using the alias the arguments are passed in parentheses after the 
> alias (like C macros) and separated by ',' (which can be escaped if 
> necessary):
> 
> Alias with one arg: \al2(ARG) will be "*AL2:ARG*"
> Alias with one arg and escaped ',': \al2(ARG\,BLARG) will be 
> "*AL2:ARG,BLARG*"
> Alias with two args: \al3(FOO,BAR) will be "*AL3:FOO -> BAR*"
> 
> If an alias is called without () no argument substitution is done, so 
> all existing documentation should work just fine.
> 
> Currently the maximum number of arguments is fixed at 20, which 
> hopefully is enough.
> 
> The path is against current CVS.
> 
> Hope you find it useful
>   
>     Dirk
> 
> 
> 
> plain text document attachment (aliasdiff)

-- 
Iain Buchanan <iain at pcorp dot com dot au>

Wilner's Observation:
	All conversations with a potato should be conducted in private.

[Doxygen-develop] Link generation in overview pages

[Jim B. <ji...@sh...>]

I found an entry asking roughly the same question in the help forum, but =
it=20
was several years old and unanswered.=20

When using Javadoc, you can specify the =E2=80=93overview tag to include =
a=20
project-wide overview section.  This is roughly equivalent to the Doxygen=20
technique of adding an @mainpage tag to a source file, followed by a tag=20
such as =E2=80=9C@htmlinclude overview.html=E2=80=9D.=20

I created a Java source file with a class named =E2=80=9CNew1=E2=80=9D, a=
nd created the=20
file overview.html with the following contents:=20

  <body>Brief overview. A link: {@link New1}</body>=20

When I run Javadoc against my source file and specify the -overview switc=
h=20
pointed to my overview.html file, a link is produced on the overview page=20
with the text string =E2=80=9CNew1=E2=80=9D which links to the documentat=
ion for class=20
New1.=20

When I run Doxygen, I get the text string =E2=80=9C{@link New1}=E2=80=9D =
in my output=20
and no link.=20

The first question: is there a better way to incorporate an overview page=20
that will cause the link tags to be evaluated into an actual links the wa=
y=20
Javadoc does?=20

Second question: In order to use the Javadoc overview feature you use a=20
command line option (no tags).  This means you can add an overview page t=
o a=20
project without editing source files to add special tags like=20
=E2=80=9C@mainpage=E2=80=9D.=20

Would you consider adding such a switch to Doxygen so that Doxygen can=20
produce the same overview pages as Javadoc without requiring a change to =
the=20
source files (adding one or more tags)?=20

Extra info:  We deliver Javadoc with our product, but are considering usi=
ng=20
Doxygen for internal use.  The hope is that initially, there will be no=20
source code changes required until we are able to get the effort moving.=20

Thanks!
Jim

[Doxygen-develop] Problem with 1.5.2

[Jason M. <ko...@gm...>]

Doxygen's only has up-to-date build tools for Visual Stuido 8.0. VS 7.1 
and 7.0 cannot read these files. And the VS 6.0 projects don't work 
without significant modification.

[Doxygen-develop] Entries, entry tree, comments

[Stefan <ja...@op...>]

Hello!

I'll be trying to extend doxygen to parse upcoming features of C++0x, 
namely concepts. I have a few questions.

1) What places should I look for to make the appropriate changes? I 
started to modify the scanner.l. I would like to make doxygen generate 
list of concepts in a file - where's the code that does for classes, 
functione, etc.?

2) What's the structure of the entry tree? Say I'm parsing a namespace:

namespace ns
{
     // a class
     // a concept
     // something else
}

When I'm parsing the concept what does the "current" variable point to? 
To the entry of the class? Should I make a new entry and make it a child 
of the class or a child of the namespace?

3) How do I handle comments that are put just before the concept? Do I 
have to write scanner rules for them, or are there some available 
already? Are there any functions concerning handling those comments that 
I should be aware of?

4) Concepts can be refined - it's pretty much an inheritance. Are there 
any function to build the inheritance diagram?


Thanks in advance,

Stefan Chrobot

[Doxygen-develop] Patches for doxygen

[Brendon C. <bc...@av...>]

Hi all,

I have been working on a project that interoperates with Doxygen to
produce accurate/complete documentation of C++ exception propagation.
Anyhow, in order to get my project to work I have had to make a few
patches to doxygen.

In particular the patches include:

-----------------
* Facility to match template types with "explicit" parameters for
defaults. For example:

void Function(std::vector<int>&);

can now be identified using:

void Function(std::vector<int,std::allocator<int> >&)

This works recursively and matches as best it can.


-----------------
* Merging of two sets of documentation for a single node.

For example:

/** \brief Brief 1.
 *
 * Detailed 1.
 */
void Function();

/** \fn Function1()
 * \brief Brief 2.
 *
 * Detailed 2.
 */

The patch will attempt to merge the two documentation blocks instead
of just ignoring the second. The resulting detailed section will include:

Detailed 1.
Detailed 2.

Where as the brief will only keep the first brief found. This is
because I could not think of a good way to merge two brief sections. I
may later choose to merge the second brief as a part of the detailed
section so it is not lots completely.


-----------------
* Updated processing of input source files to be processed in the
order they are declared in the doxygen configuration file instead of
alphabetical order.

   This was necessary because of the previous patch. I.e. the order of
processing was important to ensure that the "correct" brief
description was used for the documentation.


-----------------
* Type matches can now ignore a reference parameter to obtain a match.

   This is generally not a good idea. I can understand if this patch
is not accepted. I had to do it because of a limitation in my project.
The reasons for this are described below:

int BackFunction(std::string);
class C
{
   int Function(std::string s)
   {
      return BackFunction(s);
   }
};

The above code when compiled with GCC will be MODIFIED internally by
the compiler to look like:

int BackFunction(std::string);
class C
{
   int Function(std::string& s)
   {
      return BackFunction(s);
   }
};

Notice the & added after the std::string. My project uses GCC to
generate data files that are then processed and as such when it emits
the results, the function is emitted like:
int C::Function(std::string&)

which doxygen does not consider the same as:
int C::Function(std::string)

For good reason as it is NOT the same. Anyhow i needed to support this
(at least for now). I can understand if this would not be accepted
into doxygen as a result. I need to speak with the GCC devs more to
find out if there is a method of obtaining the actual declared name
for the above function that does not include the &.




Would the doxygen community be interested in accepting some or all of
these patches?

If so i will have to clean them up a little first (I used STL strings
and lists as I am comfortable with them and have never used the QT
ones before, so i will have to update the code to make use of the QT
utilities before submission of the patch).

For a reference the project is called EDoc++
http://edoc.sourceforge.net/


Thanks,
Brendon.

Re: [Doxygen-develop] Ada parser support (was: Fortran90 parser: interest?)

[Arnold.Steve <arn...@en...>]

Howdy:

I just got the email announcing that Aonix is going to release the
source for their ADT plugin for Eclipse as a new Eclipse project.
Great, you're thinking, but how does that help Doxygen?  Well, the way I
understand the Eclipse design, the plugins generally include their own
compiler (of a sort) as part of the language IDE.  This is the way they
do code analysis in Eclipse, build the abstract syntax trees, etc.

So maybe I'm way off base here, but I'm think there should be a way to
leverage that code into an Ada parser for Doxygen.

Thoughts?

Steve

PS. I got yanked into a bunch of review meetings, but I hope to test my
ada2cpp idea soon (unless somebody else gets to it first...).
=20

> -----Original Message-----
> From: dox...@li...=20
> [mailto:dox...@li...] On=20
> Behalf Of Jeffrey Creem
> Sent: Thursday, March 01, 2007 4:08 PM
> To: dox...@li...
> Subject: Re: [Doxygen-develop] Fortran90 parser: interest?
>=20
> Arnold.Steve wrote:
> > I could use Fortran support in general, as well as Ada83/95...
> >
> > So yes, I'd day there's definitely interest.
> >
> > Steve
> >
> > --
> > Stephen L. Arnold
> >=20=20
> >=20=20=20
> I agree. fortran support would be good. Ada 95/2005 support would be=20
> even better.
>=20
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the=20
> chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
&CID=3DDEVDEV
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop
>=20

The information contained in this email message is intended only for the us=
e of the individuals to whom it is addressed and may contain information th=
at is privileged and sensitive. If the reader of this message is not the in=
tended recipient, you are hereby notified that any dissemination, distribut=
ion or copying of this communication is strictly prohibited. If you have re=
ceived this communication in error, please notify the sender immediately by=
 email at the above referenced address. Thank you.

[Doxygen-develop] Undeserved explicit link warnings with 1.5.2

[Robbie G. <ro...@m8...>]

Hi All,
I'm getting warnings like

  myFile.cpp:2: Warning: explicit link request to 'myFunction' could
not be resolved

The documentation source in question is a "#myFunction" reference in
the @file section of myFile.cpp.

They're being generated by calls to docparser.cpp's handleLinkedWord
from the buildFileList call of parseInput. Note that myFunction is
indeed a documented function. The generated documentation is actually
correct - when handleLinkedWord is called from doxygen.cpp's
generateFileDocs, no warning is produced, and the correct link is made
in the final generated documentation.

The first call (the one that produces the warnings) is via
Definition::_setBriefDescription, which calls parseCommentAsText in
order to garner the tooltip text - so iiuc it doesn't need to expand
the links anyway. I hacked up a quick change using a global set by
validatingParseDoc to arrange handleLinkedWord to just return a
DocWord always, and arrange for only the call from parseCommentAsText
to set the global. This appears to fix the problem, but maybe there's
a better way to address this ?

To a first glance/guess, it looks like the early warnings are being
produced because the functions have not yet been parsed, and so the
references to them are unknown. I get a few other cases, some when
variables reference function names, and occasionally when variables
reference other variables.

The same issue occurs for \ref links in the same context, and for the
same reasons. A simliar change (using the same global) in
DocRef::DocRef also fixes this.

i'm happy to post my patch if that's desired, but if there's a better
way to attack this, lmk and (time permitting) i'll have a go at
implementing that.

This happens both with a self compiled exe and with the distributed
zipped binaries (windows).

 - robbie