https://github.com/lknknm created https://github.com/llvm/llvm-project/pull/156620
This is mostly just a small proof read for the https://clang.llvm.org/features.html documentation page. The changes include some typo fixes and suggestions I've found would be useful. If needed, I can also proof read other sections of the documentation and pack everything into a "bigger" PR to do everything in one go. >From 10b4bcf3653c484652e9a832e613eb820530c34f Mon Sep 17 00:00:00 2001 From: Lucas <108239558+lkn...@users.noreply.github.com> Date: Mon, 1 Sep 2025 22:54:46 +0200 Subject: [PATCH 1/7] Fix: Change Reference to 'BSD' license to 'Apache' License. --- clang/www/features.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clang/www/features.html b/clang/www/features.html index cd2f9e7b4e2e1..dca23e919a03d 100755 --- a/clang/www/features.html +++ b/clang/www/features.html @@ -39,7 +39,7 @@ <h1>Clang - Features and Goals</h1> <li><a href="#libraryarch">Library based architecture</a></li> <li><a href="#diverseclients">Support diverse clients</a></li> <li><a href="#ideintegration">Integration with IDEs</a></li> -<li><a href="#license">Use the LLVM 'BSD' License</a></li> +<li><a href="#license">Use the LLVM 'Apache 2' License</a></li> </ul> <p>Internal Design and Implementation:</p> >From 5e7816923c7f7fdb2413b31859d2c6044a0a4713 Mon Sep 17 00:00:00 2001 From: Lucas Mellone <lucasmellone@MAC-MINI.station> Date: Mon, 1 Sep 2025 23:09:01 +0200 Subject: [PATCH 2/7] Fix: 'a optimizer' to 'an optimizer' typo --- clang/www/features.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/clang/www/features.html b/clang/www/features.html index dca23e919a03d..9f3d06c204a84 100755 --- a/clang/www/features.html +++ b/clang/www/features.html @@ -39,7 +39,7 @@ <h1>Clang - Features and Goals</h1> <li><a href="#libraryarch">Library based architecture</a></li> <li><a href="#diverseclients">Support diverse clients</a></li> <li><a href="#ideintegration">Integration with IDEs</a></li> -<li><a href="#license">Use the LLVM 'Apache 2' License</a></li> +<li><a href="#license">Use the LLVM 'BSD' License</a></li> </ul> <p>Internal Design and Implementation:</p> @@ -208,7 +208,7 @@ <h3><a name="diverseclients">Support Diverse Clients</a></h3> <p>The problem with this goal is that different clients have very different requirements. Consider code generation, for example: a simple front-end that parses for code generation must analyze the code for validity and emit code -in some intermediate form to pass off to a optimizer or backend. Because +in some intermediate form to pass off to an optimizer or backend. Because validity analysis and code generation can largely be done on the fly, there is not hard requirement that the front-end actually build up a full AST for all the expressions and statements in the code. TCC and GCC are examples of >From 2ea06d3ee411b5b5cdfd532fec3304d6b20417ba Mon Sep 17 00:00:00 2001 From: lknknm <lucasmellone@MAC-MINI.station> Date: Mon, 1 Sep 2025 23:12:27 +0200 Subject: [PATCH 3/7] Fix(suggestion): 'Fast compiles' to 'Fast Compile-times' --- clang/www/features.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/clang/www/features.html b/clang/www/features.html index 9f3d06c204a84..e609ac28bb121 100755 --- a/clang/www/features.html +++ b/clang/www/features.html @@ -28,7 +28,7 @@ <h1>Clang - Features and Goals</h1> <p>End-User Features:</p> <ul> -<li><a href="#performance">Fast compiles and low memory use</a></li> +<li><a href="#performance">Fast Compile-times and low memory use</a></li> <li><a href="#expressivediags">Expressive diagnostics</a></li> <li><a href="#gcccompat">GCC compatibility</a></li> </ul> @@ -59,7 +59,7 @@ <h2><a name="enduser">End-User Features</a></h2> <!--=======================================================================--> -<h3><a name="performance">Fast compiles and Low Memory Use</a></h3> +<h3><a name="performance">Fast Compile-times and Low Memory Use</a></h3> <!--=======================================================================--> <p>A major focus of our work on clang is to make it fast, light and scalable. >From 74faa1f978fa508db31fbc12d4b1724df490ddd8 Mon Sep 17 00:00:00 2001 From: lknknm <sx...@protonmail.com> Date: Mon, 1 Sep 2025 23:27:39 +0200 Subject: [PATCH 4/7] Suggestion: change to 'when you begin implementing a language' --- clang/www/features.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clang/www/features.html b/clang/www/features.html index e609ac28bb121..4603d72a22528 100755 --- a/clang/www/features.html +++ b/clang/www/features.html @@ -349,7 +349,7 @@ <h3><a name="conformance">Conformance with C/C++/ObjC and their variants</a></h3> <!--=======================================================================--> -<p>When you start work on implementing a language, you find out that there is a +<p>When you begin implementing a language, you find out that there is a huge gap between how the language works and how most people understand it to work. This gap is the difference between a normal programmer and a (scary? super-natural?) "language lawyer", who knows the ins and outs of the language >From 6527f595be5b219cb4e7eb7bf3917feda526464c Mon Sep 17 00:00:00 2001 From: Lucas <108239558+lkn...@users.noreply.github.com> Date: Wed, 3 Sep 2025 10:18:27 +0200 Subject: [PATCH 5/7] Fix: 'libraries and tool' to 'libraries and tools' --- clang/www/features.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clang/www/features.html b/clang/www/features.html index 4603d72a22528..01a7909b545ad 100755 --- a/clang/www/features.html +++ b/clang/www/features.html @@ -156,7 +156,7 @@ <h3><a name="libraryarch">Library Based Architecture</a></h3> any specific client."</p></blockquote> <p> -Currently, clang is divided into the following libraries and tool: +Currently, clang is divided into the following libraries and tools: </p> <ul> >From 68f19876b2ece567adcee8ffb3749d3ac789cce8 Mon Sep 17 00:00:00 2001 From: Lucas <108239558+lkn...@users.noreply.github.com> Date: Wed, 3 Sep 2025 10:23:29 +0200 Subject: [PATCH 6/7] Fix(suggestion): 'As an example of the power of this library based design' --- clang/www/features.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clang/www/features.html b/clang/www/features.html index 01a7909b545ad..2b3c1d97ba746 100755 --- a/clang/www/features.html +++ b/clang/www/features.html @@ -183,7 +183,7 @@ <h3><a name="libraryarch">Library Based Architecture</a></h3> levels.</li> </ul> -<p>As an example of the power of this library based design.... If you wanted to +<p>As some examples for the power of this library based design: If you wanted to build a preprocessor, you would take the Basic and Lexer libraries. If you want an indexer, you would take the previous two and add the Parser library and some actions for indexing. If you want a refactoring, static analysis, or >From 4259073d5ab42ac434ffa45a962dc8359d39c497 Mon Sep 17 00:00:00 2001 From: Lucas <108239558+lkn...@users.noreply.github.com> Date: Wed, 3 Sep 2025 10:26:00 +0200 Subject: [PATCH 7/7] Fix(plural rule): IDE's to IDEs --- clang/www/features.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clang/www/features.html b/clang/www/features.html index 2b3c1d97ba746..ff06671f4f32a 100755 --- a/clang/www/features.html +++ b/clang/www/features.html @@ -246,7 +246,7 @@ <h3 id="ideintegration">Integration with IDEs</h3> <!--=======================================================================--> <p> -We believe that Integrated Development Environments (IDE's) are a great way +We believe that Integrated Development Environments (IDEs) are a great way to pull together various pieces of the development puzzle, and aim to make clang work well in such an environment. The chief advantage of an IDE is that they typically have visibility across your entire project and are long-lived _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
