From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <631828b4eaee51d49ac685c47b6b3554@proxima.alt.za>
References: <631828b4eaee51d49ac685c47b6b3554@proxima.alt.za>
From: =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= <aram.h@mgk.ro>
Date: Sat,  2 Feb 2013 15:28:40 +0100
Message-ID: <CAEAzY395bTyA0_6Oc18x3VPBOEXN0hC371QAW7N4oLN7h14n8w@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Go: CGO and Plan 9
Topicbox-Message-UUID: 13e9a7ca-ead8-11e9-9d60-3106f5b1d025

?c and ?g use the same calling convention, and segmented stacks are
implemented by the linker. You don't need cgo in order to call C code
from Go. Why do you want cgo?

Look at the various C files in the Go standard library, especially
inside runtime. Those are compiled with the Plan 9 compiler and Go
calls it just fine.

--=20
Aram H=C4=83v=C4=83rneanu