From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] going too far?
Date: Tue, 19 Feb 2013 13:57:13 +0200 [thread overview]
Message-ID: <bce170e796ad92bb8a539a4d5db7d4f9@proxima.alt.za> (raw)
In-Reply-To: <CAOw7k5hvnDL8ZGHQdLfcpQ3QriU+Hs4DeJ4FUPqGwRwo9CTqNw@mail.gmail.com>
> On 19 February 2013 10:05, Bruce Ellis <bruce.ellis@gmail.com> wrote:
>
>> i could only presume that the #includes are expected to be in the first
>> block.
>
>
> that would be all right, I suppose, but I didn't think the go command
> compiled C programs as well
> (or at least, that's what I'd read). It's a bit like PIP, though, so
> perhaps it does.
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.
++L
next prev parent reply other threads:[~2013-02-19 11:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 18:15 Francisco J Ballesteros
2013-02-18 18:41 ` John Floren
2013-02-18 19:22 ` andrey mirtchovski
2013-02-18 19:23 ` andrey mirtchovski
2013-02-19 1:36 ` Charles Forsyth
2013-02-19 1:39 ` Charles Forsyth
2013-02-19 1:57 ` andrey mirtchovski
2013-02-19 2:27 ` erik quanstrom
2013-02-19 4:14 ` erik quanstrom
2013-02-19 3:07 ` andrey mirtchovski
2013-02-19 9:32 ` Charles Forsyth
2013-02-19 10:05 ` Bruce Ellis
2013-02-19 10:33 ` Charles Forsyth
2013-02-19 11:57 ` lucio [this message]
2013-02-19 23:33 ` Anthony Martin
2013-02-20 8:06 ` [9fans] Go tool capabilities (Was: going too far?) lucio
2013-02-20 8:06 ` lucio
2013-02-19 2:29 ` [9fans] going too far? erik quanstrom
2013-02-19 3:08 ` andrey mirtchovski
2013-02-19 3:22 ` erik quanstrom
2013-02-20 11:45 ` Anthony Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bce170e796ad92bb8a539a4d5db7d4f9@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).