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

diff --git a/www/get_involved.html b/www/get_involved.html
index b64f42c9ba4bd0e0fe7a6c2a8269f82862e3e50e..c3c7c809bb0722650b3be0bb98b99f553c8e677e 100644 (file)
--- 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 \r
 dimensions.</li>\r
 \r
-</ul>\r
+<li><b>Implement an tool to generate code documentation</b>: Clang's\r
+library-based design allows it to be used by a variety of tools that reason\r
+about source code. One great application of Clang would be to build an\r
+auto-documentation system like doxygen that generates code documentation from\r
+source code. The advantage of using Clang for such a tool is that the tool would\r
+use the same preprocessor/parser/ASTs as the compiler itself, giving it a very\r
+rich understanding of the code.</li> </ul>\r
 \r
 <p>If you hit a bug with clang, it is very useful for us if you reduce the code\r
 that demonstrates the problem down to something small.  There are many ways to\r