Thread: [Doxygen-users] Doxygen-1.2.13.1 in CVS
Brought to you by:
dimitri
From: Dimitri v. H. <di...@st...> - 2002-01-05 10:36:16
|
Hi, Due to some problems in the previous release, I decided to put out a new one, with the following changelog: ---------------------------------------------------------------------------- + BUG: Links to grouped members were broken. + BUG: The Module index was broken in HTML and subgroups were still not sorted properly. + BUG: Selecting a non-default language was not possible in doxywizard (thanks to Heiko Schaefer for the patch). + BUG: Ending a dash-style list was not possible by starting a new paragraph anymore. + BUG: Fixed "exceptions" tag mismatch in the XML output. + BUG: extern "C" blocks inside source files incorrectly included header files during preprocessing. + BUG: Compiling doxywizard on Unix with Qt-3.x didn't work because doxycfg was linked with qtools from Qt-2.x. + BUG: Fixed potential memory corruption when generation the graphical class hierarchy (nodes were deleted more than once). + ADD: Added support for multi-method declarations such as: int func1(),func2(); + ADD: Included updated DTD for validating the XML output produced by doxygen, thanks to Angelo Hulshout. + ADD: Included support for Japanese-ShiftJIS translation, thanks to Ryunosuke Sato. + ADD: Included update for Slovak translator, thanks to Stanislav Kudlac. + ADD: Thanks to a patch by Pascal Flammant tables in the documentation can now have captions using <caption> ... </caption> within a table definition. + ADD: A dash-style list can now be ended without ending the paragraph. See the list-section of the documentation for an example. ---------------------------------------------------------------------------- Enjoy, Dimitri |
From: Jerzy K. <je...@wn...> - 2002-01-05 16:01:37
|
I use doxygen 1.2.13.1 on w2k prof. There seem to be a small inconsistency around the FILE_PATTERNS setting. 1. Problem one: In the config file in the description of the setting there is a list of the tested patterns if the setting is left blank. It goes: #If left blank the following patterns are tested: # *.c *.cc *.cxx *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp # *.h++ *.idl That list doesn't seem to be complete. For example it doesn't list the *.cpp, yet that pattern is tested and the files with .cpp extension are properly documented. It would be nice to have a complete list of the tested patterns thought since that contributes to the decision whether to leave the setting blank or to actually fill it in. In the documentation however, it states: FILE_PATTERNS If the value of the INPUT tag contains directories, you can use the FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and *.h ) to filter out the source-files in the directories. If left blank all files are included (i.e. wildcard *). Where it says that all files are included, that is not correct also... 2. Problem two: While at it - it would be just great if the default pattern also contained the *.odl file pattern together with already present *.idl. If that was the case I would not have to list all the patterns just to apped the .odl files. Alternatively, is there a way append the file patterns to the default list instead of ovewriting it? If not, perhaps something like that: FILE_PATTERNS = $(FILE_PATTERNS) value [value, ...] Where $(FILE_PATTERNS) would be a variable defined internally by doxygen for the default settings. Thanks and Best Regards, Jerzy |
From: Dimitri v. H. <di...@st...> - 2002-01-05 16:38:02
|
On Sun, Jan 06, 2002 at 12:09:41AM +0800, Jerzy Kaczorowski wrote: > I use doxygen 1.2.13.1 on w2k prof. There seem to be a small inconsistency > around the FILE_PATTERNS setting. > > 1. Problem one: In the config file in the description of the setting there > is a list of the tested patterns if the setting is left blank. It goes: > > #If left blank the following patterns are tested: > # *.c *.cc *.cxx *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx > *.hpp > # *.h++ *.idl > > That list doesn't seem to be complete. For example it doesn't list the > *.cpp, yet that pattern is tested and the files with .cpp extension are > properly documented. It would be nice to have a complete list of the tested > patterns thought since that contributes to the decision whether to leave the > setting blank or to actually fill it in. > > In the documentation however, it states: > FILE_PATTERNS > If the value of the INPUT tag contains directories, you can use the > FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and > *.h ) to filter out the source-files in the directories. If left blank all > files are included (i.e. wildcard *). > > Where it says that all files are included, that is not correct also... I'll correct these inconsistencies. > > 2. Problem two: While at it - it would be just great if the default pattern > also contained the *.odl file pattern together with already present *.idl. I'll add it. > If that was the case I would not have to list all the patterns just to apped > the .odl files. Alternatively, is there a way append the file patterns to > the default list instead of ovewriting it? If not, perhaps something like > that: > > FILE_PATTERNS = $(FILE_PATTERNS) value [value, ...] Normally += can be used for this. But the way it is implemented now, the default patterns are added afterwards, and only if the FILE_PATTERNS tag is empty, so this wouldn't work. Regards, Dimitri |