doxygen-develop Mailing List for Doxygen (Page 13)
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: Karl R. <me...@ka...> - 2013-01-14 20:57:15
|
Hi, a patch for enabling/disabling line numbers in \example listings is attached. Using the switch EXAMPLE_WITH_LINES = [YES/NO] one can now toggle line numbers. The default is 'NO' in order to be consistent with the current behavior. Best regards, Karli |
From: Rene Z. <r.z...@fr...> - 2013-01-09 20:33:58
|
Hi Dimitri, I have updated the bur tracker #689713 with: Same problem under doxygen 1.8.3. As a test I compiled a version with parameter schowLineNumbers in function TclLanguageScanner::parseCode() set to TRUE and voila, everything was OK. It is used as variable tcl.code_linenumbers in function tcl_codify(). May be you can give me now some help to fix it. It seems for me a problem with the formatting of the text. Reagrds rene |
From: anirudh s. s. <she...@gm...> - 2012-12-14 07:04:16
|
Hi, A while back (more then a year) I wanted to develop and extend the then existing support for SQL in doxygen but I it feel through. But now have decided to work on it. Though slowly but steadi Will be doing this apart from my day job for eBay so it would take a while. This email is to invite collaborations and to get to know of any update if happened in this realm. Regards, Anirudh shekhawat -- Sent from my nexus. Blame it for the typos. |
From: Albert <alb...@gm...> - 2012-12-13 20:25:56
|
Hi Ken, I did a small test with a FORTRAN file and when the extension is in lowercase the preprocessor is not invoked. When the extension is in uppercase the preprocessor is invoked, but in your documentation you will find of course INTEGER*1 instead of BYTE. This is not really documented as far as I know, but in the code, fortranscanner.l, the following code is present: bool FortranLanguageScanner::needsPreprocessing(const QCString &extension) { return extension!=extension.lower(); // use preprocessor only for upper case extensions } Albert On Wed, Dec 12, 2012 at 6:40 PM, Ken Kazinski <kjk...@ya...> wrote: > Hi Albert, > > I am using Doxygen 1.8.2. I tried to set the predefined and Expand_as_defined to: > > PREDEFINED = BYTE=INTEGER*1 \ > STRUCTRUE=TYPE > > As these are not function macro the documentation leads me to believe that they are not being replaced. > > Thanks for all the help. > > > > --- On Wed, 12/12/12, Albert <alb...@gm...> wrote: > >> From: Albert <alb...@gm...> >> Subject: Re: [Doxygen-users] Fortran Extensions >> To: "Ken Kazinski" <kjk...@ya...> >> Cc: dox...@li... >> Date: Wednesday, December 12, 2012, 10:13 AM >> Hi Ken, >> >> Which version of Doxygen are you using? >> By head I don't know in which version Double Complex entered >> but it is >> in (I found it useful and commonly used). >> The BYTE and STRUCTURE are not in. For BYTE it is easy to >> add and >> shouldn't have side effects , STRUCTURE is a different >> story. >> For BYTE probably an PREDEFINE of INTEGER*1 would work as >> well. For >> the STRUCTURE the best way would be to use a FILER. >> >> Albert >> >> On Wed, Dec 12, 2012 at 3:01 PM, Ken Kazinski <kjk...@ya...> >> wrote: >> > Intel Fortran compilers added a number of extension to >> F77 & F90. >> > >> > I am struggling with getting them to documnet correctly >> in doxygen. The type declarations Double Complex and >> Byte and the key word structure. >> > >> > Is there a way to tell doxygen that these are key words >> without recompiling doxygen with these extensions >> included. It seems that it would be easy to add these >> keywords into the fortranscanner.l and fortancode.l files >> and recompile but things like this that seem easy turn out >> to have a number of unforseen consiquenses. >> > >> > Thanks. >> > >> > >> ------------------------------------------------------------------------------ >> > LogMeIn Rescue: Anywhere, Anytime Remote support for >> IT. Free Trial >> > Remotely access PCs and mobile devices and provide >> instant support >> > Improve your efficiency, and focus on delivering more >> value-add services >> > Discover what IT Professionals Know. Rescue delivers >> > http://p.sf.net/sfu/logmein_12329d2d >> > _______________________________________________ >> > Doxygen-users mailing list >> > Dox...@li... >> > https://lists.sourceforge.net/lists/listinfo/doxygen-users >> |
From: Ken K. <kjk...@ya...> - 2012-12-12 17:40:32
|
Hi Albert, I am using Doxygen 1.8.2. I tried to set the predefined and Expand_as_defined to: PREDEFINED = BYTE=INTEGER*1 \ STRUCTRUE=TYPE As these are not function macro the documentation leads me to believe that they are not being replaced. Thanks for all the help. --- On Wed, 12/12/12, Albert <alb...@gm...> wrote: > From: Albert <alb...@gm...> > Subject: Re: [Doxygen-users] Fortran Extensions > To: "Ken Kazinski" <kjk...@ya...> > Cc: dox...@li... > Date: Wednesday, December 12, 2012, 10:13 AM > Hi Ken, > > Which version of Doxygen are you using? > By head I don't know in which version Double Complex entered > but it is > in (I found it useful and commonly used). > The BYTE and STRUCTURE are not in. For BYTE it is easy to > add and > shouldn't have side effects , STRUCTURE is a different > story. > For BYTE probably an PREDEFINE of INTEGER*1 would work as > well. For > the STRUCTURE the best way would be to use a FILER. > > Albert > > On Wed, Dec 12, 2012 at 3:01 PM, Ken Kazinski <kjk...@ya...> > wrote: > > Intel Fortran compilers added a number of extension to > F77 & F90. > > > > I am struggling with getting them to documnet correctly > in doxygen. The type declarations Double Complex and > Byte and the key word structure. > > > > Is there a way to tell doxygen that these are key words > without recompiling doxygen with these extensions > included. It seems that it would be easy to add these > keywords into the fortranscanner.l and fortancode.l files > and recompile but things like this that seem easy turn out > to have a number of unforseen consiquenses. > > > > Thanks. > > > > > ------------------------------------------------------------------------------ > > LogMeIn Rescue: Anywhere, Anytime Remote support for > IT. Free Trial > > Remotely access PCs and mobile devices and provide > instant support > > Improve your efficiency, and focus on delivering more > value-add services > > Discover what IT Professionals Know. Rescue delivers > > http://p.sf.net/sfu/logmein_12329d2d > > _______________________________________________ > > Doxygen-users mailing list > > Dox...@li... > > https://lists.sourceforge.net/lists/listinfo/doxygen-users > |
From: Albert <alb...@gm...> - 2012-12-12 15:13:54
|
Hi Ken, Which version of Doxygen are you using? By head I don't know in which version Double Complex entered but it is in (I found it useful and commonly used). The BYTE and STRUCTURE are not in. For BYTE it is easy to add and shouldn't have side effects , STRUCTURE is a different story. For BYTE probably an PREDEFINE of INTEGER*1 would work as well. For the STRUCTURE the best way would be to use a FILER. Albert On Wed, Dec 12, 2012 at 3:01 PM, Ken Kazinski <kjk...@ya...> wrote: > Intel Fortran compilers added a number of extension to F77 & F90. > > I am struggling with getting them to documnet correctly in doxygen. The type declarations Double Complex and Byte and the key word structure. > > Is there a way to tell doxygen that these are key words without recompiling doxygen with these extensions included. It seems that it would be easy to add these keywords into the fortranscanner.l and fortancode.l files and recompile but things like this that seem easy turn out to have a number of unforseen consiquenses. > > Thanks. > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users |
From: Ken K. <kjk...@ya...> - 2012-12-12 14:16:04
|
Intel Fortran compilers added a number of extension to F77 & F90. I am struggling with getting them to documnet correctly in doxygen. The type declarations Double Complex and Byte and the key word structure. Is there a way to tell doxygen that these are key words without recompiling doxygen with these extensions included. It seems that it would be easy to add these keywords into the fortranscanner.l and fortancode.l files and recompile but things like this that seem easy turn out to have a number of unforseen consiquenses. I asked in the users forum also but I thought it would help to ask here also. Thanks. |
From: Mancip-MdS <Mar...@Ma...> - 2012-12-12 09:05:08
|
Hello Dimitri I have forget class file translator.h in my previous patch (from 2012-08-31 11:47). Here is the right patch for keep consistency with fortran 90 language. Martial -- @ ================= @ @ Dr Martial MANCIP @ @ ================= @ @ Ingénieur Visualisation @ @ 016 908 3919 - 0610903344 @ @ Maison de la Simulation @ @ CEA/Saclay, bât. 565, PC 190 @ @ 91191 Gif-sur-Yvette CEDEX @ @ _____________________________ @ |
From: Rene Z. <r.z...@fr...> - 2012-12-05 16:31:23
|
Hi Dimitri, the INLINE_SOURCES problem is because of too many </div> tags in the generated html file. I have some spare time in the next weeks and could work on it. Could you give me some advice where to start? Thank you, rene |
From: Paweł W. <pav...@gm...> - 2012-11-27 12:56:18
|
Hi Petr, I know that there is option with cygwin but I don't have it installed, so the other way look simpler. Download, unpack, set variable and should work. bison version in UnxUtils is: d:\Tools\UnxUtils\usr\local\wbin>bison --version GNU Bison version 1.28 inside gnuwin32 is: bison (GNU Bison) 2.4.1 and that work fine. Regards, Paweł 2012/11/26 Petr Prikryl <Pr...@sk...>: > Hi Paweł, > > I personally use cygwin. The cygwin is mentioned in the doc. > I did not update it for a while. The bison and flex show... > > c:\cygwin\bin>bison --version > bison (GNU Bison) 2.4.2 > Written by Robert Corbett and Richard Stallman. > > Copyright (C) 2010 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > c:\cygwin\bin>flex --version > flex 2.5.35 > > Besides that, I do compile doxygen using Visual Studio 2008. > > Have a nice day, > Petr > >> -----Original Message----- >> From: Paweł Wiśniewski [mailto:pav...@gm...] >> Sent: Thursday, November 22, 2012 10:47 AM >> To: Doxygen-develop >> Subject: [Doxygen-develop] Build on Windows (fix for web site) >> >> Hallo, >> >> I was trying to build doxygen on windows according to description from >> web page (http://www.stack.nl/~dimitri/doxygen/install.html) with >> visual studio. >> Unfortunately it is not working with >> http://sourceforge.net/projects/unxutils, bison is too old. >> it is better to use flex and bison from >> http://gnuwin32.sourceforge.net/packages.html >> >> With this package, compiling is no problem in visual studio. >> >> If you can change web page it could be easier for other to build on >> windows. >> >> Best regards >> Paweł >> >> ----------------------------------------------------------------------- >> ------- >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, >> vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> Doxygen-develop mailing list >> Dox...@li... >> https://lists.sourceforge.net/lists/listinfo/doxygen-develop |
From: Petr P. <Pr...@sk...> - 2012-11-26 09:43:43
|
Hi Paweł, I personally use cygwin. The cygwin is mentioned in the doc. I did not update it for a while. The bison and flex show... c:\cygwin\bin>bison --version bison (GNU Bison) 2.4.2 Written by Robert Corbett and Richard Stallman. Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. c:\cygwin\bin>flex --version flex 2.5.35 Besides that, I do compile doxygen using Visual Studio 2008. Have a nice day, Petr > -----Original Message----- > From: Paweł Wiśniewski [mailto:pav...@gm...] > Sent: Thursday, November 22, 2012 10:47 AM > To: Doxygen-develop > Subject: [Doxygen-develop] Build on Windows (fix for web site) > > Hallo, > > I was trying to build doxygen on windows according to description from > web page (http://www.stack.nl/~dimitri/doxygen/install.html) with > visual studio. > Unfortunately it is not working with > http://sourceforge.net/projects/unxutils, bison is too old. > it is better to use flex and bison from > http://gnuwin32.sourceforge.net/packages.html > > With this package, compiling is no problem in visual studio. > > If you can change web page it could be easier for other to build on > windows. > > Best regards > Paweł > > ----------------------------------------------------------------------- > ------- > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, > vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop |
From: Paweł W. <pav...@gm...> - 2012-11-22 10:45:24
|
Hallo, Currently I'm working for German company and they said that there is mistake in date format. Now it is: Die Nov 20 2012 should be: 20.11.2012 Without day and month name, but with two digit for day and month. You can check in http://en.wikipedia.org/wiki/Date_format_by_country I think it will be better if it will be DATE_FORMAT in Doxyfile, than it everyone can change it if standard is not ok. Did you think about using QTranslator instead of current translator? Best regards Paweł |
From: Paweł W. <pav...@gm...> - 2012-11-22 09:47:36
|
Hallo, I was trying to build doxygen on windows according to description from web page (http://www.stack.nl/~dimitri/doxygen/install.html) with visual studio. Unfortunately it is not working with http://sourceforge.net/projects/unxutils, bison is too old. it is better to use flex and bison from http://gnuwin32.sourceforge.net/packages.html With this package, compiling is no problem in visual studio. If you can change web page it could be easier for other to build on windows. Best regards Paweł |
From: Dimitri v. H. <do...@gm...> - 2012-11-15 18:46:39
|
Hi, There are two causes for getting "Out of memory": 1) There is not enough memory in the system to support a project of this size. Solutions: add more memory, or split the project into smaller parts (and link them together with tag files). 2) There is a bug in doxygen which causes it to claim all memory. Without as much as a stack trace (or a reproduction scenario) there is little I can do to help. Regards, Dimitri On Nov 12, 2012, at 15:44 , Kevin McBride <dol...@ao...> wrote: > Dimitri, any ideas on this one? I think that we will need some kind of > huge project sample in a tar/zip to reproduce this bug. > > - Kevin McBride > > -----Original Message----- > From: Toth Norbert <Nor...@ev...> > To: Kevin McBride <dol...@ao...> > Sent: Sat, Nov 10, 2012 1:39 am > Subject: RE: [Doxygen-develop] Memory overrun > > Kevin McBride, > > Sorry, but i don't no provide a stacktrace. The today compilation error > was: > In file ..\qtools\qgarray.cpp, line 229: Out of memory > > I don't undestand this message. How can I decrease the memory > requirement for the doxygen? Is it depent from configuration file? > > Regards, > Norbert > > -----Original Message----- > From: Kevin McBride [mailto:dol...@ao...] > Sent: Friday, November 09, 2012 1:43 PM > To: Toth Norbert; dox...@li... > Subject: Re: [Doxygen-develop] Memory overrun > > Toth Norbert, > > Can you provide us with a stacktrace? That would help us figure out > where the problem lies in Doxygen. > > Thank you, > > - Kevin McBride > > -----Original Message----- > From: Toth Norbert <Nor...@ev...> > To: Doxygen-develop <Dox...@li...> > Sent: Fri, Nov 9, 2012 2:13 am > Subject: [Doxygen-develop] Memory overrun > > Hy all, I have got an error messag and our compilation of big C++ > project terminated. The message:„out of dynamic memory in > doctokenizerYY_create_buffer()” Can somebody tell me what can I do > now? Regards, Norbert > TÓTH--------------------------------------------------------------------- > > --------- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite > for free today: > http://p.sf.net/sfu/appdyn_d2d_nov_______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > > > > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop |
From: Kevin M. <dol...@ao...> - 2012-11-12 14:44:13
|
Dimitri, any ideas on this one? I think that we will need some kind of huge project sample in a tar/zip to reproduce this bug. - Kevin McBride -----Original Message----- From: Toth Norbert <Nor...@ev...> To: Kevin McBride <dol...@ao...> Sent: Sat, Nov 10, 2012 1:39 am Subject: RE: [Doxygen-develop] Memory overrun Kevin McBride, Sorry, but i don't no provide a stacktrace. The today compilation error was: In file ..\qtools\qgarray.cpp, line 229: Out of memory I don't undestand this message. How can I decrease the memory requirement for the doxygen? Is it depent from configuration file? Regards, Norbert -----Original Message----- From: Kevin McBride [mailto:dol...@ao...] Sent: Friday, November 09, 2012 1:43 PM To: Toth Norbert; dox...@li... Subject: Re: [Doxygen-develop] Memory overrun Toth Norbert, Can you provide us with a stacktrace? That would help us figure out where the problem lies in Doxygen. Thank you, - Kevin McBride -----Original Message----- From: Toth Norbert <Nor...@ev...> To: Doxygen-develop <Dox...@li...> Sent: Fri, Nov 9, 2012 2:13 am Subject: [Doxygen-develop] Memory overrun Hy all, I have got an error messag and our compilation of big C++ project terminated. The message:„out of dynamic memory in doctokenizerYY_create_buffer()” Can somebody tell me what can I do now? Regards, Norbert TÓTH--------------------------------------------------------------------- --------- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov_______________________________________________ Doxygen-develop mailing list Dox...@li... https://lists.sourceforge.net/lists/listinfo/doxygen-develop |
From: Kevin M. <dol...@ao...> - 2012-11-09 12:43:21
|
Toth Norbert, Can you provide us with a stacktrace? That would help us figure out where the problem lies in Doxygen. Thank you, - Kevin McBride -----Original Message----- From: Toth Norbert <Nor...@ev...> To: Doxygen-develop <Dox...@li...> Sent: Fri, Nov 9, 2012 2:13 am Subject: [Doxygen-develop] Memory overrun Hy all, I have got an error messag and our compilation of big C++ project terminated. The message:„out of dynamic memory in doctokenizerYY_create_buffer()” Can somebody tell me what can I do now? Regards, Norbert TÓTH--------------------------------------------------------------------- --------- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov_______________________________________________ Doxygen-develop mailing list Dox...@li... https://lists.sourceforge.net/lists/listinfo/doxygen-develop |
From: Toth N. <Nor...@ev...> - 2012-11-09 07:12:57
|
Hy all, I have got an error messag and our compilation of big C++ project terminated. The message: "out of dynamic memory in doctokenizerYY_create_buffer()" Can somebody tell me what can I do now? Regards, Norbert TÓTH |
From: Rene Z. <r.z...@fr...> - 2012-11-04 21:05:42
|
Hi Dimitri, recently I had a tcl user with problems using INLINE_SOURCES and call graphs. 1. Setting CALL_GRAPH and HAVE_DOT but not INLINE_SOURCES does not give call graphs in the generated output. Call graphs are only generated after setting INLINE_SOURCES. Is this intended/documented behaviour? 2. INLINE_SOURCES work correct under 1.8.0 but not under 1.8.2 (probably also not under 1.8.1). Under the later versions the included function source code is not correctly formatted. But the code is correctly formatted in the file code display. There where no changes in the tclscanner.l file from my side. You have added the parseCode() interface the following definition: Definition *searchCtx Could you give me some more information in this issue? Should I add a bug ttracker entry? Here is the text script (file t.tcl): ## @file t.tcl proc foo {} { return } proc bar {} { foo foo foo return } Thank you rene |
From: Kevin M. <dol...@ao...> - 2012-10-31 16:05:27
|
Jan, I'd rather not have a dual boot system as some campuses like Broome Community College consider running Linux as a security breach unless it is part of a class or a club. Unfortunately, none of the courses in my chosen associate degree involve Linux. Sometime in the future, I will get a second laptop and install Linux. At that time, the chosen laptop should have good compatibility with Linux. - Kevin McBride -----Original Message----- From: Jan Ruzicka <jan...@co...> To: Kevin McBride <dol...@ao...> Sent: Wed, Oct 31, 2012 10:08 am Subject: Re: [Doxygen-develop] Obtained a Laptop Hi did you consider a virtual box[1]? It would allow you to have Linux box on Windows box. Modern laptops should be fast enough to have the virtual box running at usable speed. Using Virtual box would allow you to have different OS and configurations. Jan [1] https://www.virtualbox.org/ On Oct 28, 2012, at 12:36 PM, Kevin McBride wrote: > Hello Dimitri, > > Just to let you know, I have finally obtained a laptop. I am waiting > on getting developer tools to make triaging of bugs easier; however, I > should be able to triage some bugs as the windows binary version does > not require that I have developer tools. > > Because of my studies at Broome Community College, I am reluctant to > install Linux on this laptop. I am hoping that one day I can get a > desktop where I can run Linux, perhaps the Fedora distro. > > - Kevin McBride > > > > ------------------------------------------------------------------------- ----- > WINDOWS 8 is here. > Millions of people. Your app in 30 days. > Visit The Windows 8 Center at Sourceforge for all your go to resources. > http://windows8center.sourceforge.net/ > join-generation-app-and-make-money-coding-fast/ > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop Jan Ruzicka Senior Software Engineer Comtech Mobile Datacom Corporation 20430 Century Blvd, Germantown, MD 20874 Office: 240-686-3300 Fax: 240-686-3301 The information contained in this message may be privileged and/or confidential. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please so notify the sender immediately, and delete it and all attachments from your computer and network. |
From: Kevin M. <dol...@ao...> - 2012-10-28 16:37:07
|
Hello Dimitri, Just to let you know, I have finally obtained a laptop. I am waiting on getting developer tools to make triaging of bugs easier; however, I should be able to triage some bugs as the windows binary version does not require that I have developer tools. Because of my studies at Broome Community College, I am reluctant to install Linux on this laptop. I am hoping that one day I can get a desktop where I can run Linux, perhaps the Fedora distro. - Kevin McBride |
From: Philipp M. <phi...@ge...> - 2012-09-30 14:12:28
|
Dimitri van Heesch <do...@gm...> writes: > Hi Philipp, > > On Sep 21, 2012, at 15:26 , Philipp Moeller <phi...@ge...> wrote: > >> Hi, >> >> I'm looking for a way to inject <link rel="canonical" href=""/> tags >> into doxygen HTML output. >> >> The obvious way is to do it in a post-processing, but having the ability >> to access the filename of the currently generated file (incl. it's path >> when CREATE_SUBDIRS is enabled) inside the HTML_HEADER seems like a >> better solution. >> >> It seems to be straight-forward to implement by adding another >> substitution to substituteHtmlKeywords in htmlgen.cpp > > If it is for the header and footer, then yes that would work > (similar to $relpath$, which is the relative path to the root of the documentation set). > >> >> Would it be possible to add something like that? I could provide a patch >> if wanted. That is exactly the way I did it. > Yes please, but I would like to understand what you would be using this for. We serve our documentation in a style like this: https://www.example.com/manual/versionnumber/index.html and always have a special directory https://www.example.com/manual/latest/index.html that always has the documentation of the latest release. To prevent search engines from showing links to specific versions of the documentation we use a <link rel="canonical"> tag to always point to the version found at latest. Hope this makes the use case clearer. Cheers, Philipp |
From: Dimitri v. H. <do...@gm...> - 2012-09-30 08:18:04
|
Hi Philipp, On Sep 21, 2012, at 15:26 , Philipp Moeller <phi...@ge...> wrote: > Hi, > > I'm looking for a way to inject <link rel="canonical" href=""/> tags > into doxygen HTML output. > > The obvious way is to do it in a post-processing, but having the ability > to access the filename of the currently generated file (incl. it's path > when CREATE_SUBDIRS is enabled) inside the HTML_HEADER seems like a > better solution. > > It seems to be straight-forward to implement by adding another > substitution to substituteHtmlKeywords in htmlgen.cpp If it is for the header and footer, then yes that would work (similar to $relpath$, which is the relative path to the root of the documentation set). > > Would it be possible to add something like that? I could provide a patch > if wanted. Yes please, but I would like to understand what you would be using this for. Regards, Dimitri |
From: Philipp M. <phi...@ge...> - 2012-09-21 19:28:28
|
Hi, I'm looking for a way to inject <link rel="canonical" href=""/> tags into doxygen HTML output. The obvious way is to do it in a post-processing, but having the ability to access the filename of the currently generated file (incl. it's path when CREATE_SUBDIRS is enabled) inside the HTML_HEADER seems like a better solution. It seems to be straight-forward to implement by adding another substitution to substituteHtmlKeywords in htmlgen.cpp Would it be possible to add something like that? I could provide a patch if wanted. Cheers, Philipp |
From: Vaclav P. <wen...@gm...> - 2012-09-04 10:53:45
|
Hi, I get this warning reached end of comment while inside a @code block; check for missing @endcode tag! The python docs string with wrong tag is here (nothing special): """!Some text... @code >>> some code... @code """ At some other places missing @endcode just caused a warning and documentation is generated. But here Doxygen is just doing something but without any output. Maybe it is a bug, but I'm no able to reproduce it with minimal example (but you can download the source code if you want). It happens only with the 1.8.1.2 and 1.8.2, not with the 1.6.3. For user solution is simple, just repair markup. But there is probably some problem because Doxygen should end with error or just go over this warning (like previous versions does). Vaclav |
From: Mancip-MdS <Mar...@Ma...> - 2012-08-31 11:47:22
|
Hello everyone In fortran, internal namespaces are named "Module". In the code, trModules give the same name for those fortran namespaces and for "module" groups. Then the output is wrong as in group section, we may see group names and not "module" ones. I have added trGroups translation for all languages (I have kept "modules" ones when I don't know the group exact translation). For the global coherence of the code, all "group" items may be renamed as trGroup-something and all namespace "module" for Fortran may keep name "module". Then trModulesDescription() may be renamed trGroupsDescription() and trModules() renamed trGroups(). brief of transformation in the patch : trModules() -> trGroups() trModulesDescription() -> trGroupsDescription() Add new trGroups(), trGroupsIndex(), trGroupDocumentation(), trGroupsDescription() in english and french translators. sed command for modification of translator_*.h : {{{ sed -e 's/QCString trModules()/QCString trGroups()/' -e 's/QCString trModulesDescription()/QCString trGroupsDescription()/' -e 's/* index of all groups./* index of all modules (Fortran)./' -e 's/* the documentation of all groups./* the documentation of all modules (Fortran)./' -i translator_*.h }}} regards -- @ ================= @ @ Dr Martial MANCIP @ @ ================= @ @ Ingénieur Visualisation @ @ 016 908 1752 - 0610903344 @ @ Maison de la Simulation @ @ bat. 709, Orme des Meurisiers @ @ CEA Saclay @ @ 91191 Gif sur Yvette cedex @ @ _____________________________ @ |