From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 19 Feb 2013 15:33:52 -0800
From: Anthony Martin <ality@pbrane.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <20130219233352.GA9880@dinah>
References: <CAOw7k5hvnDL8ZGHQdLfcpQ3QriU+Hs4DeJ4FUPqGwRwo9CTqNw@mail.gmail.com>
	<bce170e796ad92bb8a539a4d5db7d4f9@proxima.alt.za>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <bce170e796ad92bb8a539a4d5db7d4f9@proxima.alt.za>
Subject: Re: [9fans] going too far?
Topicbox-Message-UUID: 1ae38712-ead8-11e9-9d60-3106f5b1d025

lucio@proxima.alt.za once said:
> I think the Go tool does cover C programs and even (somebody will
> correct me if I'm wrong, I hope) assembler ones.  It would be silly if
> it didn't, or at least hard to use for things like the runtime.  One
> of Go's weak spots is that a lot of unconventional behaviour is poorly
> documented.  But I'm sure third party documentation will come soon.

This is correct. The go tool supports files with an
extension matching (go|[chsS]|swig(cxx)?|syso).

For .go files, each file is read until the end of the
import declarations.

For everything else (except .syso), each file is read
to determine the build constraints. The rules for these
are explained here

	http://golang.org/pkg/go/build/#hdr-Build_Constraints

Files with the extension .syso are not read by the
go tool. They're opaque externally-generated blobs
that are simply added to the archive before linking.

  Anthony