diff options
| author | Andrew Gerrand <adg@golang.org> | 2014-09-12 07:26:02 +1000 |
|---|---|---|
| committer | Andrew Gerrand <adg@golang.org> | 2014-09-12 07:26:02 +1000 |
| commit | 63173935e06d26c8f9295a191577355d6f0d15b7 (patch) | |
| tree | 7733bc675725a86f1138c21e3779b4f90d711f24 | |
| parent | 0f4f2b91480c6f15a10e5bc59b98d06a008b3056 (diff) | |
go.blog: fix links in "Introducing Gofix"
Fixes golang/go#8692.
LGTM=iant
R=golang-codereviews, iant
CC=golang-codereviews
https://golang.org/cl/141420043
| -rw-r--r-- | content/introducing-gofix.article | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/introducing-gofix.article b/content/introducing-gofix.article index 2a6e198..2e64e4e 100644 --- a/content/introducing-gofix.article +++ b/content/introducing-gofix.article @@ -12,7 +12,7 @@ The next Go release will include significant API changes in several fundamental Each time we make a significant API change we’ll add code to gofix to take care of the conversion, as much as mechanically possible. When you update to a new Go release and your code no longer builds, just run gofix on your source directory. -You can extend gofix to support changes to your own APIs. The gofix program is a simple driver around plugins called fixes that each handle a particular API change. Right now, writing a new fix requires doing some scanning and rewriting of the go/ast syntax tree, usually in proportion to how complex the API changes are. If you want to explore, the [[http://code.google.com/p/go/source/browse/src/cmd/gofix/netdial.go][`netdialFix`]], [[http://code.google.com/p/go/source/browse/src/cmd/gofix/osopen.go][`osopenFix`]], [[http://code.google.com/p/go/source/browse/src/cmd/gofix/httpserver.go][`httpserverFix`]], and [[http://code.google.com/p/go/source/browse/src/cmd/gofix/reflect.go][`reflectFix`]] are all illustrative examples, in increasing order of complexity. +You can extend gofix to support changes to your own APIs. The gofix program is a simple driver around plugins called fixes that each handle a particular API change. Right now, writing a new fix requires doing some scanning and rewriting of the go/ast syntax tree, usually in proportion to how complex the API changes are. If you want to explore, the [[https://code.google.com/p/go/source/browse/src/cmd/fix/netdial.go?name=go1][`netdialFix`]], [[http://code.google.com/p/go/source/browse/src/cmd/fix/osopen.go?name=go1][`osopenFix`]], [[http://code.google.com/p/go/source/browse/src/cmd/fix/httpserver.go?name=go1][`httpserverFix`]], and [[http://code.google.com/p/go/source/browse/src/cmd/fix/reflect.go?name=go1][`reflectFix`]] are all illustrative examples, in increasing order of complexity. We write Go code too, of course, and our code is just as affected by these API changes as yours. Typically, we write the gofix support at the same time as the API change and then use gofix to rewrite the uses in the main source tree. We use gofix to update other Go code bases and our personal projects. We even use gofix to update Google’s internal source tree when it is time to build against a new Go release. |