From bafc68f6cf7e5cf50159219c06ce993a07676f44 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Sat, 6 Oct 2007 05:48:57 +0000 Subject: [PATCH] fix grammaro git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@42685 91177308-0d34-0410-b5e6-96231b3b80d8 --- www/features.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/www/features.html b/www/features.html index db67be0aad..ec293cdcaf 100644 --- a/www/features.html +++ b/www/features.html @@ -53,7 +53,7 @@ There are several key features which we believe make Clang an exciting front-end

Library based architecture

A major design concept for the LLVM front-end involves using a library based architecture. In this library based architecture, various parts of the front-end can be cleanly divided into separate libraries which can then be mixed up for different needs and uses. In addition, the library based approach makes it much easier for new developers to get involved and extend LLVM to do new and unique things. In the words of Chris, -
"The world needs better compiler tools, tools which are built as libraries. This design point allows reuse of the tools in new and novel ways. However, building the tools as libraries isn't enough: they must have clean APIs, be as decoupled from each other as possible, and be easy to modify/extend. This requires clean layering, decent design, and avoiding tying the libraries to a specific use."
+
"The world needs better compiler tools, tools which are built as libraries. This design point allows reuse of the tools in new and novel ways. However, building the tools as libraries isn't enough: they must have clean APIs, be as decoupled from each other as possible, and be easy to modify/extend. This requires clean layering, decent design, and keeping the libraries independent of any specific client."
Currently, the LLVM front-end is divided into the following libraries: