[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