doxyparse addon - simple code parse based on doxyapp

Hello,

My name is Joenio and I am a graduate student in computer science, in my
graduate project I use doxygen to implement a simple source code parse
called doxyparse to extract dependencies between code elements.

The sources of this project are in:

http://gitorious.org/doxygen

Direct address of git repository is:

git://gitorious.org/doxygen/mainline.git

In this repository all doxyparse code is on doxyparse branch.

I would be grateful if the project was accepted as part of doxygen.

Thanks!
--

-- 
Joenio Costa
- www.Colivre.coop.br
- www.Perl.org.br
- Salvador.pm.org

GNU/Linux User #431067 http://counter.li.org

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 

Problems generating mixed c/fortran documentation

Hi:

We have a large amount of legacy fortran code that is used in mixed
c/fortran libraries.  Some of this code is pretty old, but is still
maintained and, as mentioned, integrated into libraries comprised of c
code as well.  The original fortran files used include files with
common areas that were later used to generate c header files via a
modified version of f2c.

Therefore, all symbols have an underscore added to the end, although
we don't add additional underscores, just the one, and the c code code
that uses common areas or makes calls to the fortran subroutines or
functions, adds the underscore directly in the code, e.g., a fortran
subroutine foo(), would be called in c as foo_().  The f2c underscore
decoration makes it impossible to generate mixed c/fortran
documentation that contains appropriate links, since the symbols don't
match.  I realize there are header files that can do this for you, but
we don't use them

I initially modified the existing fortran lexers to accommodate the
underscore decoration, but quickly found other issues with the current
implementation that made it impractical to use it with our code base,
e.g., seg faults on sun, so I decided to rewrite it with a proper
lexer in flex, and parser in bison.  We only use fixed format
fortran77, with some extensions, so my current iteration does not
include any F90 syntax at this point, however, that should be a simple
matter of adding that to the bison grammar.

I just got permission for my employer to submit back patches to the
doxygen project, but would first like to work with some of the fortran

Re: doxyparse addon - simple code parse based on doxyapp

Hi Joenio,

On 11 jul 2009, at 01:52, Joenio Costa wrote:

> Hello,
>
> My name is Joenio and I am a graduate student in computer science,  
> in my
> graduate project I use doxygen to implement a simple source code parse
> called doxyparse to extract dependencies between code elements.
>
> The sources of this project are in:
>
> http://gitorious.org/doxygen
>
> Direct address of git repository is:
>
> git://gitorious.org/doxygen/mainline.git
>
> In this repository all doxyparse code is on doxyparse branch.
>
> I would be grateful if the project was accepted as part of doxygen.

Sounds interesting.

Can you give (a pointer to) more detailed information about
what the tool does? (i.e. the kind of dependencies it extracts, and the
form in which they presented)

Can you make the changes available to developers that do not yet use  

Re: doxyparse addon - simple code parse based on doxyapp

Hi Dimitri,

On Sat, Jul 18, 2009 at 04:54:16PM +0200, Dimitri Van Heesch wrote:
> Sounds interesting.

Thanks!

> Can you give (a pointer to) more detailed information about
> what the tool does? (i.e. the kind of dependencies it extracts, and the
> form in which they presented)

Yes, sure!

Basically doxyparse extract informations about declarations and use of
symbols found in source code. Follow a small example running doxyparse
over addon/doxyapp sources:

----------------------------------------------------
~/src/doxygen$ ./bin/doxyparse addon/doxyapp/
module doxyapp.cpp
   function findXRefSymbols in line 97
   function listSymbol in line 120
   function listSymbols in line 131
      uses function listSymbol defined in doxyapp.cpp
   function lookupSymbol in line 155
   function lookupSymbols in line 204
      uses function lookupSymbol defined in doxyapp.cpp
   function main in line 233
      uses function findXRefSymbols defined in doxyapp.cpp
      uses function listSymbols defined in doxyapp.cpp

Re: doxyparse addon - simple code parse based on doxyapp

ops!

I forgot the attachment.

-- 
Joenio Costa
- www.Colivre.coop.br
- www.Perl.org.br
- Salvador.pm.org

GNU/Linux User #431067 http://counter.li.org

On Tue, Jul 21, 2009 at 12:36:39AM -0300, Joenio Costa wrote:
> Hi Dimitri,
> 
> On Sat, Jul 18, 2009 at 04:54:16PM +0200, Dimitri Van Heesch wrote:
> > Sounds interesting.
> 
> Thanks!
> 
> > Can you give (a pointer to) more detailed information about
> > what the tool does? (i.e. the kind of dependencies it extracts, and the
> > form in which they presented)
> 
> Yes, sure!
> 
> Basically doxyparse extract informations about declarations and use of
> symbols found in source code. Follow a small example running doxyparse
> over addon/doxyapp sources:
> 

[PATCH] Add config options for putting constructors first

Hi there,

on KDE we use sorted member docs which is mostly great except for the fact 
that ctors/dtors get sorted with all of the other members while I'd really 
like them to be on top of the list.

As I couldn't find a way to put them on top, I added a new config option:
SORT_MEMBERS_CONSTRUCTORS_FIRST
which will always put constructors first, destructors after and all other 
members below. The option concerns brief-doc as well as detailed-doc sorting 
but will be ignored for either if SORT_BRIEF_DOCS=NO or SORT_MEMBER_DOCS=NO.

I couldn't find any coding style guide, so I hope I mimicked the style I 
found properly. Please tell me if you want me to change or have further 
suggestions for improvement.

Regards,
Michael Leupold

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

_______________________________________________
Doxygen-develop mailing list

Aliases

Hey all,

  At the moment you can't use cond inside an alias, like:

ALIASES = foodev="\cond FooDev" \
          endfoodev="\endcond"

(http://bugzilla.gnome.org/show_bug.cgi?id=485773)

Does anyone know of a work around?

Can anyone give a hint how I could fix this bug in doxygen?

John Tapsell

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july