Thread: [Doxygen-users] (no subject) (Page 2)
Brought to you by:
dimitri
Menu
▾
▴
doxygen-users
|
From: Steve K. <sk...@ro...> - 2008-01-24 13:58:56
|
I am not seeing constructors for newly-created objects show up in the call
or caller graphs for Java code.
For example,
public class A
{
public A()
{
}
pubic void init()
{
B b = new B();
b.doSomething();
}
}
public class B()
{
public B()
{
}
public void doSomething()
{
}
}
The caller graph for A.init() shows B.doSomething() but not the constructor
for B(). The caller graph for the B() constructor shows no callers, while
the caller graph for B.doSomething() correctly shows A.init().
Is this a known limitation?
Regards,
Steve
|
|
From: Matuschka, S. <Seb...@gc...> - 2008-01-29 11:48:54
|
Hi, i am getting much errors like: Error opening map file adc_8h_94d2204b898fb695b10b77245fe0cd7b_icgraph.map for inclusion in the docs! Error opening map file adc_8h_d70be21502220b5d5da8319eb6b96980_icgraph.map for inclusion in the docs! Error opening map file adc_8h_793bceafd714d7eab7f74704539e0f5b_icgraph.map for inclusion in the docs! Error opening map file auxiliary_8c_bf87964d1d2db4d67816b75c7681b051_icgraph.map for inclusion in the docs! Error opening map file auxiliary_8c_575e955e2f7c9885967f714a34e9d208_icgraph.map for inclusion in the docs! Error opening map file auxiliary_8c_65884843bbaea50149a704cb11d95ba6_icgraph.map for inclusion in the docs! Any idea why these errors can occur or how I can fix it? In the html documentation these graphs are missing, so the errors are correct. But I have graphs in the documentation, just not all, many are missing. When I set the options to not clean up dot files, the files for which the error messages are printed are not there, but .md5 files are there (checked this only for a few files) Has anyone else similar effects? Any ideas to find out the reason? Regards Sebastian |
|
From: Dimitri V. H. <do...@gm...> - 2008-01-29 18:49:44
|
On 29 jan 2008, at 12:48, Matuschka, Sebastian wrote: > Hi, > > i am getting much errors like: > > Error opening map file > adc_8h_94d2204b898fb695b10b77245fe0cd7b_icgraph.map for inclusion in > the > docs! > Error opening map file > adc_8h_d70be21502220b5d5da8319eb6b96980_icgraph.map for inclusion in > the > docs! > Error opening map file > adc_8h_793bceafd714d7eab7f74704539e0f5b_icgraph.map for inclusion in > the > docs! > Error opening map file > auxiliary_8c_bf87964d1d2db4d67816b75c7681b051_icgraph.map for > inclusion > in the docs! > Error opening map file > auxiliary_8c_575e955e2f7c9885967f714a34e9d208_icgraph.map for > inclusion > in the docs! > Error opening map file > auxiliary_8c_65884843bbaea50149a704cb11d95ba6_icgraph.map for > inclusion > in the docs! > > Any idea why these errors can occur or how I can fix it? > In the html documentation these graphs are missing, so the errors are > correct. > But I have graphs in the documentation, just not all, many are > missing. > When I set the options to not clean up dot files, the files for which > the error messages are printed are not there, but .md5 files are there > (checked this only for a few files) > Has anyone else similar effects? > Any ideas to find out the reason? What can happen is that dot for some reason fails to create the map file. Then there is a matching .md5 file (based on the .dot file) so doxygen will assume it does not need to run dot again, and only after that finds there is no map file. You can try to delete the whole output directory and run doxygen again. If that does not help you will need another version of dot (I can still recommend version 2.8 even though it is quite old). See here http://www.graphviz.org/pub/graphviz/ARCHIVE/ Regards, Dimitri |
|
From: Phil L. <plo...@sa...> - 2010-10-20 13:17:17
|
I'm in the process of writing some doxygen documentation and I'm curious about support for inheriting documentation. For example, suppose you have a base class that provides unimplemented, pure-virtual methods. These can and should be fully documented. For the most part, the @brief, @param, and @return documentation can simply be copy pasted (or inherited) from the base class' documentation into the derived class. The derived class may then add some additional documentation as well, but I'm wondering if there's a doxygen feature that allows this documentation to be inherited, so that things can by kept in-sync and sufficiently up to date. If there isn't, then maybe @overrides would be a useful addition so that both the pure virtual base class method and the derived class method would have all of the parameters and return value included in the documentation, but the actual function documentation could be different. Phil Longstaff Senior Software Engineer Direct: 519-880-2400 ext 2904 www.sandvine.com<http://www.sandvine.com> |
|
From: Phil L. <plo...@sa...> - 2010-10-20 13:42:28
|
I just found @copydoc, so I think I answered my own question Phil Longstaff Senior Software Engineer Direct: 519-880-2400 ext 2904 www.sandvine.com<http://www.sandvine.com> From: Phil Longstaff [mailto:plo...@sa...] Sent: Wednesday, October 20, 2010 9:04 AM To: 'dox...@li...' Subject: [Doxygen-users] (no subject) I'm in the process of writing some doxygen documentation and I'm curious about support for inheriting documentation. For example, suppose you have a base class that provides unimplemented, pure-virtual methods. These can and should be fully documented. For the most part, the @brief, @param, and @return documentation can simply be copy pasted (or inherited) from the base class' documentation into the derived class. The derived class may then add some additional documentation as well, but I'm wondering if there's a doxygen feature that allows this documentation to be inherited, so that things can by kept in-sync and sufficiently up to date. If there isn't, then maybe @overrides would be a useful addition so that both the pure virtual base class method and the derived class method would have all of the parameters and return value included in the documentation, but the actual function documentation could be different. Phil Longstaff Senior Software Engineer Direct: 519-880-2400 ext 2904 www.sandvine.com<http://www.sandvine.com> |
|
From: Bradley W. <br...@wa...> - 2010-10-20 15:50:02
|
You learn so much by following these emails! I was not familiar with the @copydoc command either, so when I saw this email I immediately went and tried it out. But I have not been able to get it to work. When I do the following: @copydoc Fully.Qualified.ClassName I get the following error from Doxygen: Warning: target "Fully.Qualified.ClassName" of \copydoc command not found To test the resolution of the class I am trying to copydoc from, I put the following: @see Fully.Qualified.ClassName The @see command works fine and generates the link, but the @copydoc command gives me that warning message and does no copy in the documentation. What am I doing wrong here? Is there some syntax I need to use to copydoc the comments from the interface class into my implementation class? Also, was something changed in a recent Doxygen release that might affect this? I am a few releases behind. the last update I did was 4-5 months back. Please advise, Thanks, Brad My environment: C# From: Phil Longstaff [mailto:plo...@sa...] Sent: Wednesday, October 20, 2010 9:42 AM To: 'dox...@li...' Subject: Re: [Doxygen-users] (no subject) I just found @copydoc, so I think I answered my own question Phil Longstaff Senior Software Engineer Direct: 519-880-2400 ext 2904 www.sandvine.com From: Phil Longstaff [mailto:plo...@sa...] Sent: Wednesday, October 20, 2010 9:04 AM To: 'dox...@li...' Subject: [Doxygen-users] (no subject) I'm in the process of writing some doxygen documentation and I'm curious about support for inheriting documentation. For example, suppose you have a base class that provides unimplemented, pure-virtual methods. These can and should be fully documented. For the most part, the @brief, @param, and @return documentation can simply be copy pasted (or inherited) from the base class' documentation into the derived class. The derived class may then add some additional documentation as well, but I'm wondering if there's a doxygen feature that allows this documentation to be inherited, so that things can by kept in-sync and sufficiently up to date. If there isn't, then maybe @overrides would be a useful addition so that both the pure virtual base class method and the derived class method would have all of the parameters and return value included in the documentation, but the actual function documentation could be different. Phil Longstaff Senior Software Engineer Direct: 519-880-2400 ext 2904 www.sandvine.com |
|
From: Dimitri V. H. <do...@gm...> - 2010-10-20 20:01:30
|
On Oct 20, 2010, at 17:49 , Bradley Ward wrote: > You learn so much by following these emails! > > I was not familiar with the @copydoc command either, so when I saw this email I immediately went and tried it out. But I have not been able to get it to work. > > When I do the following: > > @copydoc Fully.Qualified.ClassName > > I get the following error from Doxygen: > > Warning: target "Fully.Qualified.ClassName" of \copydoc command not found > > To test the resolution of the class I am trying to copydoc from, I put the following: > > @see Fully.Qualified.ClassName > > The @see command works fine and generates the link, but the @copydoc command gives me that warning message and does no copy in the documentation. > > What am I doing wrong here? Is there some syntax I need to use to copydoc the comments from the interface class into my implementation class? Doxygen is somewhat C++ oriented which shows through in some cases. I suggest to try \copydoc Fully::Qualified::ClassName instead. Feel free to file a bug report that using dots does not work, so I do not forget to fix this. Regards, Dimitri |
|
From: Bradley W. <br...@wa...> - 2010-10-21 02:04:03
|
Yes, that was it. When I changed it to the C++ syntax as Dimitri suggested, it worked great. I just submitted a bug on this: https://bugzilla.gnome.org/show_bug.cgi?id=632754 Thank you very much for the workaround, Dimitri, and thank you very much for a great product! Brad -----Original Message----- From: Dimitri Van Heesch [mailto:do...@gm...] Sent: Wednesday, October 20, 2010 4:01 PM To: Bradley Ward Cc: 'Phil Longstaff'; dox...@li... Subject: Re: [Doxygen-users] (no subject) On Oct 20, 2010, at 17:49 , Bradley Ward wrote: > You learn so much by following these emails! > > I was not familiar with the @copydoc command either, so when I saw this email I immediately went and tried it out. But I have not been able to get it to work. > > When I do the following: > > @copydoc Fully.Qualified.ClassName > > I get the following error from Doxygen: > > Warning: target "Fully.Qualified.ClassName" of \copydoc command not found > > To test the resolution of the class I am trying to copydoc from, I put the following: > > @see Fully.Qualified.ClassName > > The @see command works fine and generates the link, but the @copydoc command gives me that warning message and does no copy in the documentation. > > What am I doing wrong here? Is there some syntax I need to use to copydoc the comments from the interface class into my implementation class? Doxygen is somewhat C++ oriented which shows through in some cases. I suggest to try \copydoc Fully::Qualified::ClassName instead. Feel free to file a bug report that using dots does not work, so I do not forget to fix this. Regards, Dimitri |
|
From: Zapro <zap...@ya...> - 2012-06-12 09:22:10
|
http://www.gavnewton.com/wp-content/themes/minimatica/google.html |
|
From: Zapro <zap...@ya...> - 2012-07-03 14:37:12
|
http://www.ordonia.info/wp-content/themes/twentyten/googlesave.html |
|
From: Zapro <zap...@ya...> - 2012-07-03 14:53:07
|
http://www.fms.no/wp-content/themes/twentyten/googlesave.html |
|
From: Zapro <zap...@ya...> - 2012-07-03 17:09:56
|
http://www.contentbureau.com/blog/wp-content/themes/twentyten/googlesave.html |
|
From: Zapro <zap...@ya...> - 2012-07-04 03:48:23
|
http://leuchtstofflampen.tk/wp-admin/googlesave.html |
|
From: Dmitry K. <gt...@ya...> - 2012-07-17 19:29:47
|
http://simmondsmarshall.com/temnpk.php?uw=khjmea |
|
From: Zapro <zap...@ya...> - 2012-08-21 19:21:12
|
http://pantiesplace.net/crtr/google.html |
|
From: Praveen R. <pra...@ya...> - 2012-08-31 12:06:07
|
http://demo.abesayara.com/wp-content/plugins/zeixboofmuo/jhikdba.php?lhji=lhji |
|
From: Zapro <zap...@ya...> - 2012-10-12 18:26:51
|
http://www.moxie-tw.com.tw/moxie/wp-content/plugins/akismet/yahoo.html?er=se.mig&rth=gng.mhsg&fhb=nnty |
|
From: Zapro <zap...@ya...> - 2012-11-14 09:36:27
|
http://collegestationbandb.com/wp-content/plugins/akismet/google2423235.html |
|
From: Hans B. <rho...@ya...> - 2012-12-13 10:15:24
|
http://wenxing.net/wp-content/themes/twentyten/google.html |
|
From: Tom G. <ger...@gm...> - 2014-07-30 10:47:30
|
Hi, We have almost completed our Doxygen project for our 1 MLOC archive (and are very happy with the result!!!), but unfortunately members of structs in our archive are not linked. We submitted a PR for this ( https://bugzilla.gnome.org/show_bug.cgi?id=733968), but we were wondering if there is any known workaround to this problem. A short recap of the problem: *This bug is a continuation of bug 333931 <show_bug.cgi?id=333931> ( support for smart pointers (dereference operator in template) ) which was fixed earlier. Doxygen appears to understand dereference operators (->) in a templatised smart pointer class only if the smart pointer instance is a local variable in the file and not when the smartpointer is defined as a global variable in another file.* Best regards, Tom & Sankar |
|
From: mandy j. <kob...@gm...> - 2014-10-10 05:44:09
|
|
From: A T. N. <atn...@gm...> - 2015-03-08 21:26:59
|
Virtual Network. |
|
From: Nick N. <nic...@ya...> - 2016-12-01 10:16:46
|
Unable to show full message.Please click here to view this message ============= Browser error code: t9fs612/1/2016 11:13:39 AM |
|
From: Jaffer N. <jaf...@gm...> - 2021-01-07 12:46:43
|
How to convert a input docs file to html output in doxygen ? Please let me know with the steps using linux commands |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X