将 Doxygen 与 Visual Studio 2010 结合使用
我在将 Doxygen 与 Visual Studio 2010 和 C++ 一起有效使用时遇到困难。
除了“取消/注释行”之外没有其他注释功能吗?例如,生成注释存根,并在新行后添加 ///
。
另外,我想知道需要什么才能在 VS2010 的 IntelliSense 功能中显示这些注释?
I have difficulties efficiently using Doxygen with Visual Studio 2010 and C++.
Is there no other function for commenting than "un/comment lines"? For example generating comment stubs, and adding ///
after a new line.
Also, I wonder what is needed to display those Comments within the IntelliSense feature in VS2010?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
根据 MSDN 文档,任何使用
// 的注释
或/*
分隔符将显示在 IntelliSense 成员列表中关联成员的旁边。您可以使用 doxygen 的 XML 输出或 Visual Studio 生成的 XML 文档作为智能感知输入。
/doc
文档说明了如何将 XML 文档与 IntelliSense 结合使用:AtomineerUtils 是 doxygen/javadoc/DocXML 文档的最佳 Visual Studio 插件之一。它不是免费的,但 doxygen 帮助工具列表中没有任何内容是针对 Visual Studio 2010 的。
According to the MSDN Documentation, any comments using
//
or/*
delimiters will be displayed next to the associated member in the IntelliSense Members list.You can use doxygen's XML output or the XML documentation generated by Visual Studio as IntelliSense input.
The
/doc
documentation explains how to use XML documentation with IntelliSense:AtomineerUtils is one of the best Visual Studio add-ins for doxygen/javadoc/DocXML documentation. It's not free, but nothing on the list of doxygen helper tools is targeted at Visual Studio 2010.
我自己能想到的最好的办法就是宏的集合。我四处寻找可能将一些有用的 Visual Studio doxygen 宏聚合在一起的网站,但到目前为止还是空的。但是,使用 Visual Studio 的代码模型自动填充文档确实非常方便。这是我为插入符号当前所在的函数创建文档而制作的宏:
请随意编辑或重用此宏,我欢迎任何批评。
The best that I have been able to come up with on my own has been a collection of macros. I have looked around for websites that may have aggregated some useful Visual Studio doxygen macros together, but so far have come up empty. But, using Visual Studio's code model to auto-populate the documentation can be really handy. Here is a macro that I made to create documentation for the function that the caret is currently in:
Feel free to edit or reuse this macro, and I welcome any critiques.