[cfe-commits] r44789 - /cfe/trunk/www/comparison.html

[Chris Lattner]

Author: lattner
Date: Mon Dec 10 02:21:12 2007
New Revision: 44789

URL: http://llvm.org/viewvc/llvm-project?rev=44789&view=rev
Log:
fixes, thanks to Nico Weber

Modified:
    cfe/trunk/www/comparison.html

Modified: cfe/trunk/www/comparison.html
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/comparison.html?rev=44789&r1=44788&r2=44789&view=diff

==============================================================================
--- cfe/trunk/www/comparison.html (original)
+++ cfe/trunk/www/comparison.html Mon Dec 10 02:21:12 2007
@@ -62,7 +62,7 @@
     <ul>
     <li>The Clang ASTs and design are intended to be <a 
         href="features.html#simplecode">easily understandable</a> by
-        anyone who is familiar with the languages involved and who have a basic
+        anyone who is familiar with the languages involved and who has a basic
         understanding of how a compiler works.  GCC has a very old codebase
         which presents a steep learning curve to new developers.</li>
     <li>Clang is designed as an API from its inception, allowing it to be reused
@@ -173,10 +173,10 @@
     
     <ul>
     <li>PCC dates from the 1970's and has been dormant for most of that time.
-        The clang + llvm community are very active.</li>
+        The clang + llvm communities are very active.</li>
     <li>PCC doesn't support C99, Objective-C, and doesn't aim to support
         C++.</li>
-    <li>PCC's code generation is very limited compared to LLVM, it produces very
+    <li>PCC's code generation is very limited compared to LLVM.  It produces very
         inefficient code and does not support many important targets.</li>
     <li>Like Elsa, PCC's does not have an integrated preprocessor, making it
         extremely difficult to use it for source analysis tools.</li>