News for hackers. Stuff that matters.
Re:OBNC Oberon Compiler by cturner on Sunday September 02, 2018 @09:19AM (#17896901)
Wikipedia describes GC as being automatic memory management. I don't think it is valid to describe the traditional (pre-2007) osx/objective-c model of manual reference counting as a form of garbage collection.

Darwin itself is mostly unix+C. Hence, this does not respond to the parent, asking about GC in the OS itself.

Re:OBNC Oberon Compiler by Volt on Sunday September 02, 2018 @11:08AM (#17897229)
>Darwin itself is mostly unix+C. Hence, this does not respond to the parent, asking about GC in the OS itself.

You're right, but just to clarify WRT your first paragraph, Obj-C did briefly have a GC'd runtime between the eras of manual and automatic ref counting.

Re:OBNC Oberon Compiler by cturner on Monday September 03, 2018 @05:12AM (#17901428)
As you and neighbour inferred, I had not know of this. Thanks.
Re:OBNC Oberon Compiler by pjmlp on Sunday September 02, 2018 @11:36AM (#17897332)
Objective-C 2.0 got a tracing GC, which was later replaced by ARC, because it was a failure.

Although it was possible to link frameworks compiled in mixed modes, it lead most of the time to crashs and the C semantics did not help.

Hence the pragmatic solution of ARC, which basically has the compiler inserting the retain/release calls that used to be done manually.

While not the same, it was a good enough solution.

https://developer.apple.com/documentation/foundation/object_...