straight-forward if you follow the example of what llvm-gcc generates.</li>\r
\r
<li><b>Continue work on C++ support</b>: Implementing all of C++ is a very big\r
-job, but there are lots of little things that can be done. Right now we support\r
-some small things like references and bool. We also support parsing of\r
-namespaces, but don't build ASTs for it. It would be straight-forward to\r
-implement support for representing namespaces, then add support for things like\r
-foo::bar::baz. Likewise, lots of other little pieces can be picked off and\r
-implemented.</li>\r
+job, but there are lots of little pieces that can be picked off and implemented.\r
+See the <a href="cxx_status.html">C++ status report page</a> to find out what is\r
+missing and what is already at least partially supported.</li>\r
\r
<li><b>Improve target support</b>: The current target interfaces are heavily\r
stubbed out and need to be implemented fully. See the FIXME's in TargetInfo.\r
\r
<p>Clang currently has pretty good parsing and semantic analysis support for\r
C and Objective-C right now, and bugs are usually quickly fixed once\r
- reported. C++ support is still <a href="cxx_status.html">very early</a>,\r
+ reported. <a href="cxx_status.html">C++ support</a> is still very early,\r
and we don't expect to have respectable C++ support for another 2 years\r
or so.</p>\r
\r