Hi, My use case is very very particular and unlikely to be related to most cgo use cases.
The use case requires that there is no C calling of Go. the requirements arise from a special set of circumstances, including 1. if C calls Go, then it is on a thread created in C 2. the thread above and expectations by the OS of what the call should not do are such that go's runtime treatment of cgo->go on the foreign thread is undesirable. So I need to call C without calling by Go //export in this very particular case. Scott On Mon, 1 Oct 2018 at 10:42, Tamás Gulácsi <tgulacs...@gmail.com> wrote: > Sorry, I don't understand this. > > Why can't you `//export` a Go function in package A - a function which > calls your cgo function? > > And why can't you `//export` a Go function in package B - a function which > calls the exported Go function in package A ??? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/golang-nuts/ruLltGrPWBg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Scott Cotton http://www.iri-labs.com -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
