doxygen-develop

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

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

Hi

Am Montag, 6. Dezember 2004 19:38 schrieb Dimitri van Heesch:
=2E..
> + BUG: id 157085: Autolinks for const/volatile operators didn't work.
> + BUG: id 157433: Multi-variable declarations were not parsed
> properly.=20
=2E..
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=3D120389


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=A0constcharp_fctCall (const char *)
4.  int=A0constcharpconst_fctCall (const char *const)
5.  int constconst_fctCall (MyType *const)
6.  int constcharpconst_fctCall (const char *const)
7.  int=A0intp_fctCall (int *)
8.  int=A0intpconst_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 =20
has the right elements inside.

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

Thanks for listening=20
Enno

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

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

Hi

Am Samstag, 11. Dezember 2004 22:28 schrieb Dimitri van Heesch:
> On Fri, 10 Dec 2004 14:28:31 +0100, Enno Bartels
>
> <enn...@t-...> wrote:
> > 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!
>
> I've working on a simple regression test suite myself (see attachment).
> I think it is indeed a good idea to collect more test cases so any
> regression is found quickly.
>
> I've added your const functions now, and any new test cases or
> improvements to the scripts are welcomed.
Hi I will test it and try to combine it with my work also.

What does your test suit do?
 ++ Check if the doxygen xml output has change since the last time
  -- Check if the doxygen output has some specific result!
  ?

Thanks for listening
Enno

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

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

> > I've working on a simple regression test suite myself (see attachment).
> > I think it is indeed a good idea to collect more test cases so any
> > regression is found quickly.
> >
> > I've added your const functions now, and any new test cases or
> > improvements to the scripts are welcomed.
> Hi I will test it and try to combine it with my work also.
> 
> What does your test suit do?
>  ++ Check if the doxygen xml output has change since the last time
>   -- Check if the doxygen output has some specific result!
> 

From the README:

This directory contains a number of test source files and two scripts
- update.sh: Updates the reference output for each test. The XML output is
             used for this, as this doesn't contain any layout specifics.
             This should typically be done once using a version of doxygen 
             that is known to be good.
- check.sh:  Runs each test and checks the output against the last updated
             version. Warnings reported by doxygen or differences in the
             output produced make a test fail. Differences are placed in a
             diff file with the name of the test file.

So you basically run update.sh once (and again if some features are
add that result in
different output). And then use check.sh to verify if the results are
still the same by
comparing the XML output) and if doxygen doesn't produce any warnings.

Regards,
  Dimitri

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

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

On Fri, 10 Dec 2004 14:28:31 +0100, Enno Bartels
<enn...@t-...> wrote:
> 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!

I've working on a simple regression test suite myself (see attachment).
I think it is indeed a good idea to collect more test cases so any 
regression is found quickly. 

I've added your const functions now, and any new test cases or 
improvements to the scripts are welcomed.

Regards,
   Dimitri