From 6216307e25d00bfd5ca18b8dacbb6ac85f2b9d6a Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Tue, 31 May 2011 14:41:24 -0400 Subject: [PATCH] misc/cgo: remove reference to 'destroy' function R=golang-dev, gri CC=golang-dev https://golang.org/cl/4558042 --- misc/cgo/gmp/gmp.go | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/misc/cgo/gmp/gmp.go b/misc/cgo/gmp/gmp.go index f7bbe9c514..7faa71b696 100644 --- a/misc/cgo/gmp/gmp.go +++ b/misc/cgo/gmp/gmp.go @@ -86,9 +86,8 @@ explicitly in Go to pointers to arrays, as they do (implicitly) in C. Garbage collection is the big problem. It is fine for the Go world to have pointers into the C world and to free those pointers when they -are no longer needed. To help, the garbage collector calls an -object's destroy() method prior to collecting it. C pointers can be -wrapped by Go objects with appropriate destroy methods. +are no longer needed. To help, the Go code can define Go objects +holding the C pointers and use runtime.SetFinalizer on those Go objects. It is much more difficult for the C world to have pointers into the Go world, because the Go garbage collector is unaware of the memory -- 2.50.0