Replies: 2 comments 1 reply
-
I tried with a small example an compared the HTML output, an only, as expected, the contents changed Doxyfile
Initial file
Adjusted file
Example with adjusted file: example.tar.gz when you have an example where the file names change:
|
Beta Was this translation helpful? Give feedback.
-
Doxygen 1.8.14 is a bit old (December 25, 2017) the current version of doxygen is 1.12.0, so it is advised to update (won't have an effect on the issue in question though). We are talking here about functions, initially like:
and later on like:
there functions are in my opinion different functions and can exists both in the same code base (when overload is supported).
When the example given is not sufficient, it is always good to have:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Let's say I have a function with 2 parameters/arguments in an initial version of my library. Then for the next version, I add an additional parameter to the same function. The function's name stays the same.
When I run both versions of the header file through doxygen, I get two separate files for each instance of the function. However, I'm wondering if it is possible to ensure that the file name is preserved across versions for traceability. I would like users of the library to be able to easily see when the new parameter was added to the function without having to look at two separate, unique output files.
I have
SHORT_NAMES = NO
set.Beta Was this translation helpful? Give feedback.
All reactions