[nanomsg] Re: mangos, nanomsg, shared libs in Go

  • From: Steve Vinoski <vinoski@xxxxxxxx>
  • To: nanomsg <nanomsg@xxxxxxxxxxxxx>
  • Date: Wed, 27 May 2015 23:29:10 -0400

On Wed, May 27, 2015 at 10:23 PM, Jason E. Aten <j.e.aten@xxxxxxxxx> wrote:

On Wed, May 27, 2015 at 2:30 PM, Steve Vinoski <vinoski@xxxxxxxx> wrote:

Write, maintain, and extend, but not embed.


That *was the point* of Martin's message. The announcement yesterday in
Andrew Gerrand's talk at Gopherfest was that, as of Go 1.5, to be released
in August, Go code will be easy to embed in C code.


Thanks for the explanation. I pay no attention whatsoever to anything
Go-related, so I don't know how I could have been expected to decode these
details from Martin's message alone.


The go compiler will now be able to produce shared objects that can be
dynamically linked into C code.


And you can guarantee there'll be no unwanted interactions between the
Erlang runtime and the Go runtime?

Canonical needed this feature as their package policy requires it. I assume
by didn't confirm that Dave Cheney implemented it.


I pay zero attention to Go, so sorry but these names are meaningless to me.

I changed jobs last December and so I don't even use nanomsg anymore. I
still maintain the Erlang enm library, though, because I wrote it and it
doesn't take much time. But if the nanomsg runtime switches to Go, I won't
have the need or the cycles to deal with it, so hopefully someone else who
cares about using the new runtime with Erlang -- if that will even be
possible -- will write a replacement for enm.

--steve




Cheers,
Jason


Other related posts:

  1. Home
  2. nanomsg
  3. Archive
  4. 05-2015