diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/articles/go_command.html | 2 | ||||
| -rw-r--r-- | doc/articles/race_detector.html | 24 | ||||
| -rw-r--r-- | doc/contribute.html | 16 | ||||
| -rw-r--r-- | doc/debugging_with_gdb.html | 50 | ||||
| -rw-r--r-- | doc/effective_go.html | 4 | ||||
| -rw-r--r-- | doc/gccgo_contribute.html | 2 | ||||
| -rw-r--r-- | doc/go_faq.html | 4 |
7 files changed, 51 insertions, 51 deletions
diff --git a/doc/articles/go_command.html b/doc/articles/go_command.html index fddca41e2..246b8c956 100644 --- a/doc/articles/go_command.html +++ b/doc/articles/go_command.html @@ -99,7 +99,7 @@ deduce where to obtain the source code.</p> in a known way from the import path. Specifically, the first choice is <code>$GOPATH/src/<import-path></code>. If <code>$GOPATH</code> is unset, the go command will fall back to storing source code alongside the -standard Go packages, in <code>$GOROOT/src/pkg/<import-path></code>. +standard Go packages, in <code>$GOROOT/src/<import-path></code>. If <code>$GOPATH</code> is set to a list of paths, the go command tries <code><dir>/src/<import-path></code> for each of the directories in that list.</p> diff --git a/doc/articles/race_detector.html b/doc/articles/race_detector.html index 32ad61de8..6defd98f9 100644 --- a/doc/articles/race_detector.html +++ b/doc/articles/race_detector.html @@ -57,35 +57,35 @@ Here is an example: WARNING: DATA RACE Read by goroutine 185: net.(*pollServer).AddFD() - src/pkg/net/fd_unix.go:89 +0x398 + src/net/fd_unix.go:89 +0x398 net.(*pollServer).WaitWrite() - src/pkg/net/fd_unix.go:247 +0x45 + src/net/fd_unix.go:247 +0x45 net.(*netFD).Write() - src/pkg/net/fd_unix.go:540 +0x4d4 + src/net/fd_unix.go:540 +0x4d4 net.(*conn).Write() - src/pkg/net/net.go:129 +0x101 + src/net/net.go:129 +0x101 net.func·060() - src/pkg/net/timeout_test.go:603 +0xaf + src/net/timeout_test.go:603 +0xaf Previous write by goroutine 184: net.setWriteDeadline() - src/pkg/net/sockopt_posix.go:135 +0xdf + src/net/sockopt_posix.go:135 +0xdf net.setDeadline() - src/pkg/net/sockopt_posix.go:144 +0x9c + src/net/sockopt_posix.go:144 +0x9c net.(*conn).SetDeadline() - src/pkg/net/net.go:161 +0xe3 + src/net/net.go:161 +0xe3 net.func·061() - src/pkg/net/timeout_test.go:616 +0x3ed + src/net/timeout_test.go:616 +0x3ed Goroutine 185 (running) created at: net.func·061() - src/pkg/net/timeout_test.go:609 +0x288 + src/net/timeout_test.go:609 +0x288 Goroutine 184 (running) created at: net.TestProlongTimeout() - src/pkg/net/timeout_test.go:618 +0x298 + src/net/timeout_test.go:618 +0x298 testing.tRunner() - src/pkg/testing/testing.go:301 +0xe8 + src/testing/testing.go:301 +0xe8 </pre> <h2 id="Options">Options</h2> diff --git a/doc/contribute.html b/doc/contribute.html index 849c1e476..90c3f10a1 100644 --- a/doc/contribute.html +++ b/doc/contribute.html @@ -234,9 +234,9 @@ Description: <enter description here> Files: - src/pkg/math/sin.go - src/pkg/math/tan.go - src/pkg/regexp/regexp.go + src/math/sin.go + src/math/tan.go + src/regexp/regexp.go </pre> <p> @@ -287,8 +287,8 @@ Description: Fixes issue 159. Files: - src/pkg/math/sin.go - src/pkg/math/tan.go + src/math/sin.go + src/math/tan.go </pre> <p> @@ -457,11 +457,11 @@ adding changesets adding manifests adding file changes added 1 changeset with 2 changes to 2 files -getting src/pkg/flag/flag.go +getting src/flag/flag.go couldn't find merge tool hgmerge -merging src/pkg/flag/flag_test.go +merging src/flag/flag_test.go warning: conflicts during merge. -<i>merging src/pkg/flag/flag_test.go failed!</i> +<i>merging src/flag/flag_test.go failed!</i> 1 file updated, 0 files merged, 0 files removed, 1 file unresolved use 'hg resolve' to retry unresolved file merges $ diff --git a/doc/debugging_with_gdb.html b/doc/debugging_with_gdb.html index afaedf74c..836816419 100644 --- a/doc/debugging_with_gdb.html +++ b/doc/debugging_with_gdb.html @@ -120,7 +120,7 @@ For example: <p> If you'd like to see how this works, or want to extend it, take a look at <a -href="/src/pkg/runtime/runtime-gdb.py">src/pkg/runtime/runtime-gdb.py</a> in +href="/src/runtime/runtime-gdb.py">src/runtime/runtime-gdb.py</a> in the Go source distribution. It depends on some special magic types (<code>hash<T,U></code>) and variables (<code>runtime.m</code> and <code>runtime.g</code>) that the linker @@ -153,7 +153,7 @@ the form <code>pkg.(*MyType).Meth</code>. <p> In this tutorial we will inspect the binary of the <a href="/pkg/regexp/">regexp</a> package's unit tests. To build the binary, -change to <code>$GOROOT/src/pkg/regexp</code> and run <code>go test -c</code>. +change to <code>$GOROOT/src/regexp</code> and run <code>go test -c</code>. This should produce an executable file named <code>regexp.test</code>. </p> @@ -172,7 +172,7 @@ License GPLv 3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.htm Type "show copying" and "show warranty" for licensing/warranty details. This GDB was configured as "x86_64-linux". -Reading symbols from /home/user/go/src/pkg/regexp/regexp.test... +Reading symbols from /home/user/go/src/regexp/regexp.test... done. Loading Go Runtime support. (gdb) @@ -180,7 +180,7 @@ Loading Go Runtime support. <p> The message <code>"Loading Go Runtime support"</code> means that GDB loaded the -extension from <code>$GOROOT/src/pkg/runtime/runtime-gdb.py</code>. +extension from <code>$GOROOT/src/runtime/runtime-gdb.py</code>. </p> <p> @@ -199,7 +199,7 @@ it by hand by telling gdb (assuming you have the go sources in </p> <pre> -(gdb) <b>source ~/go/src/pkg/runtime/runtime-gdb.py</b> +(gdb) <b>source ~/go/src/runtime/runtime-gdb.py</b> Loading Go Runtime support. </pre> @@ -259,7 +259,7 @@ Set a breakpoint at the <code>TestFind</code> function: <pre> (gdb) <b>b 'regexp.TestFind'</b> -Breakpoint 1 at 0x424908: file /home/user/go/src/pkg/regexp/find_test.go, line 148. +Breakpoint 1 at 0x424908: file /home/user/go/src/regexp/find_test.go, line 148. </pre> <p> @@ -268,9 +268,9 @@ Run the program: <pre> (gdb) <b>run</b> -Starting program: /home/user/go/src/pkg/regexp/regexp.test +Starting program: /home/user/go/src/regexp/regexp.test -Breakpoint 1, regexp.TestFind (t=0xf8404a89c0) at /home/user/go/src/pkg/regexp/find_test.go:148 +Breakpoint 1, regexp.TestFind (t=0xf8404a89c0) at /home/user/go/src/regexp/find_test.go:148 148 func TestFind(t *testing.T) { </pre> @@ -297,9 +297,9 @@ Look at the stack trace for where we’ve paused the program: <pre> (gdb) <b>bt</b> <i># backtrace</i> -#0 regexp.TestFind (t=0xf8404a89c0) at /home/user/go/src/pkg/regexp/find_test.go:148 -#1 0x000000000042f60b in testing.tRunner (t=0xf8404a89c0, test=0x573720) at /home/user/go/src/pkg/testing/testing.go:156 -#2 0x000000000040df64 in runtime.initdone () at /home/user/go/src/pkg/runtime/proc.c:242 +#0 regexp.TestFind (t=0xf8404a89c0) at /home/user/go/src/regexp/find_test.go:148 +#1 0x000000000042f60b in testing.tRunner (t=0xf8404a89c0, test=0x573720) at /home/user/go/src/testing/testing.go:156 +#2 0x000000000040df64 in runtime.initdone () at /home/user/go/src/runtime/proc.c:242 #3 0x000000f8404a89c0 in ?? () #4 0x0000000000573720 in ?? () #5 0x0000000000000000 in ?? () @@ -311,18 +311,18 @@ The other goroutine, number 1, is stuck in <code>runtime.gosched</code>, blocked <pre> (gdb) <b>goroutine 1 bt</b> -#0 0x000000000040facb in runtime.gosched () at /home/user/go/src/pkg/runtime/proc.c:873 +#0 0x000000000040facb in runtime.gosched () at /home/user/go/src/runtime/proc.c:873 #1 0x00000000004031c9 in runtime.chanrecv (c=void, ep=void, selected=void, received=void) - at /home/user/go/src/pkg/runtime/chan.c:342 -#2 0x0000000000403299 in runtime.chanrecv1 (t=void, c=void) at/home/user/go/src/pkg/runtime/chan.c:423 + at /home/user/go/src/runtime/chan.c:342 +#2 0x0000000000403299 in runtime.chanrecv1 (t=void, c=void) at/home/user/go/src/runtime/chan.c:423 #3 0x000000000043075b in testing.RunTests (matchString={void (struct string, struct string, bool *, error *)} - 0x7ffff7f9ef60, tests= []testing.InternalTest = {...}) at /home/user/go/src/pkg/testing/testing.go:201 + 0x7ffff7f9ef60, tests= []testing.InternalTest = {...}) at /home/user/go/src/testing/testing.go:201 #4 0x00000000004302b1 in testing.Main (matchString={void (struct string, struct string, bool *, error *)} 0x7ffff7f9ef80, tests= []testing.InternalTest = {...}, benchmarks= []testing.InternalBenchmark = {...}) -at /home/user/go/src/pkg/testing/testing.go:168 -#5 0x0000000000400dc1 in main.main () at /home/user/go/src/pkg/regexp/_testmain.go:98 -#6 0x00000000004022e7 in runtime.mainstart () at /home/user/go/src/pkg/runtime/amd64/asm.s:78 -#7 0x000000000040ea6f in runtime.initdone () at /home/user/go/src/pkg/runtime/proc.c:243 +at /home/user/go/src/testing/testing.go:168 +#5 0x0000000000400dc1 in main.main () at /home/user/go/src/regexp/_testmain.go:98 +#6 0x00000000004022e7 in runtime.mainstart () at /home/user/go/src/runtime/amd64/asm.s:78 +#7 0x000000000040ea6f in runtime.initdone () at /home/user/go/src/runtime/proc.c:243 #8 0x0000000000000000 in ?? () </pre> @@ -333,7 +333,7 @@ The stack frame shows we’re currently executing the <code>regexp.TestFind</cod <pre> (gdb) <b>info frame</b> Stack level 0, frame at 0x7ffff7f9ff88: - rip = 0x425530 in regexp.TestFind (/home/user/go/src/pkg/regexp/find_test.go:148); + rip = 0x425530 in regexp.TestFind (/home/user/go/src/regexp/find_test.go:148); saved rip 0x430233 called by frame at 0x7ffff7f9ffa8 source language minimal. @@ -410,7 +410,7 @@ We can step into the <code>String</code>function call with <code>"s"</code>: <pre> (gdb) <b>s</b> -regexp.(*Regexp).String (re=0xf84068d070, noname=void) at /home/user/go/src/pkg/regexp/regexp.go:97 +regexp.(*Regexp).String (re=0xf84068d070, noname=void) at /home/user/go/src/regexp/regexp.go:97 97 func (re *Regexp) String() string { </pre> @@ -421,12 +421,12 @@ Get a stack trace to see where we are: <pre> (gdb) <b>bt</b> #0 regexp.(*Regexp).String (re=0xf84068d070, noname=void) - at /home/user/go/src/pkg/regexp/regexp.go:97 + at /home/user/go/src/regexp/regexp.go:97 #1 0x0000000000425615 in regexp.TestFind (t=0xf840688b60) - at /home/user/go/src/pkg/regexp/find_test.go:151 + at /home/user/go/src/regexp/find_test.go:151 #2 0x0000000000430233 in testing.tRunner (t=0xf840688b60, test=0x5747b8) - at /home/user/go/src/pkg/testing/testing.go:156 -#3 0x000000000040ea6f in runtime.initdone () at /home/user/go/src/pkg/runtime/proc.c:243 + at /home/user/go/src/testing/testing.go:156 +#3 0x000000000040ea6f in runtime.initdone () at /home/user/go/src/runtime/proc.c:243 .... </pre> diff --git a/doc/effective_go.html b/doc/effective_go.html index c1e310796..4dd1a3e01 100644 --- a/doc/effective_go.html +++ b/doc/effective_go.html @@ -37,7 +37,7 @@ should read first. <h3 id="examples">Examples</h3> <p> -The <a href="/src/pkg/">Go package sources</a> +The <a href="/src/">Go package sources</a> are intended to serve not only as the core library but also as examples of how to use the language. @@ -344,7 +344,7 @@ determines just which package is being used. <p> Another convention is that the package name is the base name of its source directory; -the package in <code>src/pkg/encoding/base64</code> +the package in <code>src/encoding/base64</code> is imported as <code>"encoding/base64"</code> but has name <code>base64</code>, not <code>encoding_base64</code> and not <code>encodingBase64</code>. </p> diff --git a/doc/gccgo_contribute.html b/doc/gccgo_contribute.html index 9dd6ecb85..db7d1ab0e 100644 --- a/doc/gccgo_contribute.html +++ b/doc/gccgo_contribute.html @@ -73,7 +73,7 @@ script <code>libgo/merge.sh</code>. Accordingly, most library changes should be made in the main Go repository. The files outside of <code>libgo/go</code> are gccgo-specific; that said, some of the files in <code>libgo/runtime</code> are based on files -in <code>src/pkg/runtime</code> in the main Go repository. +in <code>src/runtime</code> in the main Go repository. </p> <h2>Testing</h2> diff --git a/doc/go_faq.html b/doc/go_faq.html index f2082ef5b..4e90d3907 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -971,7 +971,7 @@ It is a handy reference for people doing code reviews for Go projects. How do I submit patches to the Go libraries?</h3> <p> -The library sources are in <code>go/src/pkg</code>. +The library sources are in <code>go/src</code>. If you want to make a significant change, please discuss on the mailing list before embarking. </p> @@ -1571,7 +1571,7 @@ table-driven, iterating over a list of inputs and outputs defined in a data structure (Go has excellent support for data structure literals). The work to write a good test and good error messages will then be amortized over many test cases. The standard Go library is full of illustrative examples, such as in -<a href="/src/pkg/fmt/fmt_test.go">the formatting tests for the <code>fmt</code> package</a>. +<a href="/src/fmt/fmt_test.go">the formatting tests for the <code>fmt</code> package</a>. </p> |