Thread: [Doxygen-develop] Patch against SVN trunk
Brought to you by:
dimitri
From: Brendon C. <br...@ch...> - 2007-11-04 03:57:56
Attachments:
edoc.patch
|
Hi doxygen devs, I have attached a patch for Doxygen that provides some features described below. I was wondering if a doxygen dev could look over these changes and commit them to SVN if they find no problems with them? The patch was created simply with: svn diff > ../edoc.patch Please let me know if there are any problems with these changes or if you dont think they should be accepted into doxygen what i could change to allow that or why. If you need any more information about this patch please let me know. There is also a previous post of mine on doxygen-users (Wrong place for it i just realised) which describes a set of similar patches i made against doxygen ver 1.5.1. This has some examples as to what this patch achieves. http://sourceforge.net/mailarchive/forum.php?thread_name=46CF99DC.70307%40christian.net&forum_name=doxygen-users The main purpose for it is so that doxygen can correctly parse files that are generated by EDoc++ and produce documentation that contains accurate and detailed information about exception propagation through C++ code in addition to its normal API documentation. However these patches are for functionality that is not specific to EDoc++. For more information on EDoc++ see: http://edoc.sourceforge.net/ Thanks, Brendon. * Added DESTDIR install capability to build * Added function for comparing two types taking default template parameters into account (Not a perfect match but does a best effort match using text comparisons and data existing in doxygen). * Modified matchArgument2() to match function prototypes taking template types into acount. * Modified processing of input files to ocurr in the order specified in the configuration file instead of in alphabetical order. This allows the user to determine the order in which appended documentation ocurrs when a single funciton has multiple blocks of documentation by ensuring that the file which contains the documentation to be first is listed in the configuration file before a file whose documentation the user wishes to come afterwards. |
From: Dimitri v. H. <do...@gm...> - 2007-11-05 20:23:07
|
Hi Brendon, Thanks for your patch. I will look into it, but it would help me if you could also submit a bug report (with severity set to enhancement) with the changelog and attach the patch. That way I do not forget to include it. It also helps you, as you will be notified when the patch is included. Regards, Dimitri On 11/4/07, Brendon Costa <br...@ch...> wrote: > > Hi doxygen devs, > > I have attached a patch for Doxygen that provides some features > described below. I was wondering if a doxygen dev could look over these > changes and commit them to SVN if they find no problems with them? > > The patch was created simply with: svn diff > ../edoc.patch > > Please let me know if there are any problems with these changes or if > you dont think they should be accepted into doxygen what i could change > to allow that or why. > > If you need any more information about this patch please let me know. > There is also a previous post of mine on doxygen-users (Wrong place for > it i just realised) which describes a set of similar patches i made > against doxygen ver 1.5.1. This has some examples as to what this patch > achieves. > > > http://sourceforge.net/mailarchive/forum.php?thread_name=46CF99DC.70307%40christian.net&forum_name=doxygen-users > > The main purpose for it is so that doxygen can correctly parse files > that are generated by EDoc++ and produce documentation that contains > accurate and detailed information about exception propagation through > C++ code in addition to its normal API documentation. However these > patches are for functionality that is not specific to EDoc++. > > For more information on EDoc++ see: > http://edoc.sourceforge.net/ > > Thanks, > Brendon. > > > > * Added DESTDIR install capability to build > > * Added function for comparing two types taking default template > parameters into account (Not a perfect match but does a best effort > match using text comparisons and data existing in doxygen). > > * Modified matchArgument2() to match function prototypes taking template > types into acount. > > * Modified processing of input files to ocurr in the order specified in > the configuration file instead of in alphabetical order. This allows the > user to determine the order in which appended documentation ocurrs when > a single funciton has multiple blocks of documentation by ensuring that > the file which contains the documentation to be first is listed in the > configuration file before a file whose documentation the user wishes to > come afterwards. > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > > > |
From: Brendon C. <br...@ch...> - 2007-11-07 10:37:39
|
Hi Dimitri, I submitted a bug (Though made a few mistakes in the process). There was some problem with my internet connection and although i only submitted once there are three consecutive bugs listed in the database for this item. I have marked them as duplicates. Sorry about that. Also when initially submitting the report, there was no space to attach the patch file so i included it in the text. Turns out i was able to attach it after the bug was created and have done so. One last issue. It will not let me add PATCH as a keyword as described on the bug reports page: http://www.stack.nl/~dimitri/doxygen/trouble.html#bug_reports The bug link can be found below: http://bugzilla.gnome.org/show_bug.cgi?id=494519 Also do you want a changelog entry as text in the bug report or attach a new file: changelog with just the applicable entry? Sorry for the issues. I am not familiar with bugzilla or at least that configuration of it and made a few blunders :-) Thanks, Brendon. > Thanks for your patch. > > I will look into it, but it would help me if you could also submit > a bug report (with severity set to enhancement) with the changelog and > attach the patch. That way I do not forget to include it. > It also helps you, as you will be notified when the patch is included. > > Regards, > Dimitri |