Lambda functions inline source generating not correct, it is look like variables with init section not like functions with inline source.In test it ok but in real project i want to hide many of entities and show just may be full code of some documented classes inline. But now it include not body, but names of methods and variables. In general it reasonable if i whant to add only class overview without code everithing is ok, but how to add full class source inline? After all, this is what i expected after read the INLINE_SOURCES description 'inline include body of. Class do not insert source code inline anyway without or with ' for member functions it only show list of members of class but not code of members.Without ' source was not inserted inline. The enum, and enum class in c++ have the same behaviour like function.Source, config file and generated html here I'v extend the test to clarify how setting INLINE_SOURCES to YES work and thats the result. i suggest changing to Setting the INLINE_SOURCES tag to YES will include the body of functions with detailed section, classes and enums directly into the documentation. Now it is Setting the INLINE_SOURCES tag to YES will include the body of functions, classes and enums directly into the documentation. So may be there is enough reason to change the INLINE_SOURCES description. But there is a solution to this, which mean this is not a bug, I close the question. ![]() If the function was not important i will never see this. And actually what the reason not to generate inline sources if there is no detailed description? For what task may it be necessary not to generate an inline source if the function has only brief but not details? I think this behavior of the program confuses the person who has read the docs first time. ![]() So it's not bug, it's a feature? I'm new at doxygen and when i find that doxygen do not generate inline source after set INLINE_SOURCES = YES i began to read documents hard and than stackoverflow and than i did not find any information that to generate inline sources the detailed section must be present. ![]() And ALWAYS_DETAILED_SEC was NO, and after set it to YES both version of functions generate inline code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |