软件文档...... [英] Software documentation...
问题描述
我正在寻找一款同样适用的免费软件文档工具
带有C和C ++的
。我到目前为止与谷歌发现的是：
- Doxygen
- Robodoc
- 自然文件
可能还有更多。有没有人对这些（和其他）软件文档工具有什么建议？
" barcaroller" < BA ********* @ music.net>在消息中写道
新闻：Mf ******************** @ news20.bellglobal.com。 ..我正在寻找一个同样适用于C和C ++的免费软件文档工具。我到目前为止与谷歌发现的是：
- Doxygen
- Robodoc
- 自然文档
可能还有更多。有没有人对这些
有任何建议尝试一下，确定其中一个或多个是否满足你的需求。
（和其他）
访问 www.google .com 和搜索。
冲洗，重复。
-Mike
barcarolleraécrit：我正在寻找一个同样适用于C和C ++的免费软件文档工具。我到目前为止与谷歌发现的是：
- Doxygen
- Robodoc
- 自然文档
可能还有更多。有没有人对这些（和其他）软件文档工具有任何建议？
所有这些自动文档工具永远不会取代
写文档，即使它们是文本格式的。
困扰我的是人们认为他们可以自救。
编写文档的工作在没有意识到的用户身上扔了几个兆字节的自动生成的垃圾
，认为有实际存在的没有的b $ ba文档。
NO，仅知道void fnx（int）
在文件fnx.c中定义并且在
中使用是不够的
（删除了20个文件的愚蠢清单）
不，有必要知道那个拦截功能是什么？
并且永远不会写通过doxygen或类似工具
工具。
lcc-win32的IDE有一个自动写入的模块
文档li ke doxygen。我消除了它因为
这个考虑因素：它绝不会说GREP会说的任何东西。
jacob
jacob navia写道：困扰我的是人们认为他们可以自救
通过投掷来编写文档的工作在没有意识到的用户的情况下，有几兆字节的自动生成的垃圾，认为有文件，而实际上没有。
但是，当你创建库时，它们确实很有用。
I''m looking for a free software documentation tool that works equally well
with C and C++. The ones I have found so far with Google are:
- Doxygen
- Robodoc
- Natural Docs
There probably are more. Does anyone have any recommendations regarding
these (and other) software documentation tools?
解决方案
"barcaroller" <ba*********@music.net> wrote in message
news:Mf********************@news20.bellglobal.com. ..I''m looking for a free software documentation tool that works equally well
with C and C++. The ones I have found so far with Google are:
- Doxygen
- Robodoc
- Natural Docs
There probably are more. Does anyone have any recommendations regarding
these
Try them out and determine if one or more of them fill your needs.
(and other) software documentation tools?
Visit www.google.com and search.
Rinse, repeat.
-Mike
barcaroller a écrit :I''m looking for a free software documentation tool that works equally well
with C and C++. The ones I have found so far with Google are:
- Doxygen
- Robodoc
- Natural Docs
There probably are more. Does anyone have any recommendations regarding
these (and other) software documentation tools?
All those automatic documentation tools never replace
WRITING THE DOCS, even if they are in text format.
What bothers me is that people think they can save themselves
the work of writing the documentation by throwing a
few megabytes of automatically generated rubbish
at the unaware user, that thinks that there is
a documentation when in reality there is NONE.
NO, it is not enough to know that void fnx(int)
is defined in file fnx.c and it is used in
( stupid list of 20 files deleted)
NO, it is necessary to know what that dammed function DOES
and that will never be written by doxygen or similar
tools.
The IDE of lcc-win32 had a module that wrote automatically
the documentation like doxygen. I eliminated it because of
this considerations: it would never say anything more than
what GREP would say anyway.
jacob
jacob navia wrote:What bothers me is that people think they can save themselves
the work of writing the documentation by throwing a
few megabytes of automatically generated rubbish
at the unaware user, that thinks that there is
a documentation when in reality there is NONE.
However, when you create libraries, they are indeed really useful.
这篇关于软件文档......的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
