What I meant was that the refs should be treated like any Go object instance, 
and when collected on the Go side it should dec the ref count so the object can 
be freed on the OSX side.

Might be tricky with weak refs, etc.

Is that what happens?

> On May 31, 2019, at 11:33 AM, Greg Pomerantz <gmp.nsw...@wow.st> wrote:
> 
> Also I don't think an API is going to assume or require ARC -- as far as I 
> understand it, ARC is just a compiler shortcut that adds retain and release 
> calls so the programmer doesn't have to, it is not any sort of runtime memory 
> management or garbage collection system. As long as Clang has a -fno-objc-arc 
> flag, there should be no problem turning ARC off.
> 
> On Friday, May 31, 2019 at 11:51:01 AM UTC-4, Robert Engels wrote:
> Isn't a lack of ARC support a critical limitation, as ARC is required going 
> forward, and many of the newer API's assume ARC behind the scenes?
> 
> -----Original Message----- 
> From: Greg Pomerantz 
> Sent: May 30, 2019 8:25 AM 
> To: golang-nuts 
> Subject: [go-nuts] Announcing NSWrap -- a comprehensive Objective-C binding 
> generator for MacOS 
> 
> I have been working on a binding generator that can read MacOS header files 
> and provide bindings for Objective-C interfaces and library functions. NSWrap 
> can also automatically generate classes implementing one or more named 
> protocols or subclassing a specified class.
> 
> The automatically generated Go types implement method inheritance, and 
> overloaded method names are disambiguated. Variadic functions and methods are 
> supported and pointers to pointers are converted into slices. You can create 
> selectors (to assign actions to NSControl objects, for example) and access 
> Objective-C memory management methods (other than Automatic Reference 
> Counting), including AutoreleasePools.
> 
> An example Cocoa application is provided in 24 lines of Go code. A text-mode 
> Bluetooth Low Energy heart rate monitor in pure Go is 127 lines. The official 
> git repository is linked below. This is the first release, so expect plenty 
> of rough edges.
> 
> https://git.wow.st/gmp/nswrap <https://git.wow.st/gmp/nswrap>
> 
> -- 
> 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 golan...@ <>googlegroups.com <http://googlegroups.com/>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/golang-nuts/15be0140-b994-4692-9062-4792be74a8f9%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/golang-nuts/15be0140-b994-4692-9062-4792be74a8f9%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> 
> 
> -- 
> 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 
> <mailto:golang-nuts+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/golang-nuts/5ff1a68f-c379-4ea7-9177-1a4e15f899a9%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/golang-nuts/5ff1a68f-c379-4ea7-9177-1a4e15f899a9%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
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/55E4EC25-2107-4273-B52A-E474680CFE79%40ix.netcom.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to