Re: [go-nuts] Thread local error information when wrapping lib with cgo

On Wed, Apr 5, 2017 at 10:32 PM, distributed wrote: > > Thanks for the clarification. I suppose internal UnlockOSThread does not > override the runtime.LockOSThread by my code from the outside? Correct. Ian -- You received this message because you are subscribed to the Google Groups "golang-n

Re: [go-nuts] Thread local error information when wrapping lib with cgo

Thanks for the clarification. I suppose internal UnlockOSThread does not override the runtime.LockOSThread by my code from the outside? Not really. On error you could malloc a buffer, copy in the string, > and return the buffer to Go. In Go you could copy the buffer into Go > memory and C.fre

Re: [go-nuts] Thread local error information when wrapping lib with cgo

On Wed, Apr 5, 2017 at 12:22 AM, distributed wrote: > I am currently wrapping a proprietary library with cgo. > > About error reporting, the library documentation says "Every function that > can fail returns at least boolean or pointer value that can be used to > detect error state (false and NULL