jyapayne/swig
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Use Sphinx-friendly formatting for overloaded functions documentation.

Browse source 
Sphinx doesn't allow sections inside the function documentation and gives tons
of SEVERE warnings for them, so while just emphasizing the "Overload" header
is not ideal, it is better than before because at least the string "Overload"
itself appears in the Sphinx-generated output.
This commit is contained in:
Vadim Zeitlin 2014-07-13 20:47:00 +02:00
commit ea1d56da67
4 changed files with 9 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

10
Source/DoxygenTranslator/src/PyDocConverter.cpp
View file

@ -692,10 +692,8 @@ String *PyDocConverter::makeDocumentation(Node *n)
for (int realOverloadCount = 0;
realOverloadCount < (int) allDocumentation.size();
realOverloadCount++) {
concatDocString << generateDivider() << std::endl;
concatDocString << "Overload " << (realOverloadCount + 1) << ":"
concatDocString << "*Overload " << (realOverloadCount + 1) << ":*"
<< std::endl;
concatDocString << generateDivider();
concatDocString << allDocumentation[realOverloadCount] << std::endl;
}
pyDocString = concatDocString.str();
@ -744,9 +742,3 @@ String *PyDocConverter::makeDocumentation(Node *n)
return NewString("");
}
std::string PyDocConverter::generateDivider()
{
static string dividerString(DOC_STRING_LENGTH, '-');
return dividerString;
}