diff options
author | Andrew Gerrand <adg@golang.org> | 2012-03-27 12:46:46 +1100 |
---|---|---|
committer | Andrew Gerrand <adg@golang.org> | 2012-03-27 12:46:46 +1100 |
commit | 9031f952e2b17752f4eb716d4d96575026ce5338 (patch) | |
tree | 7f026c18b2e537eed3030450bf0a65fc38b72f47 | |
parent | 849ad2d0cac9b3ee97b3d331ca6e556a6073d94d (diff) | |
download | go-9031f952e2b17752f4eb716d4d96575026ce5338.tar.gz go-9031f952e2b17752f4eb716d4d96575026ce5338.zip |
doc: remove cov and prof from /ref/cmd
Update #3400
R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5921044
-rw-r--r-- | doc/reference-cmd.html | 38 |
1 files changed, 12 insertions, 26 deletions
diff --git a/doc/reference-cmd.html b/doc/reference-cmd.html index 442df0846b..b2cb2efa04 100644 --- a/doc/reference-cmd.html +++ b/doc/reference-cmd.html @@ -10,27 +10,25 @@ by the <a href="/cmd/go/">go</a> program. </p> <p> -The most common way to run these programs is as a subcommand of the go -program, -for instance as "go fmt". Run like this, the command operates on complete -packages of Go source code, with the go program invoking the underlying binary -with arguments appropriate to package-level processing. +The most common way to run these programs is as a subcommand of the go program, +for instance as <code>go fmt</code>. Run like this, the command operates on +complete packages of Go source code, with the go program invoking the +underlying binary with arguments appropriate to package-level processing. </p> <p> The programs can also be run as stand-alone binaries, with unmodified arguments, -using the go tool subcommand, such as "go tool vet". -This style of invocation allows, for instance, checking a single source file rather than -an entire package: "go tool vet myprogram.go" as compared to -"go vet mypackage". -Some of the commands, such as prof and yacc, are accessible -only through the go tool subcommand. +using the go <code>tool</code> subcommand, such as <code>go tool vet</code>. +This style of invocation allows, for instance, checking a single source file +rather than an entire package: <code>go tool vet myprogram.go</code> as +compared to <code>go vet mypackage</code>. +Some of the commands, such as <code>yacc</code>, are accessible only through +the go <code>tool</code> subcommand. </p> <p> -Finally, two of the commands, fmt and -doc, are also installed as regular binaries called -gofmt and godoc +Finally, two of the commands, <code>fmt</code> and <code>doc</code>, are also +installed as regular binaries called <code>gofmt</code> and <code>godoc</code> because they are so often referenced. </p> @@ -64,12 +62,6 @@ details. </tr> <tr> -<td><a href="/cmd/cov/">cov</a></td> -<td> </td> -<td>Cov is a rudimentary code coverage tool.</td> -</tr> - -<tr> <td><a href="/cmd/fix/">fix</a></td> <td> </td> <td>Fix finds Go programs that use old features of the language and libraries @@ -91,12 +83,6 @@ gofmt</a> command with more general options.</td> </tr> <tr> -<td><a href="/cmd/prof/">prof</a></td> -<td> </td> -<td>Prof is a rudimentary real-time profiler.</td> -</tr> - -<tr> <td><a href="/cmd/vet/">vet</a></td> <td> </td> <td>Vet examines Go source code and reports suspicious constructs, such as Printf |