doxygen-develop Mailing List for Doxygen (Page 59)
Brought to you by:
dimitri
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
(4) |
Jul
(29) |
Aug
(8) |
Sep
(8) |
Oct
(17) |
Nov
(34) |
Dec
(6) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(20) |
Feb
(14) |
Mar
(11) |
Apr
(9) |
May
(8) |
Jun
(7) |
Jul
(25) |
Aug
(12) |
Sep
(12) |
Oct
(24) |
Nov
(27) |
Dec
(12) |
2003 |
Jan
(12) |
Feb
(14) |
Mar
(15) |
Apr
(11) |
May
(17) |
Jun
(20) |
Jul
(32) |
Aug
(13) |
Sep
(34) |
Oct
(12) |
Nov
(16) |
Dec
(33) |
2004 |
Jan
(20) |
Feb
(6) |
Mar
(20) |
Apr
(15) |
May
(16) |
Jun
(28) |
Jul
(7) |
Aug
(7) |
Sep
(17) |
Oct
(16) |
Nov
(17) |
Dec
(43) |
2005 |
Jan
(15) |
Feb
(5) |
Mar
(14) |
Apr
(4) |
May
(3) |
Jun
(8) |
Jul
(17) |
Aug
(16) |
Sep
(7) |
Oct
(17) |
Nov
(1) |
Dec
(7) |
2006 |
Jan
(7) |
Feb
(6) |
Mar
(10) |
Apr
(6) |
May
(3) |
Jun
(4) |
Jul
(3) |
Aug
(3) |
Sep
(18) |
Oct
(11) |
Nov
(10) |
Dec
(3) |
2007 |
Jan
(12) |
Feb
(12) |
Mar
(23) |
Apr
(5) |
May
(13) |
Jun
(6) |
Jul
(5) |
Aug
(4) |
Sep
(8) |
Oct
(10) |
Nov
(6) |
Dec
(7) |
2008 |
Jan
(7) |
Feb
(13) |
Mar
(35) |
Apr
(14) |
May
(13) |
Jun
(4) |
Jul
(9) |
Aug
(6) |
Sep
(12) |
Oct
(9) |
Nov
(6) |
Dec
(3) |
2009 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
(15) |
May
(1) |
Jun
(2) |
Jul
(7) |
Aug
(3) |
Sep
(4) |
Oct
(1) |
Nov
(2) |
Dec
(1) |
2010 |
Jan
(4) |
Feb
|
Mar
(5) |
Apr
(1) |
May
(5) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(11) |
Oct
(2) |
Nov
(1) |
Dec
(5) |
2011 |
Jan
(12) |
Feb
(3) |
Mar
(28) |
Apr
(4) |
May
(3) |
Jun
(4) |
Jul
(15) |
Aug
(12) |
Sep
(2) |
Oct
(3) |
Nov
(6) |
Dec
(3) |
2012 |
Jan
(1) |
Feb
(4) |
Mar
(9) |
Apr
(5) |
May
(6) |
Jun
(6) |
Jul
(3) |
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
(9) |
Dec
(7) |
2013 |
Jan
(8) |
Feb
(14) |
Mar
(15) |
Apr
(21) |
May
(29) |
Jun
(34) |
Jul
(3) |
Aug
(7) |
Sep
(13) |
Oct
(1) |
Nov
(3) |
Dec
(5) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(2) |
Jun
(4) |
Jul
(2) |
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
(4) |
Dec
(2) |
2015 |
Jan
(7) |
Feb
(4) |
Mar
(3) |
Apr
(15) |
May
(4) |
Jun
(9) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
(3) |
Dec
(7) |
2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(9) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(5) |
2018 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
(7) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2021 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: <Joh...@sy...> - 2002-10-16 08:38:05
|
Hi just in case, somebody is still using 1.2.17. There is a bug in the xml output. Closing ">" was missing in the <include statement. Line 1539 in xmlgen.cpp: - - t << " local=\"" << (ii->local ? "yes" : "no") << "\"" ++ t << " local=\"" << (ii->local ? "yes" : "no") << "\"" << ">"; Johannes ---- Johannes Klein Software Engineer Symbian Ltd. http://www.symbian.com ********************************************************************** Symbian Ltd is a company registered in England and Wales with registered number 01796587 and registered office at 19 Harcourt Street, London, W1H 4HF, UK. This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify pos...@sy... and delete the message and any attachments accompanying it immediately. Symbian does not accept liability for any corruption, interception, amendment, tampering or viruses occuring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy. ********************************************************************** |
From: <ca...@cr...> - 2002-10-16 07:40:33
|
Hi!=09 Line 281 (in Russian version line 278) is wrong for Russian translator = too. > -----Original Message----- > From: Dimitri van Heesch [mailto:di...@st...] > Sent: Wednesday, October 16, 2002 12:23 AM > To: dox...@li... > Subject: Re: [Doxygen-develop] New version of Brazilian translator >=20 >=20 > On Tue, Oct 15, 2002 at 02:20:59PM -0300, FJTC (Fabio Jun=20 > Takada Chino) wrote: > >=20 > > Hi. > >=20 > > This is the new version of Brazilian Portuguese translator.=20 > I found a small bug > > in the translator_en.h at line 281. It is > >=20 > > if (extractAll) .... > >=20 > > but must be > >=20 > > if (!extractAll) ... > >=20 > > I did not fix it to avoid conflicts between versions. >=20 > This is wrong indeed. I've now fixed it for all languages for which > I could see it was wrong (this excludes Japanese, Korean, Russian, > Taiwanese, Chinese and Greek). >=20 > > I also have a comment about the method trDocumentation(). I=20 > think it should get > > the project name as a parameter to avoid problems with=20 > languages (like > > Portuguese) which allows the form "Documentation of X" but=20 > not the form "X > > Documentation" (the English common form). I'm not sure but=20 > I think that other > > Latin languages may have the same problem. >=20 > Yes, this needs fixing for a long time. >=20 > Regards, > Dimitri >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop >=20 |
From: Dimitri v. H. <di...@st...> - 2002-10-15 20:22:50
|
On Tue, Oct 15, 2002 at 02:20:59PM -0300, FJTC (Fabio Jun Takada Chino) wrote: > > Hi. > > This is the new version of Brazilian Portuguese translator. I found a small bug > in the translator_en.h at line 281. It is > > if (extractAll) .... > > but must be > > if (!extractAll) ... > > I did not fix it to avoid conflicts between versions. This is wrong indeed. I've now fixed it for all languages for which I could see it was wrong (this excludes Japanese, Korean, Russian, Taiwanese, Chinese and Greek). > I also have a comment about the method trDocumentation(). I think it should get > the project name as a parameter to avoid problems with languages (like > Portuguese) which allows the form "Documentation of X" but not the form "X > Documentation" (the English common form). I'm not sure but I think that other > Latin languages may have the same problem. Yes, this needs fixing for a long time. Regards, Dimitri |
From: FJTC (F. J. T. Chino) <ch...@ic...> - 2002-10-15 17:24:43
|
Hi. This is the new version of Brazilian Portuguese translator. I found a small bug in the translator_en.h at line 281. It is if (extractAll) .... but must be if (!extractAll) ... I did not fix it to avoid conflicts between versions. I also have a comment about the method trDocumentation(). I think it should get the project name as a parameter to avoid problems with languages (like Portuguese) which allows the form "Documentation of X" but not the form "X Documentation" (the English common form). I'm not sure but I think that other Latin languages may have the same problem. See you... FJTC ---------------------------------------------------------------------- FJTC (Fabio Jun Takada Chino) - ch...@ic... Computer Science - ICMC - University of Sao Paulo - Brazil GBDI - Grupo de Base de Dados e Imagens ---------------------------------------------------------------------- Homepage http://www.icmc.sc.usp.br/~chino (main) http://gbdi.icmc.sc.usp.br/ (GBDI) http://www.fjtc.hpg.com.br/ (Anime - Portuguese Only) http://www.bbits.hpg.com.br/ (Game Programming - English Only) ====================================================================== |
From: Darren B. <Da...@CO...> - 2002-10-11 09:46:28
|
A Win32 Pas2Dox user reported to me that he could not generate documentation for filenames containing spaces. I have made the following modifications (in bold) to my local copy of Doxygen 1.2.18, which adds quotes around the filename. util.cpp void preprocessFile(const char *fileName,BufStr &output) else // filter the input { QCString cmd=Config_getString("INPUT_FILTER")+" \""+name+"\""; FILE *f=popen(cmd,"r"); if (!f) { err("Error: could not execute filter %s\n",Config_getString("INPUT_FILTER").data()); return ""; } pre.l void preprocessFile(const char *fileName,BufStr &output) QCString cmd = inputFilter+" \""+fileName+"\""; Ta, Darren. |
From: Ryunosuke S. <pe...@mi...> - 2002-10-06 02:27:28
|
I was confusing. Please ignore the mail. ----- Original Message ----- From: "FJTC (Fabio Jun Takada Chino)" <ch...@ic...> To: "Ryunosuke Satoh" <su...@ho...> Cc: "Doxygen developers" <dox...@li...> Sent: Sunday, October 06, 2002 11:16 AM Subject: Re: [Doxygen-develop] libpng problem > On Sun, 6 Oct 2002, Ryunosuke Satoh wrote: > > > Hi doxygen developers, > > > > I'm porting on cygwin, but cygwin maintainers say, > > ----------------------------------- > > > Anyway, I am saying it again - it is not a showstopper... but it would be > > > nice to have it linked against the dll. It'll save some space and also > > > will utilize the work of other peoples which spent time on portin libpng > > > to Cygwin and made it possible to build it as dll. > > ----------------------------------- > > They say that doxygen must exclude libpng source files. > > They dislike one package include other library without dynamic linking. > > I will obey their arguments on cygwin "only". > > I don't know we must exclude libpng on all platform. > > I think windows developers needs the source files. > > > > Would you give me your opinion? > > > > Ryunosuke Satoh > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Doxygen-develop mailing list > > Dox...@li... > > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > > > > Hi. > > It's a quite strange. > > Isn't libpng under GPL (or LGPL) ? I don't know it. If so, the porting is > under the GPL (or LGPL) too (copyleft of GPL and LGPL). > > Since Doxygen is under GPL it will not be a problem to link doxygen to it. > > See you... > FJTC > > ---------------------------------------------------------------------- > FJTC (Fabio Jun Takada Chino) - ch...@ic... > Computer Science - ICMC - University of Sao Paulo - Brazil > GBDI - Grupo de Base de Dados e Imagens > ---------------------------------------------------------------------- > Homepage > http://www.icmc.sc.usp.br/~chino (main) > http://gbdi.icmc.sc.usp.br/ (GBDI) > http://www.fjtc.hpg.com.br/ (Anime - Portuguese Only) > http://www.bbits.hpg.com.br/ (Game Programming - English Only) > ====================================================================== > |
From: FJTC (F. J. T. Chino) <ch...@ic...> - 2002-10-06 02:20:10
|
On Sun, 6 Oct 2002, Ryunosuke Satoh wrote: > Hi doxygen developers, > > I'm porting on cygwin, but cygwin maintainers say, > ----------------------------------- > > Anyway, I am saying it again - it is not a showstopper... but it would be > > nice to have it linked against the dll. It'll save some space and also > > will utilize the work of other peoples which spent time on portin libpng > > to Cygwin and made it possible to build it as dll. > ----------------------------------- > They say that doxygen must exclude libpng source files. > They dislike one package include other library without dynamic linking. > I will obey their arguments on cygwin "only". > I don't know we must exclude libpng on all platform. > I think windows developers needs the source files. > > Would you give me your opinion? > > Ryunosuke Satoh > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > Hi. It's a quite strange. Isn't libpng under GPL (or LGPL) ? I don't know it. If so, the porting is under the GPL (or LGPL) too (copyleft of GPL and LGPL). Since Doxygen is under GPL it will not be a problem to link doxygen to it. See you... FJTC ---------------------------------------------------------------------- FJTC (Fabio Jun Takada Chino) - ch...@ic... Computer Science - ICMC - University of Sao Paulo - Brazil GBDI - Grupo de Base de Dados e Imagens ---------------------------------------------------------------------- Homepage http://www.icmc.sc.usp.br/~chino (main) http://gbdi.icmc.sc.usp.br/ (GBDI) http://www.fjtc.hpg.com.br/ (Anime - Portuguese Only) http://www.bbits.hpg.com.br/ (Game Programming - English Only) ====================================================================== |
From: Ryunosuke S. <pe...@mi...> - 2002-10-05 23:54:02
|
Thanks,I succeed. Ryu ----- Original Message ----- From: "Patrick Hughes" <Pat...@ho...> To: <dox...@li...> Sent: Sunday, October 06, 2002 12:59 AM Subject: [Doxygen-develop] Re: libpng problem > Just modify the link line under the win32-g++ tmake dir, to use -lpng.dll > instead of -lpng > > Patrick > |
From: Patrick H. <Pat...@ho...> - 2002-10-05 19:30:44
|
Just modify the link line under the win32-g++ tmake dir, to use -lpng.dll instead of -lpng Patrick "Ryunosuke Satoh" <pe...@mi...> wrote in message news:006b01c26c85$aef9eca0$5b01a8c0@athlon... > Hi doxygen developers, > > I'm porting on cygwin, but cygwin maintainers say, > ----------------------------------- > > Anyway, I am saying it again - it is not a showstopper... but it would be > > nice to have it linked against the dll. It'll save some space and also > > will utilize the work of other peoples which spent time on portin libpng > > to Cygwin and made it possible to build it as dll. > ----------------------------------- > They say that doxygen must exclude libpng source files. > They dislike one package include other library without dynamic linking. > I will obey their arguments on cygwin "only". I want to include doxygen in cygwin distribution. > I don't know we must exclude libpng on all platform. > I think windows developers needs the source files. > > Would you give me your opinion? > > Ryunosuke Satoh > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf |
From: Ryunosuke S. <pe...@mi...> - 2002-10-05 15:41:40
|
Hi doxygen developers, I'm porting on cygwin, but cygwin maintainers say, ----------------------------------- > Anyway, I am saying it again - it is not a showstopper... but it would be > nice to have it linked against the dll. It'll save some space and also > will utilize the work of other peoples which spent time on portin libpng > to Cygwin and made it possible to build it as dll. ----------------------------------- They say that doxygen must exclude libpng source files. They dislike one package include other library without dynamic linking. I will obey their arguments on cygwin "only". I want to include doxygen in cygwin distribution. I don't know we must exclude libpng on all platform. I think windows developers needs the source files. Would you give me your opinion? Ryunosuke Satoh |
From: Ryunosuke S. <su...@ho...> - 2002-10-05 15:37:53
|
Hi doxygen developers, I'm porting on cygwin, but cygwin maintainers say, ----------------------------------- > Anyway, I am saying it again - it is not a showstopper... but it would be > nice to have it linked against the dll. It'll save some space and also > will utilize the work of other peoples which spent time on portin libpng > to Cygwin and made it possible to build it as dll. ----------------------------------- They say that doxygen must exclude libpng source files. They dislike one package include other library without dynamic linking. I will obey their arguments on cygwin "only". I don't know we must exclude libpng on all platform. I think windows developers needs the source files. Would you give me your opinion? Ryunosuke Satoh |
From: Dimitri v. H. <di...@st...> - 2002-10-03 17:47:42
|
On Tue, Oct 01, 2002 at 06:21:09AM +0900, Ryunosuke Satoh wrote: > Hi > > I found incompatibility. > This problem causes garbage characters in Japanese. > > source1: > ------------------------------------- > /** > * test > * \param c \b \\param3 <-- check > */ > int main(char a, ///< \b param1 > int b ///< \b \\param2 <-- check > ); > > Please tell me the cause or the name of doubtful file. > Help me! I'm seeking it for twelve hours. There were several problems with escaping commands (like using \\param). I'll try to have them fixed them in the next release. Regards, Dimitri |
From: Dimitri v. H. <di...@st...> - 2002-10-03 17:45:50
|
On Thu, Oct 03, 2002 at 07:26:36PM +0400, Andrew Zabolotny wrote: > Hello! > > As I have mentioned a couple of days ago on the doxygen-users list, I've > encountered a Bad Thing {tm} in doxygen: INPUT_ENCODING does not have effect on > example files. Nobody replied, thus I've decided I'm the first one with this > problem. So I took the sources and digged ahead... > > That's what I've found: if we change line 350 of doc.l to look this way: > currentIncludeFile=fileToString(fd->absFilePath(),Config_getBool > ("FILTER_SOURCE_FILES")); > > and also the line 387 to look like this: > od.codify(fileToString(fd->absFilePath(),Config_getBool("FILTER_SOURCE_FILES")) > +"\n"); > > my problem is gone. I don't know whether this is the best solution (not sure > what for includeFile() and verbIncludeFile are used for...) but I think the > developers should take a look at this... I was thinking about this solution as well. It's good to know that you already tried it and it worked ;-) Regards, Dimitri |
From: Andrew Z. <an...@ma...> - 2002-10-03 15:25:46
|
Hello! As I have mentioned a couple of days ago on the doxygen-users list, I've encountered a Bad Thing {tm} in doxygen: INPUT_ENCODING does not have effect on example files. Nobody replied, thus I've decided I'm the first one with this problem. So I took the sources and digged ahead... That's what I've found: if we change line 350 of doc.l to look this way: currentIncludeFile=fileToString(fd->absFilePath(),Config_getBool ("FILTER_SOURCE_FILES")); and also the line 387 to look like this: od.codify(fileToString(fd->absFilePath(),Config_getBool("FILTER_SOURCE_FILES")) +"\n"); my problem is gone. I don't know whether this is the best solution (not sure what for includeFile() and verbIncludeFile are used for...) but I think the developers should take a look at this... Greetings, _\ndy |
From: Stefan W. <dox...@ma...> - 2002-10-02 14:18:47
|
(and again ...) Hi there! It seams that I found a funny bug. \link foo::foo constructor \endlink is parsed as \link foo::foo const ructor \endlink (please note the space in const ructor!) and thus results in a warning and a missing link. Workaround: "\link foo::foo Constructor \endlink" with a upper case "C" I using doxygen 1.2.17. Stefan BTW: Shall bugs be posted to doxygen-users, doxygen-develop or both and is there a up-to-date list of bugs available online? //////////////////////////////////////////////////////////////////////////// /*! \brief Mail signature \author Stefan Wahl \since doxygen 1.12.10 \note Please reply to the list. That's why it exists. */ //////////////////////////////////////////////////////////////////////////// |
From: Ryunosuke S. <pe...@mi...> - 2002-09-30 21:21:17
|
Hi I found incompatibility. This problem causes garbage characters in Japanese. source1: ------------------------------------- /** * test * \param c \b \\param3 <-- check */ int main(char a, ///< \b param1 int b ///< \b \\param2 <-- check ); HTML output from souce1: --------------------------------------- Function Documentation int main ( char a, int b ) test Parameters: c \\param3 <-- check Parameters: a param1 b \param2 <-- check ------------------------------------------ Same arguments, different outputs. BACK SLASH go away. --------------------------------------- Input: * \param c \b \\param3 <-- check int b ///< \b \\param2 <-- check Output: c \\param3 <-- check b \param2 <-- check -------------------------------------- Please tell me the cause or the name of doubtful file. Help me! I'm seeking it for twelve hours. Ryunosuke Satoh su...@ho... |
From: Dimitri v. H. <di...@st...> - 2002-09-30 17:20:16
|
On Mon, Sep 30, 2002 at 01:09:07PM +0100, Joh...@sy... wrote: > Hi, > > In version 1.2.18 the XML output is wrong for simplesect. A ">" is > inserted wrongly. > > Example: > > <simplesect kind=">return"> > <simplesect kind=">warning"> > etc. Indeed, that's a pretty silly bug. Will be fixed ASAP. Regards, Dimitri |
From: <Joh...@sy...> - 2002-09-30 12:11:49
|
Hi, In version 1.2.18 the XML output is wrong for simplesect. A ">" is inserted wrongly. Example: <simplesect kind=">return"> <simplesect kind=">warning"> etc. Thanks Johannes ---- Johannes Klein Software Engineer Symbian Ltd. http://www.symbian.com Telephone: +44 (0) 20 7563 2612 ********************************************************************** Symbian Ltd is a company registered in England and Wales with registered number 01796587 and registered office at 19 Harcourt Street, London, W1H 4HF, UK. This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify pos...@sy... and delete the message and any attachments accompanying it immediately. Symbian does not accept liability for any corruption, interception, amendment, tampering or viruses occuring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy. ********************************************************************** |
From: Ryunosuke S. <pe...@mi...> - 2002-09-28 01:44:59
|
Hi I'm in trouble with garbage characters. Please look at this code. int main(char a, ///< ssa int b ///< ssb\\\\\\\\\ <--- cause ); HTML Docs were generated from this code, but the comment '\\\\\\\\\' was lost. Why lost ? If someone knows that a function delete it from comments, Would you tell me the function name? I must configure it. Ryu su...@ho... |
From: Outhier X. <Xav...@FR...> - 2002-09-24 07:30:33
|
[...] > ========== > ATTENTION! > ========== > > If you are the language maintainer, this is a good time to > update your translator now because Dimitri announced that > version 1.2.18 is going to be released soon. Please, think > about users who do not use sources from CVS, but only the > precompiled binaries. The 1.2.18 will be the next ones for > a while. [...] Sorry I was on vacation. In any way better late than never. (Is it an Englsih expression?) Bye, Xavier. -- Artificial Anthill Project http://aanthill.org |
From: Tom E. <tea...@cs...> - 2002-09-20 07:29:55
|
Please can someone help me with this... it's causing me much stress! I am running two different versions of Doxygen (1.2.8.1 at work and 1.2.16 at home) on a moderate-sized Java project. I'm getting very frustrated with the class-hierarchy generation on the 1.2.16 version. Let me demonstrate: At work I get the following class hierarchy built from my sources: ------------------- * Iterator * BackpropNetwork::LayerIterator * JDialog * ListDialog * NetworkParametersDialog * JFrame * MainWindow * JInternalFrame * MessageFrame * JPanel * ParameterPanel * Observable * AbstractNeuralNetwork * BackpropNetwork * SymmetricHopfieldNetwork * SymmetricDeltaHopfieldNetwork * AsymmetricDeltaHopfieldNetwork * AbstractNeuron * DummyNeuron * SigmoidNeuron * ThresholdNeuron * Serializable * Connection * NetworkModel * NeuralNetwork * AbstractNeuralNetwork * Neuron * AbstractNeuron * Parameter * SupervisedLearning * BackpropNetwork * UnsupervisedLearning * SymmetricHopfieldNetwork ------------------------------------------ This is what I want to see... It has all of my own classes and *only* the classes from the Java libraries that I inherit from. When I run Doxygen at home however, I get not only these classes, but dozens of other classes from the libraries that I use, but don't inherit from. Like this: ------------------------------------------ * Connection * NeuralNetwork * AbstractNeuralNetwork * BackpropNetwork * SymmetricHopfieldNetwork * SymmetricDeltaHopfieldNetwork * AsymmetricDeltaHopfieldNetwork * Neuron * AbstractNeuron * DummyNeuron * SigmoidNeuron * ThresholdNeuron * Parameter * ui::NetworkModel * SupervisedLearning * BackpropNetwork * UnsupervisedLearning * SymmetricHopfieldNetwork * AbstractAction * AbstractAction * AbstractAction * Action * Action * Action * ActionEvent * ActionEvent * ActionEvent * ArrayList * ArrayList * ArrayList * ArrayList * ArrayList * ArrayList * ArrayList * BorderFactory * BorderLayout * BorderLayout * BoxLayout * BufferedWriter * Constructor * Constructor * File * File ..... ...... ----------------------------------- The hierarchy goes on for about 5 more pages... but you see my problem! I really don't want all that stuff showing in my documentation like that. I want a graph like I get with 1.2.8.1, but I don't think I should have to downgrade from 1.2.16. I can get a graph *like* the one I want by using HIDE_UNDOC_CLASSES=YES, but when I do this I no longer get to see the classes from the library that my classes inherit from. There must be something I'm missing here... I'm pretty new to Doxygen, but I've found it invaluable, and come to depend on it greatly. Please can someone help me with this problem? Thanks in advance, Tom -- Tom Eastman <tea...@cs...> GnuPG Key: 12834220 Fingerprint: AF47 70FA 03B5 0EE7 E9B5 B91F 3636 C516 1283 4220 This message is transmitted using 100% recycled electrons. |
From: Ryunosuke S. <su...@ho...> - 2002-09-16 13:44:31
|
Hi, This is new tr_jp.h. I'm trying to add Doxygen to cygwin distribution. just a moment... Ryunosuke Satoh su...@ho... |
From: Prikryl,Petr <PRI...@sk...> - 2002-09-16 08:29:39
|
Info on the status of the language translators (September 16, 2002) (The previous report was from July 8.) (Related to the Doxygen-1.2.17-20020915 in CVS; full translator_report.txt included in the attached zip file. Posted to doxygen-users -- still searching for Finnish and Swedish language maintainers -- and to the doxygen-developers.) Hi, Firstly, thanks to all active language maintainers. Now... ========== ATTENTION! ========== If you are the language maintainer, this is a good time to update your translator now because Dimitri announced that version 1.2.18 is going to be released soon. Please, think about users who do not use sources from CVS, but only the precompiled binaries. The 1.2.18 will be the next ones for a while. Thanks ========== Other news ========== Doxygen speaks another language -- the Catalan. Albert Mora is the Catalan maintainer -- welcome! The total is 28 languages. We have many hot candidates for up-to-date status. Look at the attached translator_report.txt in the attached zip file. ----------------------------------------------- We are still searching for Finnish and Swedish maintainers because their translators became extremely obsolete. It seems that the original maintainers are not in touch with doxygen any more (read it "unreachable"). It may happen that Finnish and Swedish translator will disappear one day, when more complicated changes will be applied to the translator part of doxygen sources. Please, if you know some Finnish or Swedish speaking friends (programmers) who could be interested in doxygen, try to contact them. ----------------------------------------------- With regards, Petr <<tr20020916.zip>> -- Petr Prikryl, Skil, spol. s r.o., (pri...@sk...) |
From: <Nas...@Sy...> - 2002-09-13 12:10:14
|
How easy is it to add custom tags to Doxygen? I have added the following ALIASE: "panic=\par Panic:\n" on the following XML Doc: A double-line breaked paragraph. A paragaph with <CODE>some code</CODE> in it. @code bool samplecode = true; @endcode @deprecated 6.0 Deprecated text. @exception KLeaveCode Leave text @panic USER-120 Panic text @param a Parameter text @post Post condition text. @pre Pre condition text. @verbatim verbatim text tab tab tab @endverbatim @warning Warning text @internal Internal text */ TInt AllTagsFunction(TInt a); and get this: ... <parameterlist kind="exception"><parametername>KLeaveCode</parametername><parameterdescription><para> Leave text </para> </parameterdescription></parameterlist><simplesect kind="par"><para> USER-120 Panic text </para> </simplesect><parameterlist kind="param"><parametername>a</parametername><parameterdescription><para>Parameter text </para> </parameterdescription></parameterlist><simplesect kind="post"><para>Post condition text. </para> </simplesect><simplesect kind="pre"><para>Pre condition text. </para> </simplesect> ... The problem being the panic aliase that was added isn't being added as a <parameterlist kind="panic"> like <parameterlist kind="exception"> but as <simplesect kind="par"> which is wrong. How do I get it to render this new tag properly? Will I have to modify the C++ code? Any help from anyone that has successfully added custom tags would be helpful. ______________________________ Nasser Saleem Ahmed Software Engineer Symbian Ltd United Kingdom ______________________________________ ********************************************************************** Symbian Ltd is a company registered in England and Wales with registered number 01796587 and registered office at 19 Harcourt Street, London, W1H 4HF, UK. This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify pos...@sy... and delete the message and any attachments accompanying it immediately. Symbian does not accept liability for any corruption, interception, amendment, tampering or viruses occuring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy. ********************************************************************** |
From: Miguel <mig...@te...> - 2002-09-09 22:32:00
|
This is a patch against current CVS with the latest version of my new output format, "Perl". See my previous message for details. Now "Perl" should be complete enough to document a simple C file. I've also included a script you can use to generate LaTeX output from the intermediate format. This LaTeX output is by the moment much more incomplete than the standard one, of course, but I think it is more customizable. Read the doxydocs-latex.pl file for instructions. I'm still expecting your comments :-). -- Miguel |