[go-nuts] cgo: curious why this type conversion works

[go-nuts] cgo: curious why this type conversion works

	Kevin Malachowski
	Dec 21, 2015 at 2:34 am

There are new explicit rules about when its safe to pass memory between Go and C: https://tip.golang.org/doc/go1.6#cgo

I'm guessing that both conversions work because both uint8_t and uchar are the same thing? I haven't done a lot of C recently, but arent all three types unsigned, 8-bit numbers?

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts

Tim K: I was pretty sure that for the following type conversions I would have to go through an intermediate type conversion to unsafe.Pointer, but to my beginner surprise this works: var x [5]byte C.f1( (*C.uint8_t)(&x[0]), 5, ... ) C.f2( (*C.uchar)(&x[0]), 5, ... ) Is it because C.uint8_t and C.uchar are aliases for byte? Something else? And I assume it's safe to pass a Go byte buffer like this to a C function to directly fill it out with data, correct? I don't need to C.malloc (and later C.free) a C

Follow ups

Related Discussions

Discussion Navigation

view	thread \| post
posts	‹ prev \| 2 of 5 \| next ›

Discussion Overview

group	golang-nuts @
categories	go
posted	Dec 20, '15 at 12:04a
active	Dec 22, '15 at 8:51p
posts	5
users	3
website	golang.org

font	variable	Hotkey: f
user style	avatars	Hotkey: a

[go-nuts] cgo: curious why this type conversion works

Search Discussions

Discussion Posts

Related Discussions

3 users in discussion