> just a standard IPv6 representation of an IPv4 address and port.
>
> So, how do I make it go away?
>
replace the :: with \:: then doxygen won't try to interpret the :: as
something special (this works for most special characters)
--
Richard Damon
-
ou can make files be specifically markdown, I don't normally do
this, I see this as a feature to use when you have some documentation
that has already been prepared in markdown format, that you want to
include as part of you documentation package (and then refer
not subdirectories
# should be searched for input files as well. Possible values are YES and NO.
# If left blank NO is used.
RECURSIVE = YES
--
Richard Damon
--
Learn the latest--Visual Studio 2012, Shar
predefine the "macro" __attribute__() to
expand to nothing. This removes the attribute keyword clause, making the
code look like standard C, and Doxygen can processes it.
--
Richard Damon
--
CenturyLink Clo
my
> own DOT file but much more convenient would be a switch within
> Doxyfile.
>
The call graph of main()?
If you have a library, I think you will need to make a "dumy" function
that calls all the root api func
On 1/26/15 4:28 PM, W. Miah wrote:
> Hello,
>
> I am getting a bit confused with the difference between CALL_GRAPH and
> CALLER_GRAPH. Can someone give me an example to illustrate the effects
> of setting both of them to YES and NO?
>
> Thanks in advance,
> Wadud.
A CALL_GRAPH is a listing of every
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
--
Mon
hat the list in the code is not the
> same as the list in the config file comment, for starters).
>
> I am not seeing any combination of configuration parameters that will
> achieve that. Is that true?
>
> Thanks,
> Clayton
>
Have you tried += to add the items to the lists? I
his option must be set to YES to include the documentation for static
items.
--
Richard Damon
--
___
Doxygen-users mailing list
Doxygen-users@lists.source
is a doxygen warning and
> In case "2" it is a check style warning.
>
> Is there another way to write doxygen comment for that parameter?
>
> Could anyone please help us fix this issue.
>
>
> Thank you
> Sai
>
The issue is that is not a parameter of the func
al compilation, but will be defined in your
doxygen config file. Then Doxygen will see that definition and document
it. I sometimes use the macro DOXYGEN for this. Something like:
#ifdef DOXYGEN
#define MYLIB_SOME_MACRO
#endif
--
Richard Damon
of changes in the code, but perhaps if you gave it a struct tag,
you might get doxygen to note its existence, and that shouldn't change
how you use it.
--
Richard Damon
--
What NetFlow Analyzer can do for you? Mon
7;t fully support the enum class construct,
and is still keeping track of the enumeration values in the ns::A
namespace, and not in the appropriate Enum# sub-namespace therein.
--
Richard Damon
--
___
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
o() function is fully
documented, and Derived:implementFoo() will be documented with the behavior.
-Original Message-
From: Stefan Ludewig [mailto:kaiserl...@exitgames.com]
Sent: Monday, February 13, 2017 9:32 AM
To: Richard Damon ;
doxygen-users@lists.sourceforge.net
Subject: RE: [Doxygen
You can make a function you call to access them! Make the function inline, and
it will likely not even cost you any time/space in the program. Maybe even
uglify the global variable name so you change all the references to use the
accessor function.
> On Mar 21, 2017, at 9:13 AM, Xenia Galinskay
e dependent (C++ with its
overloads, especially operator xxx()s would require basically a FULL:
parsing of the code).
One option would be to not include the whole library directory as an
input, but only the specific files that you need from the library.
--
Richard Damon
-
ust
those of my base class that gave it friendship.
The out of class operators (which are sometimes given friend access) are
NOT member functions.
Doxygen listing them as 'Inherited Members' would have been a bu
f the curiously recurring template pattern (CRTP).
This implies that the friend specifier is essential.
Maarten
On 01/09/2017 12:56, Richard Damon wrote:
On 9/1/17 2:03 AM, Maarten de Jong wrote:
Dear all,
In some previous versions of Doxygen (e.g. 1.6.1) , the friend
operators of the b
predict, as a hash
is added to the name to allow the detection of needing to update the file.
--
Richard Damon
--
Check out the vibrant tech community on one of the world's most
engaging tech
(!(e)) { \
>
> std::string message = "\""; \
>
> message += #e; \
>
> message += "\" is false"; \
>
> throw eccl::assertion_exception(message); \
>
> }
&g
er the returns, that is like because the
documentation is produced in the order it is in the file, (there is no
implicit sorting of these paragraphs) so since the parameters are
documented after the returns, that is how the documentation is produced.
--
Richard Damon
-
eclaring the class could even than bring the
name into the global namespace so most of the program doesn't need to
see the difference.
--
Richard Damon
___
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
m the issue under
> discussion...
>
I will use Doxygen for more than just Public API, which is one reason it
has the option to document internal/private members.
If the executables are really independent, I might be tempted to run
separate reports for each, and perhaps have the common library as a
i
rence. It would be a simple enough program to write to customize
for you own needs.
--
Richard Damon
___
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
If it is in a C/C++ code file, I just use an #if 0/#endif to comment the
comment out.
> On Nov 4, 2019, at 11:38 AM, Kerry, Richard wrote:
>
>
>
> A Doxygen comment is pretty well explained in the docs, but is there some
> syntax to comment-out a line of mark-up in a Doxygen comment block
ering out loud whether the pre-processor acts before or after
> the lexical analyser strips comments.
>
>
>
You can't do
/**
#if
*/
as comments are removed before preprocessing
You should be able to do
///
///
///
ntation for the contents of files that are
inputs to doxygen, not files that they include.
--
Richard Damon
___
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
o get rid of these "EXPORT"s in doxygen??
>
>
> right I'm using sed to hack the tex files:
>
> sed -i 's/E\\+X\\+P\\+O\\+RT//g' *.tex
>
>
> there must be a better way??
>
>
> thanks,
>
> Harald
>
Enable preprocessing (maybe pre
///
} ///
} ///
} ///
Since every line has a comment, the documenting comment block should
continue
--
Richard Damon
___
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
29 matches
Mail list logo
