edits, switch the goals/why section.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@44777 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/www/index.html b/www/index.html
index 343e9b4a4296f419db8933b90980e89c707f1def..ee212f61a13feaae1672103238eaa31e99722a00 100644 (file)
--- a/www/index.html
+++ b/www/index.html
@@ -17,28 +17,6 @@
     Objective C++ front-end for the <a href="http://www.llvm.org/">LLVM</a>\r
     compiler.</p>\r
     \r
-    <h2>Why?</h2>\r
-    \r
-    <p>The development of a new front-end was started out of a need -- a need\r
-       for a compiler that allows better diagnostics, better integration with\r
-       IDEs, a license that is compatible with commercial products, and a\r
-       compiler that is easier to develop and maintain.  All of these were\r
-       motivations for starting work on a new front-end that could\r
-       meet these needs.</p>\r
-       \r
-    <p>A good (but quite dated) introduction to Clang can be found in the\r
-       following video lectures:</p>\r
-       \r
-    <ul>\r
-      <li><a href="clang_video-05-25-2007.html">Clang Introduction</a>\r
-          (May 2007)</li>\r
-      <li><a href="clang_video-07-25-2007.html">Features and Performance of \r
-          Clang</a>  (July 2007)</li>\r
-    </ul>\r
-    \r
-    <p>For a more detailed comparison about Clang and other compilers, please\r
-       see the <a href="comparison.html">clang comparison page</a>.</p>\r
-    \r
     <h2>Features/Goals</h2>\r
     \r
     <p>Some of the goals for the project include the following:</p>\r
@@ -51,10 +29,12 @@
         C90, C99, etc.</li>\r
     <li>GCC compatibility: support GCC extensions, but allow them to be\r
         disabled.</li>\r
-    <li>Library based architecture with finely crafted APIs.</li>\r
-    <li>Support many clients, such as refactoring, static analysis, as well as\r
+    <li><a href="features.html#performance">High performance and low memory\r
+         use</a>.</li>\r
+    <li>Build a library-based architecture with finely crafted APIs, allowing\r
+        the code to be reused in many ways.</li>\r
+    <li>Support many clients such as refactoring, static analysis, as well as\r
         code generation.</li>\r
-    <li>High performance.</li>\r
     <li>Design for integration with IDEs as well as code generation with the\r
         <a href="http://llvm.org">LLVM Optimizer and Code Generator</a>.</li>\r
     <li><a href="features.html#expressivediags">Expressive diagnostics</a>:\r
@@ -70,7 +50,29 @@
        href="features.html">Features</a> section.</p>\r
        \r
        \r
-    <h2>Current Status</h2>\r
+     <h2>Why?</h2>\r
+    \r
+    <p>The development of a new front-end was started out of a need -- a need\r
+       for a compiler that allows better diagnostics, better integration with\r
+       IDEs, a license that is compatible with commercial products, and a\r
+       compiler that is easier to develop and maintain.  All of these were\r
+       motivations for starting work on a new front-end that could\r
+       meet these needs.</p>\r
+       \r
+    <p>A good (but quite dated) introduction to Clang can be found in the\r
+       following video lectures:</p>\r
+       \r
+    <ul>\r
+      <li><a href="clang_video-05-25-2007.html">Clang Introduction</a>\r
+          (May 2007)</li>\r
+      <li><a href="clang_video-07-25-2007.html">Features and Performance of \r
+          Clang</a>  (July 2007)</li>\r
+    </ul>\r
+    \r
+    <p>For a more detailed comparison between Clang and other compilers, please\r
+       see the <a href="comparison.html">clang comparison page</a>.</p>\r
+    \r
+   <h2>Current Status</h2>\r
     \r
     <p>Clang is still in early development stages.  If you are looking for\r
     source analysis or source-to-source transformation tools, clang is probably\r
@@ -91,7 +93,7 @@
        mailing list, or start by browsing its archives.</p>\r
 \r
     <p>If you are interested in trying out Clang, please see the build\r
-       instructions on the <ahref="get_involved.html#build">Get Involved</a> \r
+       instructions on the <a href="get_involved.html#build">Get Involved</a> \r
        page.</p>    \r
   </div>\r
 </body>\r