doxygen 与 IDL/ODL
如果您有一个 C++ 项目，其中包含一堆 .ODL 文件和 ODL 编译器生成的 .h 文件，是否应该告诉 doxygen 解析 .odl 和 .h，或者仅解析其中一个或其他？一般来说，我不喜欢记录生成的代码，但 IDL 是一种特殊情况。
无论如何，在我的测试中，ODL 文件的成员列表似乎无法正常工作，ODL 文件是否已正确解析？
If you have a C++ project that has a bunch of .ODL files and the generated .h files from the ODL compiler, should doxygen be told to parse both .odl and .h, or only one or the other? In general I don't like documenting generated code but IDL is sort of a special case.
In any case, it seems like the member listing of ODL files is not quite working properly in my tests, are ODL files properly parsed?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
从 此页面 看来，Doxygen 完美支持解析
*idl和*.odl文件。也许您对评论格式有一些疑问？无论如何，我建议您不要解析
*.idl/*.odl文件和生成的.h文件。根据定义，后者生成并表示与*.idl/*.old文件中定义的类相同的类。解析两者就像两次记录同一组类，这显然不是一个好主意。
From this page it seems the Doxygen perfectly supports parsing
*idland*.odlfiles. Maybe you have some issues regarding the comments format ?Anyway, I would advise you against parsing both
*.idl/*.odlfiles and generated.hfiles. The latter are, by definition, generated and represent the same classes than the one defined in the*.idl/*.oldfiles.Parsing both is like documenting the same set of classes twice, which is obviously not a good idea.