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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



LRN <lrn1986@xxxxxxxxx> 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


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux