summaryrefslogtreecommitdiff
path: root/Doc/Manual/Go.html
diff options
context:
space:
mode:
authorMichael Schaller <michael@5challer.de>2015-08-27 10:07:45 +0200
committerMichael Schaller <michael@5challer.de>2015-08-27 10:09:50 +0200
commitd5cf0ab1110a81482d725d5abf0f0af44ebbcd21 (patch)
tree216ba973ca5384daf45ba18f7468f55619dfb919 /Doc/Manual/Go.html
parent8d2f3403d285f448d3e50d56449ecaa82f554cdd (diff)
downloadswig-d5cf0ab1110a81482d725d5abf0f0af44ebbcd21.tar.gz
First batch of changes after code review by @ianlancetaylor for pull request #502.
Diffstat (limited to 'Doc/Manual/Go.html')
-rw-r--r--Doc/Manual/Go.html11
1 files changed, 5 insertions, 6 deletions
diff --git a/Doc/Manual/Go.html b/Doc/Manual/Go.html
index 7531a218c..a62efec43 100644
--- a/Doc/Manual/Go.html
+++ b/Doc/Manual/Go.html
@@ -67,10 +67,9 @@ code. SWIG fills this gap.
</p>
<p>
-There are (at least) two different Go compilers. The first is the Go compiler
-of the <a href="https://golang.org/doc/install">Go distribution</a>.
-Since Go 1.5 the Go compiler is part of the <a href="https://golang.org/cmd/go/">
-go tool</a>. Go 1.4 and earlier use the gc tool which is called by the go tool.
+There are (at least) two different Go compilers. The first is the gc compiler
+of the <a href="https://golang.org/doc/install">Go distribution</a>, normally
+invoked via the <a href="https://golang.org/cmd/go/">go tool</a>.
The second Go compiler is the <a href="https://golang.org/doc/install/gccgo">
gccgo compiler</a>, which is a frontend to the GCC compiler suite.
The interface to C/C++ code is completely different for the two Go compilers.
@@ -120,8 +119,8 @@ temporary WORK directory.
<p>
To manually generate and compile C/C++ wrapper code for Go, use the <tt>-go</tt>
option with SWIG. By default SWIG will generate code for the Go compiler of the
-Go distribution. To generate code for gccgo, you should also use the <tt>-gccgo
-</tt> option.
+Go distribution. To generate code for gccgo, you should also use the
+<tt>-gccgo</tt> option.
</p>
<p>