edits, switch the goals/why section.

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

1 files changed, 29 insertions, 27 deletions

diff --git a/www/index.html b/www/index.html
index 343e9b4a42..ee212f61a1 100644
--- 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>

     compiler.</p>

     

-    <h2>Why?</h2>

-    

-    <p>The development of a new front-end was started out of a need -- a need

-       for a compiler that allows better diagnostics, better integration with

-       IDEs, a license that is compatible with commercial products, and a

-       compiler that is easier to develop and maintain.  All of these were

-       motivations for starting work on a new front-end that could

-       meet these needs.</p>

-       

-    <p>A good (but quite dated) introduction to Clang can be found in the

-       following video lectures:</p>

-       

-    <ul>

-      <li><a href="clang_video-05-25-2007.html">Clang Introduction</a>

-          (May 2007)</li>

-      <li><a href="clang_video-07-25-2007.html">Features and Performance of 

-          Clang</a>  (July 2007)</li>

-    </ul>

-    

-    <p>For a more detailed comparison about Clang and other compilers, please

-       see the <a href="comparison.html">clang comparison page</a>.</p>

-    

     <h2>Features/Goals</h2>

     

     <p>Some of the goals for the project include the following:</p>

@@ -51,10 +29,12 @@
         C90, C99, etc.</li>

     <li>GCC compatibility: support GCC extensions, but allow them to be

         disabled.</li>

-    <li>Library based architecture with finely crafted APIs.</li>

-    <li>Support many clients, such as refactoring, static analysis, as well as

+    <li><a href="features.html#performance">High performance and low memory

+         use</a>.</li>

+    <li>Build a library-based architecture with finely crafted APIs, allowing

+        the code to be reused in many ways.</li>

+    <li>Support many clients such as refactoring, static analysis, as well as

         code generation.</li>

-    <li>High performance.</li>

     <li>Design for integration with IDEs as well as code generation with the

         <a href="http://llvm.org">LLVM Optimizer and Code Generator</a>.</li>

     <li><a href="features.html#expressivediags">Expressive diagnostics</a>:

@@ -70,7 +50,29 @@
        href="features.html">Features</a> section.</p>

        

        

-    <h2>Current Status</h2>

+     <h2>Why?</h2>

+    

+    <p>The development of a new front-end was started out of a need -- a need

+       for a compiler that allows better diagnostics, better integration with

+       IDEs, a license that is compatible with commercial products, and a

+       compiler that is easier to develop and maintain.  All of these were

+       motivations for starting work on a new front-end that could

+       meet these needs.</p>

+       

+    <p>A good (but quite dated) introduction to Clang can be found in the

+       following video lectures:</p>

+       

+    <ul>

+      <li><a href="clang_video-05-25-2007.html">Clang Introduction</a>

+          (May 2007)</li>

+      <li><a href="clang_video-07-25-2007.html">Features and Performance of 

+          Clang</a>  (July 2007)</li>

+    </ul>

+    

+    <p>For a more detailed comparison between Clang and other compilers, please

+       see the <a href="comparison.html">clang comparison page</a>.</p>

+    

+   <h2>Current Status</h2>

     

     <p>Clang is still in early development stages.  If you are looking for

     source analysis or source-to-source transformation tools, clang is probably

@@ -91,7 +93,7 @@
        mailing list, or start by browsing its archives.</p>

 

     <p>If you are interested in trying out Clang, please see the build

-       instructions on the <ahref="get_involved.html#build">Get Involved</a> 

+       instructions on the <a href="get_involved.html#build">Get Involved</a> 

        page.</p>    

   </div>

 </body>