First batch of changes after code review by @ianlancetaylor for pull request #502.

This commit is contained in:
Michael Schaller 2015-08-27 10:07:45 +02:00
commit d5cf0ab111

View file

@ -67,10 +67,9 @@ code. SWIG fills this gap.
</p> </p>
<p> <p>
There are (at least) two different Go compilers. The first is the Go compiler 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>. of the <a href="https://golang.org/doc/install">Go distribution</a>, normally
Since Go 1.5 the Go compiler is part of the <a href="https://golang.org/cmd/go/"> invoked via the <a href="https://golang.org/cmd/go/">go tool</a>.
go tool</a>. Go 1.4 and earlier use the gc tool which is called by the go tool.
The second Go compiler is the <a href="https://golang.org/doc/install/gccgo"> 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. 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. The interface to C/C++ code is completely different for the two Go compilers.
@ -120,8 +119,8 @@ temporary WORK directory.
<p> <p>
To manually generate and compile C/C++ wrapper code for Go, use the <tt>-go</tt> 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 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 Go distribution. To generate code for gccgo, you should also use the
</tt> option. <tt>-gccgo</tt> option.
</p> </p>
<p> <p>