Doxygen developer mailing list

headers

Antoine Tandin | 7 Dec 2004 12:54

sending code

The code I’ve send is still not in cvs and I have no feedback to know if there is a problem with my code.

I even don’t know if the code has been received.

Do dimitri <at> stack.nl is the good address to send code ?

Should I use a special mail title for submitting code ?

I did diff –u on /src directory with the lastest cvs snapshot after merging my code with the new snapshot.

Do I need to merge my code with the lastest cvs snapshot until my code has been merged ?

Does the web interface of the cvs is up-to-date ?

headers

Dimitri van Heesch | 7 Dec 2004 13:11

Re: sending code

On Tue, 7 Dec 2004 12:54:39 +0100, Antoine Tandin
<atandin <at> komodosoft.com> wrote:
> 
> The code I've send is still not in cvs and I have no feedback to know if
> there is a problem with my code.
> 
> I even don't know if the code has been received.
> 
> Do dimitri <at> stack.nl is the good address to send code ?
> 
> Should I use a special mail title for submitting code ?
> 

The address is ok, and the mail has been received. I just haven't
gotten around to it yet.
I did have a brief look and if the patch was trivial to apply I would
have done so, but
that was not the case. The main reasons are:
- The patch contains 4 or so features combined in one. So it is a all
or nothing approach.
- The new features/fixes were not discussed on forehand, and I do not
agree with the
   implementation in all cases.

> I did diff –u on /src directory with the lastest cvs snapshot after merging
> my code with the new snapshot.
> 
> Do I need to merge my code with the lastest cvs snapshot until my code has
> been merged ?

No not necessarily, but if you could split the patch up into more managable 
parts that would help.

Regards,
  Dimitri

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

headers

Antoine Tandin | 7 Dec 2004 18:29

new feature discussion

Hello, I would like to discuss about some new options(features) for
doxygen.
All of them are triggered by the configuration file.

So I introduce them by there configuration name.

1 - NO_TYPEDEF_REFERENCED_BY_RELATION
Just don't produce the "Referenced by" paragraph for typedef.
Most of the time, this paragraph is long and useless.
There is no "reference by" for classes... so why for typedef.

The patch is very simple :
Just add a condition in the function addDocCrossReference
static void addDocCrossReference(MemberDef *src,MemberDef *dst)
{
  //printf("addDocCrossReference
src=%s,dst=%s\n",src->name().data(),dst->name().data());
  if ( dst->isTypedef() &&
Config_getBool("NO_TYPEDEF_REFERENCED_BY_RELATION") ) //+++ added line
    return;
//+++ added line
  if (Config_getBool("REFERENCED_BY_RELATION") && 
      (src->isFunction() || src->isSlot()) 
     )
  {
    dst->addSourceReferencedBy(src);
  }
  if ((Config_getBool("REFERENCES_RELATION") ||
Config_getBool("CALL_GRAPH")) && 
      (src->isFunction() || src->isSlot())
     )
  {
    src->addSourceReferences(dst);
  }
}

2 - GROUP_COLLABORATION_GRAPH
Create a dot graph on the top of each group page.
The graph shows relations between groups :
- is the group is part of an other group
- is the group contains other groups
- all members (class, namespace ...) share with other groups

3 - ALLOW_MEMBER_MULTIGROUP
This change the behavior of group pages.
With this option set, group page don't contain member documentation but
only a link to the member documentation.
With this option set, a function can be part of more than one groups.
With this option set, function documentation are no more moved to the
group page, so for a class member, the documentation stays in the class
file...

4 - SHOW_GROUPLINKS
Just add in the documentation of members a link to the group(s) they are
part of. (like for classes)

Please tell me what you think about those features.
Keep in mind that they don't change anything if the options are not set.

All of those 4 features are independent, but 2 and 4 are more relevant
with the 3 set.

Thanks

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

headers

Dimitri van Heesch | 8 Dec 2004 08:28

Re: new feature discussion

On Tue, 7 Dec 2004 18:29:13 +0100, Antoine Tandin
<atandin <at> komodosoft.com> wrote:
> Hello, I would like to discuss about some new options(features) for
> doxygen.
> All of them are triggered by the configuration file.
> 
> So I introduce them by there configuration name.
> 
> 1 - NO_TYPEDEF_REFERENCED_BY_RELATION
> Just don't produce the "Referenced by" paragraph for typedef.
> Most of the time, this paragraph is long and useless.
> There is no "reference by" for classes... so why for typedef.

I agree, but I don't think is it needed to have an option for this:
just always turn this on.

> The patch is very simple :
> Just add a condition in the function addDocCrossReference

> 
> 2 - GROUP_COLLABORATION_GRAPH
> Create a dot graph on the top of each group page.
> The graph shows relations between groups :
> - is the group is part of an other group
> - is the group contains other groups
> - all members (class, namespace ...) share with other groups

