From 34c0533a005ad5be0356dbb913ab3a05fb6b3ca5 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Fri, 27 Feb 2009 19:31:12 +0000 Subject: [PATCH] minor wording changes. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@65648 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/InternalsManual.html | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/InternalsManual.html b/docs/InternalsManual.html index dfd487aa45..42b3b784d9 100644 --- a/docs/InternalsManual.html +++ b/docs/InternalsManual.html @@ -393,12 +393,13 @@ it is rendered.

In some cases, the front end emits diagnostics when it is clear that some small change to the source code would fix the problem. For example, a missing semicolon at the end of a statement or a use of -deprecated syntax that is easily rewritten into a more modern form. In -these cases, the front end should emit the diagnostic and recover -gracefully.

+deprecated syntax that is easily rewritten into a more modern form. +Clang tries very hard to emit the diagnostic and recover gracefully +in these and other cases.

-

In these cases, the diagnostic can be annotation with a code -modification "hint" that describes how to modify the code referenced +

However, for these cases where the fix is obvious, the diagnostic +can be annotated with a code +modification "hint" that describes how to change the code referenced by the diagnostic to fix the problem. For example, it might add the missing semicolon at the end of the statement or rewrite the use of a deprecated construct into something more palatable. Here is one such -- 2.40.0