> > I am a beginner with GO and cgo, and have never dealt with C corruption > issues. > > First, I would try really hard to find a pure go solution to your problem, or next best, a solution that uses a 3rd party go package that handles the cgo for you. I understand that this may not be possible.
Using cgo is diving right into what is the (arguably) most difficult, confusing, error prone, advanced part of the language. Go is a really great language, and one of its features is its simplicity. I find that beginners in go write better, more reliable, and more readable code with less of a learning curve than most languages. However, this does *not* apply to using cgo. I'm suspect that some people come to go and get put off because they start with cgo, or one of the other "danger areas". I always suggest that those new to go focus on writing idiomatic code in pure go. Completely avoid cgo, the "unsafe" package, and reflection. Which ever way you go, I wish you the best of luck. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/084f07f7-6dad-4b1b-bd87-42b9ec45660f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