This could be useful, but how are you going to express to containment relations.
A "boxes in boxes" approach (which would be natural) doesn't work well with dot.

> 3 - ALLOW_MEMBER_MULTIGROUP
> This change the behavior of group pages.
> With this option set, group page don't contain member documentation but
> only a link to the member documentation.
> With this option set, a function can be part of more than one groups.
> With this option set, function documentation are no more moved to the
> group page, so for a class member, the documentation stays in the class
> file...

This feature has been discussed and requested before, but I don't think it
will work with the current implementation. If you have an undocumented file
with a member in multiple groups and this member is referred to in some place
to which group would you point? (if the file that actually contains
the member was
documented, the file could be a good candidate, but this is not guaranteed. 

> 
> 4 - SHOW_GROUPLINKS
> Just add in the documentation of members a link to the group(s) they are
> part of. (like for classes)

This could be useful (but less so if the member can be in one group only).

Regards,
  Dimitri

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

headers

Maik Hinrichs | 9 Dec 2004 21:23

make clean and make distclean in src

Hello,

I would like to suggest following small changes in src/Makefile.in:

1. "make clean" should remove generated source files by lex and bison, so I 
moved files from distclean to clean.

2. "make distclean" should remove file lang_cfg.h (generated by configure).

Please find attached diff file.

Cu,
Maik

Attachment (src_Makefile.in_diff): text/x-diff, 713 bytes

headers

Maik Hinrichs | 9 Dec 2004 21:44

Build libraries on Solaris (sparc)

Hello,

I had to make a small change in file tmake.conf of target solaris-cc to 
translate the libraries.

I changed value of TMAKE_AR from "CC -xar -o" to "ar cqs".

System: SunOS 5.9 (sparc)
Compiler: CC (gcc 3.3.2)

Please find attached diff file.

Cu,
Maik

Attachment (tmake_lib_solaris-cc_tmake.conf_diff): text/x-diff, 287 bytes

headers

Antoine Tandin | 10 Dec 2004 10:41

RE : new feature discussion

diff file attached for an implementation of those 4 features. Critics
are welcome :)

Following an example in compiled html.

-----Message d'origine-----
De : Antoine Tandin [mailto:atandin <at> komodosoft.com] 
Envoyé : mardi 7 décembre 2004 18:29
À : doxygen-develop <at> lists.sourceforge.net
Objet : [Doxygen-develop] new feature discussion

Hello, I would like to discuss about some new options(features) for
doxygen.
All of them are triggered by the configuration file.

So I introduce them by there configuration name.

1 - NO_TYPEDEF_REFERENCED_BY_RELATION
Just don't produce the "Referenced by" paragraph for typedef.
Most of the time, this paragraph is long and useless.
There is no "reference by" for classes... so why for typedef.

The patch is very simple :
Just add a condition in the function addDocCrossReference
static void addDocCrossReference(MemberDef *src,MemberDef *dst)
{
  //printf("addDocCrossReference
src=%s,dst=%s\n",src->name().data(),dst->name().data());
  if ( dst->isTypedef() &&
Config_getBool("NO_TYPEDEF_REFERENCED_BY_RELATION") ) //+++ added line
    return;
//+++ added line
  if (Config_getBool("REFERENCED_BY_RELATION") && 
      (src->isFunction() || src->isSlot()) 
     )
  {
    dst->addSourceReferencedBy(src);
  }
  if ((Config_getBool("REFERENCES_RELATION") ||
Config_getBool("CALL_GRAPH")) && 
      (src->isFunction() || src->isSlot())
     )
  {
    src->addSourceReferences(dst);
  }
}

2 - GROUP_COLLABORATION_GRAPH
Create a dot graph on the top of each group page.
The graph shows relations between groups :
- is the group is part of an other group
- is the group contains other groups
- all members (class, namespace ...) share with other groups

3 - ALLOW_MEMBER_MULTIGROUP
This change the behavior of group pages.
With this option set, group page don't contain member documentation but
only a link to the member documentation.
With this option set, a function can be part of more than one groups.
With this option set, function documentation are no more moved to the
group page, so for a class member, the documentation stays in the class
file...

4 - SHOW_GROUPLINKS
Just add in the documentation of members a link to the group(s) they are
part of. (like for classes)

Please tell me what you think about those features.
Keep in mind that they don't change anything if the options are not set.

All of those 4 features are independent, but 2 and 4 are more relevant
with the 3 set.

Thanks

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop

Attachment (patch.rar): application/octet-stream, 6881 bytes

headers

Enno Bartels | 10 Dec 2004 14:28

Const test cases working fine -- Re: [Doxygen-users] Doxygen-1.3.9.1-20040612 in CVS

Hi

