From 9ef369211da8f22fcce65ec4f9cfb75c9304b414 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Thu, 19 Mar 2009 22:03:42 +0000 Subject: [PATCH] wording. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@67337 91177308-0d34-0410-b5e6-96231b3b80d8 --- www/features.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/www/features.html b/www/features.html index 9ae7f77eeb..21382fd5b1 100644 --- a/www/features.html +++ b/www/features.html @@ -136,8 +136,8 @@ to tap the full potential of the clang design.

In addition to being fast and functional, we aim to make Clang extremely user friendly. As far as a command-line compiler goes, this basically boils down to making the diagnostics (error and warning messages) generated by the compiler -be as useful as possible. There are several ways that we do this, but it -basically boils down to pinpointing exactly what is wrong in the program, +be as useful as possible. There are several ways that we do this, but the +most important are pinpointing exactly what is wrong in the program, highlighting related information so that it is easy to understand at a glance, and making the wording as clear as possible.

@@ -158,9 +158,9 @@ understand what is wrong based on the Clang error: Because clang prints a caret, you know exactly which plus it is complaining about. The range information highlights the left and right side of the plus which makes it immediately obvious what the compiler is talking about, which is very useful for -cases involving precedence issues and many other cases.

+cases involving precedence issues and many other situations.

-

Clang diagnostics are very right and have many features. For more +

Clang diagnostics are very polished and have many features. For more information and examples, please see the Expressive Diagnostics page.

-- 2.40.0