1
0
mirror of https://github.com/golang/go synced 2024-11-20 01:34:41 -07:00
go/src/cmd/dist
Shenghou Ma faef52c214 all: fix typos
R=golang-dev, bradfitz, khr, r
CC=golang-dev
https://golang.org/cl/7461046
2013-06-09 21:50:24 +08:00
..
a.h cmd/dist, cmd/ld: GO_EXTLINK_ENABLED=0 defaults to -linkmode=internal 2013-03-29 16:33:35 -07:00
arg.h build: dist-based build for Plan 9 2012-05-01 22:32:46 -07:00
arm.c cmd/dist: support for NetBSD/ARM 2013-03-03 06:50:17 +08:00
buf.c cmd/dist: clear execute bit from source file 2012-02-11 13:23:44 +09:00
build.c cmd/cov: delete 2013-05-24 11:06:06 -07:00
buildgc.c build: dist-based build for Plan 9 2012-05-01 22:32:46 -07:00
buildruntime.c cmd/5a, cmd/dist, runtime: support m/g in the assembler, drop support for R9/R10 2013-05-30 03:03:52 +08:00
goc2c.c runtime/bytes: fast Compare for byte arrays and strings. 2013-05-14 16:05:51 -07:00
main.c
plan9.c all: fix typos 2013-06-09 21:50:24 +08:00
README cmd/dist: fix code example in README 2013-01-30 08:46:50 -08:00
unix.c all: fix typos 2013-06-09 21:50:24 +08:00
windows.c lib9: add mktempdir, removeall, runprog 2013-03-06 15:48:28 -05:00

This program, dist, is the bootstrapping tool for the Go distribution.
It takes care of building the C programs (like the Go compiler) and
the initial bootstrap copy of the go tool.  It also serves as a catch-all
to replace odd jobs previously done with shell scripts.

Dist is itself written in very simple C.  All interaction with C libraries,
even standard C libraries, is confined to a single system-specific file
(plan9.c, unix.c, windows.c), to aid portability.  Functionality needed
by other files should be exposed via the portability layer.  Functions
in the portability layer begin with an x prefix when they would otherwise
use the same name as or be confused for an existing function.
For example, xprintf is the portable printf.

By far the most common data types in dist are strings and arrays of
strings.  Instead of using char* and char**, though, dist uses two named
data structures, Buf and Vec, which own all the data they point at.
The Buf operations are functions beginning with b; the Vec operations
are functions beginning with v.  The basic form of any function declaring
Bufs or Vecs on the stack should be

	void
	myfunc(void)
	{
		Buf b1, b2;
		Vec v1;
		
		binit(&b1);
		binit(&b2);
		vinit(&v1);
		
		... main code ...
		bprintf(&b1, "hello, world");
		vadd(&v1, bstr(&b1));  // v1 takes a copy of its argument
		bprintf(&b2, "another string");
		vadd(&v1, bstr(&b2));  // v1 now has two strings
		
		bfree(&b1);
		bfree(&b2);
		vfree(&v1);
	}
	
The binit/vinit calls prepare a buffer or vector for use, initializing the 
data structures, and the bfree/vfree calls free any memory they are still
holding onto.  Use of this idiom gives us lexically scoped allocations.