doxygen-develop Mailing List for Doxygen (Page 4)
Brought to you by:
dimitri
Menu
▾
▴
doxygen-develop — List for discussing new features, submitting patches, etc.
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: Timo M. <tim...@gm...> - 2015-07-27 16:09:19
|
Hi all, Found a resolution for my problem, and it is to use extension mapping. Found it by going through existing bugs reported for Doxygen and bumped into Bug 751616 <https://bugzilla.gnome.org/show_bug.cgi?id=751616>. So, all is in order and my proto2cpp <https://sourceforge.net/p/proto2cpp/> filter works fine also with Doxygen v1.8.8 and newer ones. Br, TimoM On Sun, May 10, 2015 at 11:18 PM, Timo Marjoniemi <tim...@gm...> wrote: > Hi Eckard and thanks for your response. > > Unfortunately the instructions given in Bug 700148 > <https://bugzilla.gnome.org/show_bug.cgi?id=700148> didn't help in my > problem... > Another interesting finding is that if I copy the output from proto2cpp > <https://sourceforge.net/p/proto2cpp/> filter and paste it in a .h file > it does work -- Doxygen does generate documentation from the file. > > Br, > Timo M. > > > On Fri, May 8, 2015 at 3:06 PM, Eckard Klotz <eck...@t-...> > wrote: > >> Hello TimoM. >> >> Even you say it was not present with v1.8.7 may this bug-report describe >> a similar problem? >> >> *"Bug 700148* <https://bugzilla.gnome.org/show_bug.cgi?id=700148> - FILTER_PATTERNS >> is working with additional " at the end" at >> "https://bugzilla.gnome.org/show_bug.cgi?id=700148" >> <https://bugzilla.gnome.org/show_bug.cgi?id=700148> >> >> Best regards, >> Eckard Klotz. >> >> >> >> >> Am 07.05.2015 um 22:57 schrieb Timo Marjoniemi: >> >> Hi, >> >> A filter for Google Protocol buffers files I've written ( >> https://sourceforge.net/p/proto2cpp/) does not work from Doxygen v1.8.8 >> onward and so far I haven't been able to make it work. It does work with >> v1.8.7 and several older versions (oldest I've tested is 1.8.1.1). >> Has anyone else encountered such problems with custom Doxygen filters? >> Any clues what could be the root cause and how to fix it? >> >> Thanks in advance, >> TimoM >> >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight.http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> >> >> >> _______________________________________________ >> Doxygen-develop mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/doxygen-develop >> >> >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ >> Doxygen-develop mailing list >> Dox...@li... >> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >> >> > |
|
From: Phyks <ph...@ph...> - 2015-06-22 16:30:11
|
I confirm the method in the SO thread is working. Thanks! Le 2015-06-20 12:50, Albert a écrit : > The doxygen implementation markdown does not support all of markdown, > please see the chaper about markdown in the documentation ( > http://www.stack.nl/~dimitri/doxygen/manual/markdown.html) > > I also forgot to mention about the remarks I placed at: > http://stackoverflow.com/questions/30863422/doxygen-how-to-embed-images-on-main-page-for-all-output-formats > > Albert > > On Sat, Jun 20, 2015 at 10:39 AM, Albert <alb...@gm...> > wrote: > >> I don't think it is directly necessary, the 2 small 3 line examples >> might >> be sufficient. >> >> Albert >> >> On Sat, Jun 20, 2015 at 10:34 AM, Phyks <ph...@ph...> wrote: >> >>> Ah, no, I was not planning to add any attachments. I do not have my >>> sample README.md and doxyfile files with me at the moment. :/ >>> >>> I can send you an example though if you want. >>> >>> -- >>> Phyks >>> >>> Le 20/06/2015 10:21, Albert a écrit : >>> > Looks like you wanted to add an attachment, but forgot it. >>> > >>> > Albert >>> > >>> > On Sat, Jun 20, 2015 at 10:15 AM, Phyks <ph...@ph...> wrote: >>> > >>> >> I am including my README.md file as the homepage of my doxygen >>> >> documentation. >>> >> >>> >> If I write in this file: >>> >> ``` >>> >> <a href="http://link"><img src="http://link.jpg"; /></a> >>> >> ``` >>> >> >>> >> I get the error (although this should be valid markdown formatting). >>> >> >>> >> >>> >> If I write the closest full markdown version: >>> >> ``` >>> >> [](link)] >>> >> ``` >>> >> >>> >> I also get the error. >>> >> >>> >> Thanks >>> >> -- >>> >> Phyks >>> >> >>> >> Le 18/06/2015 19:22, Albert a écrit : >>> >>> In version 1.2.6 there was no markdown support in doxygen so this must >>> >> be a >>> >>> separate problem. An example would be nice. >>> >>> >>> >>> >>> >>> On Thu, Jun 18, 2015 at 12:48 PM, Phyks <ph...@ph...> wrote: >>> >>> >>> >>>> Hi, >>> >>>> >>> >>>> I've just encountered this issue in a Markdown file: >>> >>>> http://sourceforge.net/p/doxygen/mailman/message/12235967/. >>> >>>> >>> >>>> However, according to the thread, I understand it was fixed in 1.2.6 >>> and >>> >>>> I am using 1.8.9.1. >>> >>>> >>> >>>> Thanks >>> >>>> -- >>> >>>> Phyks >>> >>>> >>> >>>> >>> >>>> >>> >> >>> ------------------------------------------------------------------------------ >>> >>>> _______________________________________________ >>> >>>> Doxygen-develop mailing list >>> >>>> Dox...@li... >>> >>>> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >>> >>>> >>> >>> >>> >> >>> >> >>> >> >>> ------------------------------------------------------------------------------ >>> >> _______________________________________________ >>> >> Doxygen-develop mailing list >>> >> Dox...@li... >>> >> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >>> >> >>> > >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Doxygen-develop mailing list >>> Dox...@li... >>> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >>> >> >> -- Phyks |
|
From: Albert <alb...@gm...> - 2015-06-20 10:50:28
|
The doxygen implementation markdown does not support all of markdown, please see the chaper about markdown in the documentation ( http://www.stack.nl/~dimitri/doxygen/manual/markdown.html) I also forgot to mention about the remarks I placed at: http://stackoverflow.com/questions/30863422/doxygen-how-to-embed-images-on-main-page-for-all-output-formats Albert On Sat, Jun 20, 2015 at 10:39 AM, Albert <alb...@gm...> wrote: > I don't think it is directly necessary, the 2 small 3 line examples might > be sufficient. > > Albert > > On Sat, Jun 20, 2015 at 10:34 AM, Phyks <ph...@ph...> wrote: > >> Ah, no, I was not planning to add any attachments. I do not have my >> sample README.md and doxyfile files with me at the moment. :/ >> >> I can send you an example though if you want. >> >> -- >> Phyks >> >> Le 20/06/2015 10:21, Albert a écrit : >> > Looks like you wanted to add an attachment, but forgot it. >> > >> > Albert >> > >> > On Sat, Jun 20, 2015 at 10:15 AM, Phyks <ph...@ph...> wrote: >> > >> >> I am including my README.md file as the homepage of my doxygen >> >> documentation. >> >> >> >> If I write in this file: >> >> ``` >> >> <a href="http://link"><img src="http://link.jpg"; /></a> >> >> ``` >> >> >> >> I get the error (although this should be valid markdown formatting). >> >> >> >> >> >> If I write the closest full markdown version: >> >> ``` >> >> [](link)] >> >> ``` >> >> >> >> I also get the error. >> >> >> >> Thanks >> >> -- >> >> Phyks >> >> >> >> Le 18/06/2015 19:22, Albert a écrit : >> >>> In version 1.2.6 there was no markdown support in doxygen so this must >> >> be a >> >>> separate problem. An example would be nice. >> >>> >> >>> >> >>> On Thu, Jun 18, 2015 at 12:48 PM, Phyks <ph...@ph...> wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> I've just encountered this issue in a Markdown file: >> >>>> http://sourceforge.net/p/doxygen/mailman/message/12235967/. >> >>>> >> >>>> However, according to the thread, I understand it was fixed in 1.2.6 >> and >> >>>> I am using 1.8.9.1. >> >>>> >> >>>> Thanks >> >>>> -- >> >>>> Phyks >> >>>> >> >>>> >> >>>> >> >> >> ------------------------------------------------------------------------------ >> >>>> _______________________________________________ >> >>>> Doxygen-develop mailing list >> >>>> Dox...@li... >> >>>> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >> >>>> >> >>> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> >> Doxygen-develop mailing list >> >> Dox...@li... >> >> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >> >> >> > >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Doxygen-develop mailing list >> Dox...@li... >> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >> > > |
|
From: Albert <alb...@gm...> - 2015-06-20 08:39:45
|
I don't think it is directly necessary, the 2 small 3 line examples might be sufficient. Albert On Sat, Jun 20, 2015 at 10:34 AM, Phyks <ph...@ph...> wrote: > Ah, no, I was not planning to add any attachments. I do not have my > sample README.md and doxyfile files with me at the moment. :/ > > I can send you an example though if you want. > > -- > Phyks > > Le 20/06/2015 10:21, Albert a écrit : > > Looks like you wanted to add an attachment, but forgot it. > > > > Albert > > > > On Sat, Jun 20, 2015 at 10:15 AM, Phyks <ph...@ph...> wrote: > > > >> I am including my README.md file as the homepage of my doxygen > >> documentation. > >> > >> If I write in this file: > >> ``` > >> <a href="http://link"><img src="http://link.jpg"; /></a> > >> ``` > >> > >> I get the error (although this should be valid markdown formatting). > >> > >> > >> If I write the closest full markdown version: > >> ``` > >> [](link)] > >> ``` > >> > >> I also get the error. > >> > >> Thanks > >> -- > >> Phyks > >> > >> Le 18/06/2015 19:22, Albert a écrit : > >>> In version 1.2.6 there was no markdown support in doxygen so this must > >> be a > >>> separate problem. An example would be nice. > >>> > >>> > >>> On Thu, Jun 18, 2015 at 12:48 PM, Phyks <ph...@ph...> wrote: > >>> > >>>> Hi, > >>>> > >>>> I've just encountered this issue in a Markdown file: > >>>> http://sourceforge.net/p/doxygen/mailman/message/12235967/. > >>>> > >>>> However, according to the thread, I understand it was fixed in 1.2.6 > and > >>>> I am using 1.8.9.1. > >>>> > >>>> Thanks > >>>> -- > >>>> Phyks > >>>> > >>>> > >>>> > >> > ------------------------------------------------------------------------------ > >>>> _______________________________________________ > >>>> Doxygen-develop mailing list > >>>> Dox...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/doxygen-develop > >>>> > >>> > >> > >> > >> > ------------------------------------------------------------------------------ > >> _______________________________________________ > >> Doxygen-develop mailing list > >> Dox...@li... > >> https://lists.sourceforge.net/lists/listinfo/doxygen-develop > >> > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > |
|
From: Phyks <ph...@ph...> - 2015-06-20 08:34:43
|
Ah, no, I was not planning to add any attachments. I do not have my sample README.md and doxyfile files with me at the moment. :/ I can send you an example though if you want. -- Phyks Le 20/06/2015 10:21, Albert a écrit : > Looks like you wanted to add an attachment, but forgot it. > > Albert > > On Sat, Jun 20, 2015 at 10:15 AM, Phyks <ph...@ph...> wrote: > >> I am including my README.md file as the homepage of my doxygen >> documentation. >> >> If I write in this file: >> ``` >> <a href="http://link"><img src="http://link.jpg"; /></a> >> ``` >> >> I get the error (although this should be valid markdown formatting). >> >> >> If I write the closest full markdown version: >> ``` >> [](link)] >> ``` >> >> I also get the error. >> >> Thanks >> -- >> Phyks >> >> Le 18/06/2015 19:22, Albert a écrit : >>> In version 1.2.6 there was no markdown support in doxygen so this must >> be a >>> separate problem. An example would be nice. >>> >>> >>> On Thu, Jun 18, 2015 at 12:48 PM, Phyks <ph...@ph...> wrote: >>> >>>> Hi, >>>> >>>> I've just encountered this issue in a Markdown file: >>>> http://sourceforge.net/p/doxygen/mailman/message/12235967/. >>>> >>>> However, according to the thread, I understand it was fixed in 1.2.6 and >>>> I am using 1.8.9.1. >>>> >>>> Thanks >>>> -- >>>> Phyks >>>> >>>> >>>> >> ------------------------------------------------------------------------------ >>>> _______________________________________________ >>>> Doxygen-develop mailing list >>>> Dox...@li... >>>> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >>>> >>> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Doxygen-develop mailing list >> Dox...@li... >> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >> > |
|
From: Albert <alb...@gm...> - 2015-06-20 08:21:50
|
Looks like you wanted to add an attachment, but forgot it. Albert On Sat, Jun 20, 2015 at 10:15 AM, Phyks <ph...@ph...> wrote: > I am including my README.md file as the homepage of my doxygen > documentation. > > If I write in this file: > ``` > <a href="http://link"><img src="http://link.jpg"; /></a> > ``` > > I get the error (although this should be valid markdown formatting). > > > If I write the closest full markdown version: > ``` > [](link)] > ``` > > I also get the error. > > Thanks > -- > Phyks > > Le 18/06/2015 19:22, Albert a écrit : > > In version 1.2.6 there was no markdown support in doxygen so this must > be a > > separate problem. An example would be nice. > > > > > > On Thu, Jun 18, 2015 at 12:48 PM, Phyks <ph...@ph...> wrote: > > > >> Hi, > >> > >> I've just encountered this issue in a Markdown file: > >> http://sourceforge.net/p/doxygen/mailman/message/12235967/. > >> > >> However, according to the thread, I understand it was fixed in 1.2.6 and > >> I am using 1.8.9.1. > >> > >> Thanks > >> -- > >> Phyks > >> > >> > >> > ------------------------------------------------------------------------------ > >> _______________________________________________ > >> Doxygen-develop mailing list > >> Dox...@li... > >> https://lists.sourceforge.net/lists/listinfo/doxygen-develop > >> > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > |
|
From: Phyks <ph...@ph...> - 2015-06-20 08:15:09
|
I am including my README.md file as the homepage of my doxygen documentation. If I write in this file: ``` <a href="http://link"><img src="http://link.jpg"; /></a> ``` I get the error (although this should be valid markdown formatting). If I write the closest full markdown version: ``` [](link)] ``` I also get the error. Thanks -- Phyks Le 18/06/2015 19:22, Albert a écrit : > In version 1.2.6 there was no markdown support in doxygen so this must be a > separate problem. An example would be nice. > > > On Thu, Jun 18, 2015 at 12:48 PM, Phyks <ph...@ph...> wrote: > >> Hi, >> >> I've just encountered this issue in a Markdown file: >> http://sourceforge.net/p/doxygen/mailman/message/12235967/. >> >> However, according to the thread, I understand it was fixed in 1.2.6 and >> I am using 1.8.9.1. >> >> Thanks >> -- >> Phyks >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Doxygen-develop mailing list >> Dox...@li... >> https://lists.sourceforge.net/lists/listinfo/doxygen-develop >> > |
|
From: Albert <alb...@gm...> - 2015-06-18 17:22:44
|
In version 1.2.6 there was no markdown support in doxygen so this must be a separate problem. An example would be nice. On Thu, Jun 18, 2015 at 12:48 PM, Phyks <ph...@ph...> wrote: > Hi, > > I've just encountered this issue in a Markdown file: > http://sourceforge.net/p/doxygen/mailman/message/12235967/. > > However, according to the thread, I understand it was fixed in 1.2.6 and > I am using 1.8.9.1. > > Thanks > -- > Phyks > > > ------------------------------------------------------------------------------ > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > |
|
From: Phyks <ph...@ph...> - 2015-06-18 11:02:52
|
Hi, I have an issue with preprocessor directives in inline code in Markdown readme included in Doxygen doc. When compiling the file, I get ``` README.md:175: warning: explicit link request to 'if' could not be resolved ``` Due to the line in the README. ``` * Code should **never** be commented out. To temporarily comment some code, use `#if 0` preprocessor directive. ``` It compiles fine, but there is still a warning during compilation. Note also that the warning message refers to line 175 although my README.md file has only 169 lines (and the faulty one is the last one). Thanks! -- Phyks |
|
From: Phyks <ph...@ph...> - 2015-06-18 10:57:50
|
Hi, I've just encountered this issue in a Markdown file: http://sourceforge.net/p/doxygen/mailman/message/12235967/. However, according to the thread, I understand it was fixed in 1.2.6 and I am using 1.8.9.1. Thanks -- Phyks |
|
From: <Ale...@ex...> - 2015-05-27 18:12:44
|
Hello, I asked this question on the doxygen users list, but without any luck. It would be nice if this little feature could be added to the doxygen code to parse bash functions correctly. Besides of this little parser problem it works like a charm! I found a little doxygen filter for bash functions: http://www.cbica.upenn.edu/sbia/software/basis/apidoc/v1.0/doxyfilter-bash_8py_source.html After a few changes, it works really fine for my sources (60_000 loc). (Attached, plus Example file) But there is a thing, which is really annoying, there are tons of bash-functions, which uses a dot or a minus in the function name (which is allowed in bash), for example: function e.() { echo "hello" } function e-e() { echo "foo" } Is there a chance to add the dot and the minus for function names, so that doxygen is able to parse these names correctly? It would be very helpful. Thank you. Best regards, Alexander Elgert |
|
From: Timo M. <tim...@gm...> - 2015-05-10 20:19:02
|
Hi Eckard and thanks for your response. Unfortunately the instructions given in Bug 700148 <https://bugzilla.gnome.org/show_bug.cgi?id=700148> didn't help in my problem... Another interesting finding is that if I copy the output from proto2cpp <https://sourceforge.net/p/proto2cpp/> filter and paste it in a .h file it does work -- Doxygen does generate documentation from the file. Br, Timo M. On Fri, May 8, 2015 at 3:06 PM, Eckard Klotz <eck...@t-...> wrote: > Hello TimoM. > > Even you say it was not present with v1.8.7 may this bug-report describe a > similar problem? > > *"Bug 700148* <https://bugzilla.gnome.org/show_bug.cgi?id=700148> - FILTER_PATTERNS > is working with additional " at the end" at > "https://bugzilla.gnome.org/show_bug.cgi?id=700148" > <https://bugzilla.gnome.org/show_bug.cgi?id=700148> > > Best regards, > Eckard Klotz. > > > > > Am 07.05.2015 um 22:57 schrieb Timo Marjoniemi: > > Hi, > > A filter for Google Protocol buffers files I've written ( > https://sourceforge.net/p/proto2cpp/) does not work from Doxygen v1.8.8 > onward and so far I haven't been able to make it work. It does work with > v1.8.7 and several older versions (oldest I've tested is 1.8.1.1). > Has anyone else encountered such problems with custom Doxygen filters? > Any clues what could be the root cause and how to fix it? > > Thanks in advance, > TimoM > > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight.http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > > > > _______________________________________________ > Doxygen-develop mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/doxygen-develop > > > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > > |
|
From: Eckard K. <eck...@t-...> - 2015-05-08 12:06:44
|
Hello TimoM. Even you say it was not present with v1.8.7 may this bug-report describe a similar problem? *"Bug 700148* <https://bugzilla.gnome.org/show_bug.cgi?id=700148> -FILTER_PATTERNS is working with additional " at the end" at "https://bugzilla.gnome.org/show_bug.cgi?id=700148" Best regards, Eckard Klotz. Am 07.05.2015 um 22:57 schrieb Timo Marjoniemi: > Hi, > > A filter for Google Protocol buffers files I've written > (https://sourceforge.net/p/proto2cpp/) does not work from Doxygen > v1.8.8 onward and so far I haven't been able to make it work. It does > work with v1.8.7 and several older versions (oldest I've tested is > 1.8.1.1). > Has anyone else encountered such problems with custom Doxygen filters? > Any clues what could be the root cause and how to fix it? > > Thanks in advance, > TimoM > > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > > > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop |
|
From: Timo M. <tim...@gm...> - 2015-05-07 20:57:28
|
Hi, A filter for Google Protocol buffers files I've written ( https://sourceforge.net/p/proto2cpp/) does not work from Doxygen v1.8.8 onward and so far I haven't been able to make it work. It does work with v1.8.7 and several older versions (oldest I've tested is 1.8.1.1). Has anyone else encountered such problems with custom Doxygen filters? Any clues what could be the root cause and how to fix it? Thanks in advance, TimoM |
|
From: Bastiaan V. <Bas...@SA...> - 2015-04-28 09:09:19
|
+1 for generated labels to figures and tables. Just wanted to chime in, in support of this feature request. We do our 400 page manual [1] in Doxygen, and referencing to figures is the one thing that we still miss. All our figures are in \figure syntax, so I’d hope an implementation would support that as well. I’d suggest using the stem of the figure file name as the label name. That way, the syntax for images can stay the same. So, in the below example, \ref fig_growth_vs_time would generate a link to the figure (top of the figure, not the caption at the bottom). Tables in HTML format could probably be labeled using the <A name=“,,,”> named anchor, for LaTeX output as well. Best regards, Bastiaan Veelo. [1] http://www.sarc.nl/pias/manuals/manuals-pias-fairway <http://www.sarc.nl/pias/manuals/manuals-pias-fairway> > On 28 Apr 2015, at 01:26, Gavin Radolan <ga...@ta...> wrote: > > Hello, > > I'm using Doxygen to create a reference manual. Input is markdown. Output is LaTeX and html. Currently using Doxygen 1.8.8. > > I'm wondering if there are any plans for Doxygen to support automatic numbering of figures and tables, with referencing capability from the markdown text? > > For example, behavior similar to the @section command's LaTeX output. But separate enumeration for figures and another separate enumeration for tables. And with the enumeration showing up in both LaTeX and html output. > > Syntax might be something like this, > > At the figure: > >  > > or maybe > >  > @figure fig_name "Growth rate vs time" > > The first example is preferable for it's simplicity, but maybe it's difficult to have ![Caption text ] used for multiple purposes... > > At the table: > > @table tab_name Growth rate data 2009 - 2014 > > | Year | Growth Rate| > |:------:|-----------------:| > | 2009| 0.3245 | > ....whatever.... > > In the body text: > > The growth rate for the last five years is shown in \ref tab_name. As can be seen in /ref fig_name, the growth rate is logarithmic. > > In the generated pdf/html: > > The growth rate for the last five years is shown in Table 93: Growth rate 2009 - 2014. As can be seen in Figure 125: Growth rate vs time, the growth rate is logarithmic. > > So "Figure N" and "Table M" are automatically generated and pre-pended to the caption for each figure/table in the document. And you can link to any figure or table anyplace in the doc using a /ref tag. > > I've noticed some users implement similar functionality with post-processing scripts or other "add-on" tools, such as doxynum. I could do likewise, but first, wanted to ask whether or not there are plans to have such functionality "built-in" to Doxygen - and if so, approximately when? > > Kind regards, > > Gavin Radolan > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop |
|
From: Gavin R. <ga...@ta...> - 2015-04-27 23:26:38
|
Hello,
I'm using Doxygen to create a reference manual. Input is markdown. Output
is LaTeX and html. Currently using Doxygen 1.8.8.
I'm wondering if there are any plans for Doxygen to support automatic
numbering of figures and tables, with referencing capability from the
markdown text?
For example, behavior similar to the @section command's LaTeX output. But
separate enumeration for figures and another separate enumeration for
tables. And with the enumeration showing up in both LaTeX and html output.
Syntax might be something like this,
At the figure:
or maybe
@figure fig_name "Growth rate vs time"
The first example is preferable for it's simplicity, but maybe it's
difficult to have ![Caption text ] used for multiple purposes...
At the table:
@table tab_name Growth rate data 2009 - 2014
| Year | Growth Rate|
|:------:|-----------------:|
| 2009| 0.3245 |
....whatever....
In the body text:
The growth rate for the last five years is shown in \ref tab_name. As can
be seen in /ref fig_name, the growth rate is logarithmic.
In the generated pdf/html:
The growth rate for the last five years is shown in Table 93: Growth rate
2009 - 2014. As can be seen in Figure 125: Growth rate vs time, the growth
rate is logarithmic.
So "Figure N" and "Table M" are automatically generated and pre-pended to
the caption for each figure/table in the document. And you can link to any
figure or table anyplace in the doc using a /ref tag.
I've noticed some users implement similar functionality with
post-processing scripts or other "add-on" tools, such as doxynum. I could
do likewise, but first, wanted to ask whether or not there are plans to
have such functionality "built-in" to Doxygen - and if so, approximately
when?
Kind regards,
Gavin Radolan
|
|
From: Michael S. <ms...@re...> - 2015-04-23 12:04:12
|
On 23.04.2015 00:00, johnk wrote: > I'm getting OT and I've already made changes to my code to use qtools > instead of stdlib, but out of curiosity of portability issues, I went > looking and found the following: > > http://stackoverflow.com/questions/5205491/whats-this-stl-vs-c-standard-library-fight-all-about/5205571#5205571 thanks for the link, so i was being inexcusably sloppy and assumed you meant that the containers/algorithms that comprise the STL were not in the C++ standard library while you actually meant "the STL as originally proposed by SGI back in the day"; sorry for the confusion - now that i understand your point, i fully agree with it :) |
|
From: johnk <jk...@ar...> - 2015-04-22 22:00:43
|
I'm getting OT and I've already made changes to my code to use qtools instead of stdlib, but out of curiosity of portability issues, I went looking and found the following: http://stackoverflow.com/questions/5205491/whats-this-stl-vs-c-standard-library-fight-all-about/5205571#5205571 On 04/07/2015 06:05 AM, Michael Stahl wrote: > On 06.04.2015 19:28, johnk wrote: >> On 04/06/2015 12:10 PM, Dimitri van Heesch wrote: >>> I try to keep doxygen's code very portable. As a result I have avoided using STL. >> I can understand not wanting to use STL, which, despite the name, was >> never really standardized, however the standard C++ library which is > STL is certainly part of the standard, and in particular part of the > "standard C++ library"; the implementations were just buggy for many > years (but nowadays things tend to work). > > 23 Containers library > 23.1 General > 23.2 Container requirements > 23.3 Sequence containers > 23.4 Associative containers > 23.5 Unordered associative containers > 23.6 Container adaptors > > 24 Iterators library > 24.1 General > 24.2 Iterator requirements > 24.3 Header <iterator> synopsis > 24.4 Iterator primitives > 24.5 Iterator adaptors > 24.6 Stream iterators > > 25 Algorithms library > 25.1 General > 25.2 Non-modifying sequence operations > 25.3 Mutating sequence operations > 25.4 Sorting and related operations > 25.5 C library algorithms > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > |
|
From: Dimitri v. H. <do...@gm...> - 2015-04-14 17:40:20
|
> On 13 Apr 2015, at 19:11 , johnk <jk...@ar...> wrote: > > I'd like to link to Doxygen pages from a wiki. Currently, we do that by > generating all the documentation in the top-level directory. This is > less than ideal as it results in over 48000 files in a single > directory. Doxygen allows for the creation of sub-directories to > alleviate this, but the mapping doesn't seem straight-forward. > > Several javascript files are generated by Doxygen that look like they > could provide a look-up table, but I've been investigating hierarchy.js > and have been unable to figure out how it's generated, nor how it's > used. Given my inability to discover how the file is generated and > used, I'm a little reluctant to make use of it for fear it might > disappear in some future release. I've been poking at this for a while > now, and haven't uncovered any answers yet. > > Is there a known method for linking to the appropriate document using > the name of the class/file/namespace/etc. as a reference? This has been discussed before, see: http://doxygen.10944.n7.nabble.com/how-to-link-to-a-doxygen-page-td1089.html Regards, Dimitri |
|
From: johnk <jk...@ar...> - 2015-04-13 17:11:56
|
I'd like to link to Doxygen pages from a wiki. Currently, we do that by generating all the documentation in the top-level directory. This is less than ideal as it results in over 48000 files in a single directory. Doxygen allows for the creation of sub-directories to alleviate this, but the mapping doesn't seem straight-forward. Several javascript files are generated by Doxygen that look like they could provide a look-up table, but I've been investigating hierarchy.js and have been unable to figure out how it's generated, nor how it's used. Given my inability to discover how the file is generated and used, I'm a little reluctant to make use of it for fear it might disappear in some future release. I've been poking at this for a while now, and haven't uncovered any answers yet. Is there a known method for linking to the appropriate document using the name of the class/file/namespace/etc. as a reference? |
|
From: johnk <jk...@ar...> - 2015-04-07 17:43:02
|
On 04/07/2015 02:30 AM, Roger Lucas (rogerluc) wrote: > We use Doxygen extensively and have recently added PlantUML to allow embedded > class diagram images. > > The instructions provided by PlantUML work well - we get the correct images > created and they get referenced in the Doxygen HTML output so that you get the > images inline with the documentation. > > What more were you trying to do? > Embedded PlantUML diagrams work great, yes, but what I wanted was to have PlantUML class diagrams generated automatically from the code base we're documenting. Doxygen already does this using Graphviz, but I'm not overly fond of how it looks. I'd like to provide the option of generating the same (more or less) graphs using PlantUML even if it doesn't support image mapping. In short, I want dynamic UML class diagrams using PlantUML in addition to the already supported static diagrams. |
|
From: Michael S. <ms...@re...> - 2015-04-07 11:05:57
|
On 06.04.2015 19:28, johnk wrote: > On 04/06/2015 12:10 PM, Dimitri van Heesch wrote: >> I try to keep doxygen's code very portable. As a result I have avoided using STL. > I can understand not wanting to use STL, which, despite the name, was > never really standardized, however the standard C++ library which is STL is certainly part of the standard, and in particular part of the "standard C++ library"; the implementations were just buggy for many years (but nowadays things tend to work). 23 Containers library 23.1 General 23.2 Container requirements 23.3 Sequence containers 23.4 Associative containers 23.5 Unordered associative containers 23.6 Container adaptors 24 Iterators library 24.1 General 24.2 Iterator requirements 24.3 Header <iterator> synopsis 24.4 Iterator primitives 24.5 Iterator adaptors 24.6 Stream iterators 25 Algorithms library 25.1 General 25.2 Non-modifying sequence operations 25.3 Mutating sequence operations 25.4 Sorting and related operations 25.5 C library algorithms |
|
From: Roger L. (rogerluc) <rog...@ci...> - 2015-04-07 07:30:52
|
We use Doxygen extensively and have recently added PlantUML to allow embedded class diagram images. The instructions provided by PlantUML work well - we get the correct images created and they get referenced in the Doxygen HTML output so that you get the images inline with the documentation. What more were you trying to do? - Roger -----Original Message----- From: johnk [mailto:jk...@ar...] Sent: 02 April 2015 18:22 To: dox...@li... Subject: [Doxygen-develop] Working on adding PlantUML class diagrams I'm interested in (and have started) modifying the Doxygen code to allow for the generation of class diagrams using PlantUML, but I wanted to get some input before I got too far in. My current thinking is just to have the diagrams generated as an aside to the Graphviz diagrams. I mostly wanted a tool to automatically generate nice UML class diagrams from my code. I'm already using Doxygen and it has a framework for doing this already. PlantUML does not support image mapping so the nice links that are generated in Graphviz simply aren't available. That said, others probably have a different opinion on how best to utilize PlantUML. As such, I'm open to suggestions as to how best to utilize the tool inside Doxygen (beyond the already available embedded diagrams). I should probably mention that I'm only inclined to add support for PlantUML class diagrams - it's not really suited for the other types of diagrams that Doxygen generates. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Doxygen-develop mailing list Dox...@li... https://lists.sourceforge.net/lists/listinfo/doxygen-develop |
|
From: johnk <jk...@ar...> - 2015-04-06 17:28:54
|
On 04/06/2015 12:10 PM, Dimitri van Heesch wrote: > I try to keep doxygen's code very portable. As a result I have avoided using STL. I can understand not wanting to use STL, which, despite the name, was never really standardized, however the standard C++ library which is part of the C++ standard definition should be portable and consistent. Of course you noted that, though I thought stdc++ was part of the standard before rev 11. Boost I can certainly understand leaving out. I'm definitely not a fan of adding additional dependencies that are outside of a standard build environment (whatever that means :-). I had assumed that Doxygen had predated stdc++, but thought maybe there might be some momentum to "update" it. > Also STL uses exceptions whereas doxygen doesn't. So if any STL class throws an exception, > doxygen will crash. Fair enough. > So what do you need that is in STL, but not in qtools? I disagree with the assertion that the standard C++ library (of which STL is a predecessor) is not portable, but it's your baby. It's not so much that qtools doesn't have things that are unavailable, for me it's partially a matter of familiarity. Maybe even wholly. I find qtools confusing with its multiple implementations of string classes and so on. Qtools does a lot of the same stuff as stdc++ but I find the stdc++ implementation cleaner and more thorough, personally. I can certainly use the qtools, though it'd be helpful to get some clarification as to when to use "QGString" and when to use "QCString". The documentation of the former is just "This is an alternative implementation of QCString", which isn't terribly helpful. Also if you happen to have an emacs style setting that you can pass on so I can keep the formatting consistent, I'd appreciate it :-) |
|
From: Dimitri v. H. <do...@gm...> - 2015-04-06 17:11:03
|
Hi Johnk, > On 06 Apr 2015, at 16:58 , johnk <jk...@ar...> wrote: > > Dimitri, as I work on some enhancements for Doxygen, is there any reason > I shouldn't use std as opposed to "qtools"? The first enhancement I > did, some additional capabilities for markdown tables (column and row > spans), I used std. The PlantUML enhancements I'm working on would > really benefit from std, but I wanted to be sure there wasn't a reason > not to implement things that way. I try to keep doxygen's code very portable. As a result I have avoided using STL. You can of course say: but hey STL is *the* standard library supported by any compiler. While that somewhat true it wasn't very well supported back in the days (remember I started with doxygen in 1997) and still it is tempting to use stuff (like C++11 or boost) that is not generally supported on all platforms or drags in additional dependencies. Also STL uses exceptions whereas doxygen doesn't. So if any STL class throws an exception, doxygen will crash. My claim is that it is still hard to write portable code using STL. I'm not alone: see also the Mozilla guidelines: https://developer.mozilla.org/en-US/docs/Mozilla/C++_Portability_Guide So what do you need that is in STL, but not in qtools? Regards, Dimitri |
28 messages has been excluded from this view by a project administrator.