Am Montag, 6. Dezember 2004 19:38 schrieb Dimitri van Heesch:
...
> + BUG: id 157085: Autolinks for const/volatile operators didn't work.
> + BUG: id 157433: Multi-variable declarations were not parsed
> properly. 
...
Thank you very much for solving this nasty bug.
Now I can use "const" without breaking the doxy docu!

I think this has even solved the following bug
http://bugzilla.gnome.org/show_bug.cgi?id=120389

I did test this with the following test cases and
everyone was working fine (for the first time) !

1.  int charp_fctCall (char *)
2.  int charpconst_fctCall (char *const)
3.  int constcharp_fctCall (const char *)
4.  int constcharpconst_fctCall (const char *const)
5.  int constconst_fctCall (MyType *const)
6.  int constcharpconst_fctCall (const char *const)
7.  int intp_fctCall (int *)
8.  int intpconst_fctCall (int *const)

On my CVS copy of doxygen I do have an additional test
directory for my test cases. And with "make test" it
will generate the docu and check if it  
has the right elements inside.

Maybe it would be wise to add my and even more 
test cases to the doxgen cvs version. So a new version
of doxygen could be tested automaticly for old/new 
problems very easyly!

Thanks for listening 
Enno

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

headers

atandin@komodosoft.com | 10 Dec 2004 18:19

feature suggestion

What do you think about creating hyperlink on class attributes in the
class' collaboration graphs ?

--------------------------------------------------------------------
mail2web - Vérifiez votre courrier électronique depuis le web sur
http://mail2web.com/ .

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

headers

Mohammad Musa | 10 Dec 2004 20:45

Supporting Verilog


Hello All,

I am new to this list and I'm interested in adding verilog support to
doxygen. No one is working on supporting verilog currently. Is that correct?

I would appreciate any help guiding me on how and where to start this
project.

Thanks,
Mohammad

"atandin <at> komodosoft.com" wrote:

> What do you think about creating hyperlink on class attributes in the
> class' collaboration graphs ?
>
> --------------------------------------------------------------------
> mail2web - Vérifiez votre courrier électronique depuis le web sur
> http://mail2web.com/ .
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Doxygen-develop mailing list
> Doxygen-develop <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop

--
---------------------------------------------------
/ /\ / Mohammad Musa       mohammad.musa <at> xilinx.com
\ \    Xilinx              Telephone:  408-559-7778
/ /    2100 Logic Drive    Direct:     408-626-6484
\_\/ \ San Jose, CA 95124  FAX:        408-377-9013

Attachment (mohammad.musa.vcf): text/x-vcard, 182 bytes

27	May 2013
21	April 2013
15	March 2013
14	February 2013
8	January 2013
7	December 2012
9	November 2012
2	October 2012
4	September 2012
3	August 2012
3	July 2012
6	June 2012
6	May 2012
5	April 2012
9	March 2012
4	February 2012
1	January 2012
3	December 2011
6	November 2011
3	October 2011
2	September 2011
12	August 2011
15	July 2011
4	June 2011
3	May 2011
4	April 2011
28	March 2011
2	February 2011
12	January 2011
5	December 2010
1	November 2010
2	October 2010
11	September 2010
3	August 2010
2	July 2010
5	May 2010
1	April 2010
5	March 2010
4	January 2010
1	December 2009
2	November 2009
1	October 2009
4	September 2009
3	August 2009
7	July 2009
2	June 2009
1	May 2009
15	April 2009
2	March 2009
2	February 2009
2	January 2009
3	December 2008
6	November 2008
14	October 2008
12	September 2008
6	August 2008
9	July 2008
4	June 2008
13	May 2008
14	April 2008
35	March 2008
14	February 2008
7	January 2008
7	December 2007
6	November 2007
10	October 2007
8	September 2007
5	August 2007
5	July 2007
6	June 2007
13	May 2007
5	April 2007
23	March 2007
12	February 2007
12	January 2007
3	December 2006
10	November 2006
11	October 2006
19	September 2006
3	August 2006
3	July 2006
4	June 2006
3	May 2006
6	April 2006
10	March 2006
6	February 2006
7	January 2006
7	December 2005
1	November 2005
17	October 2005
7	September 2005
15	August 2005
17	July 2005
8	June 2005
3	May 2005
4	April 2005
14	March 2005
5	February 2005
15	January 2005
42	December 2004
16	November 2004
16	October 2004
18	September 2004
7	August 2004
8	July 2004
28	June 2004
16	May 2004
15	April 2004
20	March 2004
6	February 2004
20	January 2004
35	December 2003
16	November 2003
12	October 2003
34	September 2003
13	August 2003
29	July 2003
17	June 2003
17	May 2003
11	April 2003
15	March 2003
15	February 2003
11	January 2003
10	December 2002
24	November 2002
24	October 2002
12	September 2002
12	August 2002
25	July 2002
7	June 2002
1	May 2002

Mon	Tue	Wed	Thu	Fri	Sat	Sun

		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31