[go-nuts] Re: annoing: runtime error: cgo argument has Go pointer to Go pointer

2020-01-29 Thread Tamás Gulácsi
What does "argv" hold? Can it be a concrete type, not an interface ? That would allow passing it - or if you copy it to a C.malloc-ed array.. 2020. január 29., szerda 23:12:37 UTC+1 időpontban aotto1...@gmail.com a következőt írta: > > Hi, > > I try to use a *C* library with *GO* and have a sma

[go-nuts] Re: annoing: runtime error: cgo argument has Go pointer to Go pointer

2020-01-29 Thread Andreas Otto
Am Donnerstag, 30. Januar 2020 06:15:28 UTC+1 schrieb Tamás Gulácsi: > > What does "argv" hold? > > Can it be a concrete type, not an interface ? That would allow passing it > - or if you copy it to a C.malloc-ed array.. > > > *Argv* are the arguments of *Send* and many kind of types are are su

[go-nuts] Re: annoing: runtime error: cgo argument has Go pointer to Go pointer

2020-01-30 Thread Tamás Gulácsi
2020. január 30., csütörtök 8:27:14 UTC+1 időpontban Andreas Otto a következőt írta: > > > > Am Donnerstag, 30. Januar 2020 06:15:28 UTC+1 schrieb Tamás Gulácsi: >> >> What does "argv" hold? >> >> Can it be a concrete type, not an interface ? That would allow passing it >> - or if you copy it to

[go-nuts] Re: annoing: runtime error: cgo argument has Go pointer to Go pointer

2020-01-31 Thread Andreas Otto
I do nothing on *C* with this pointer… I just give the Pointer as Argument to an *GO* callback. Am Donnerstag, 30. Januar 2020 14:25:48 UTC+1 schrieb Tamás Gulácsi: > > > > How do you handle the interface types on the C side? If you call back to > Go exported functions, > then you shouldn't tra

[go-nuts] Re: annoing: runtime error: cgo argument has Go pointer to Go pointer

2020-02-01 Thread Andreas Otto
No, because this is a *printf *like feature and the *callSig* is the format and the *option[] *are the arguments, which support many different types… Am Donnerstag, 30. Januar 2020 06:15:28 UTC+1 schrieb Tamás Gulácsi: > > What does "argv" hold? > > Can it be a concrete type, not an interface ? T