aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRob Pike <r@golang.org>2010-04-07 16:13:14 -0700
committerRob Pike <r@golang.org>2010-04-07 16:13:14 -0700
commita3db32d2a641f8d2d8a0e37e8ae226134b85dd79 (patch)
tree4fbeaec22fd22ba054cbe6be86aee76d906238bb
parent956926ee31af1d7901d9e04c7eeab2c84aa8b212 (diff)
downloadgo-a3db32d2a641f8d2d8a0e37e8ae226134b85dd79.tar.gz
go-a3db32d2a641f8d2d8a0e37e8ae226134b85dd79.zip
Language FAQ: editing tweaks after iant.
R=iant CC=golang-dev https://golang.org/cl/874043
-rw-r--r--doc/go_lang_faq.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/go_lang_faq.html b/doc/go_lang_faq.html
index 2fd71936ba..b8deb15343 100644
--- a/doc/go_lang_faq.html
+++ b/doc/go_lang_faq.html
@@ -282,14 +282,14 @@ This remains an open issue.
<h3 id="exceptions">
Why does Go not have exceptions?</h3>
<p>
-We believe that coupling the usual idea of exceptions to a control
+We believe that coupling exceptions to a control
structure, as in the <code>try-catch-finally</code> idiom, results in
convoluted code. It also tends to encourage programmers to label
too many ordinary errors, such as failing to open a file, as
-exceptional. And then the type system gets mixed in.
+exceptional.
</p>
<p>
-Go takes a different approach. Instead of exceptions, it has couple
+Go takes a different approach. Instead of exceptions, it has a couple
of built-in functions to signal and recover from truly exceptional
conditions. The recovery mechanism is executed only as part of a
function's state being torn down after an error, which is sufficient