This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Using Go to build a shared library to be called from C

From: Ian Lance Taylor <iant at google dot com>
To: LRN <lrn1986 at gmail dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Mon, 13 Jun 2011 23:31:49 -0700
Subject: Re: Using Go to build a shared library to be called from C
References: <4DF6362F.7030003@gmail.com> <mcr1uyxtof9.fsf@coign.corp.google.com> <4DF68543.9050505@gmail.com>

LRN <lrn1986@gmail.com> writes:

> Anyway, if this situation is not going to change for some time, it
> might be a good thing to update the documentation to make it clear
> what works and what doesn't.

Yes, probably a good idea.

> Ah, and another thing. Does that apply to static linking as well? I
> suddenly realized that if it does, then why the hell the documentation
> even mentions C->Go interoperability?

A Go program can call C functions just fine.  Those C functions can call
Go code.  The problem is when your main function is in C, or when you
use shared libraries written in Go.

Ian

References:
- Using Go to build a shared library to be called from C
  - From: LRN
- Re: Using Go to build a shared library to be called from C
  - From: Ian Lance Taylor
- Re: Using Go to build a shared library to be called from C
  - From: LRN

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]