On 6/24/15 12:38 PM, woody wrote:
> 1. I would like to take an undocumented package and have doxygen insert the
> initial documentation into the source file.
> That is, run doxygen on an undocumented package (which I have done)
> and be able to tell doxygen to insert into the SOURCE FILES, the specific
> doxygen headers needed, based on what it figured out.
> is there a way to have doxygen do that?
To my knowledge, doxygen has no facilities to write into the source
files. It would be a very different sort of utility to do what you are
looking for.
>
> 2. It seems to me like doxygen should be able to generate, for each
> variable, a list of line numbers in the code where the variable is
> referenced. I don't see an option for this in the expert section of the wizard.
To my knowledge, doxygen doesn't keep track references to that level of
detail, and only tracks 'global' items.
>
> 3. since this is an embedded project, the main file has a number of
> interrupt handlers. This is an intensive interrupt driven system. is there
> a way to make doxygen aware that it should include these interrupt
> functions in the dependency graph, so that the result of graphvis would
> list those as interrupt functions, that interact with
> main. i.e. interrupt_function_name with a pointer line to and from main?
>
Interrupt functions really aren't interacting with main, but with the
whole flow of execution, so drawing their call tree back to main would
actually be a bit deceptive. Also interrupt functions tend to use some
implementation specific method of marking them as interrupt functions so
it is hard for doxygen to identify them, and in some environments there
is nothing special to mark them, either there is just an array of
functions pointers used as a vector table (maybe with an assembly
written wrapper), or a call to a function like setVector with a pointer
to the function.
--
Richard Damon
|
