diff options
| author | Ted Kremenek <kremenek@apple.com> | 2008-07-25 23:34:29 +0000 |
|---|---|---|
| committer | Ted Kremenek <kremenek@apple.com> | 2008-07-25 23:34:29 +0000 |
| commit | ffc8a6172ef2e5abf01fcf47c77823ee322ff255 (patch) | |
| tree | 734903a7a9417fc50fc0adefaf83116c45f8e574 | |
| parent | 7c4a191d8be7eac565a64369de072b2a52bf6749 (diff) | |
Added project idea for a doxygen-like tool built using clang
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@54076 91177308-0d34-0410-b5e6-96231b3b80d8
| -rw-r--r-- | www/get_involved.html | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/www/get_involved.html b/www/get_involved.html index b64f42c9ba..c3c7c809bb 100644 --- a/www/get_involved.html +++ b/www/get_involved.html @@ -116,7 +116,13 @@ things. I don't think that there is a specific licensing reason to reimplement libgcc, but there is a lot of room for improvement in it in many
dimensions.</li>
-</ul>
+<li><b>Implement an tool to generate code documentation</b>: Clang's
+library-based design allows it to be used by a variety of tools that reason
+about source code. One great application of Clang would be to build an
+auto-documentation system like doxygen that generates code documentation from
+source code. The advantage of using Clang for such a tool is that the tool would
+use the same preprocessor/parser/ASTs as the compiler itself, giving it a very
+rich understanding of the code.</li> </ul>
<p>If you hit a bug with clang, it is very useful for us if you reduce the code
that demonstrates the problem down to something small. There are many ways to
|