macOS Objective-C 2.0

[ANTMUZ]

How much different is Obj-C 2.0 compared to Obj-C in its current form? I'm guessing it's not totally different, maybe it just has a few extra additions and improvements?

Should I wait for 2.0 documentation or do you think I'm pretty safe learning Obj-C today?

Cheers

 

[MongoTheGeek]

How much different is Obj-C 2.0 compared to Obj-C in its current form? I'm guessing it's not totally different, maybe it just has a few extra additions and improvements?

Should I wait for 2.0 documentation or do you think I'm pretty safe learning Obj-C today?

Cheers

It adds some things that are nice to have but by no means necessary. It will save you a half dozen lines of code. I would say just learn it.

 

[Objectivist-C]

https://forums.macrumors.com/threads/285137/

 

[Krevnik]

The problem is that a couple features of 2.0 will require Leopard to run. So unless you want to lock yourself into Leopard, you need to learn what is available now first.

It honestly, 2.0 is more of convenience than actual muscle. Using 1.0 on Leopard is not a huge loss, in my opinion.

 

[janey]

It adds some things that are nice to have but by no means necessary. It will save you a half dozen lines of code. I would say just learn it.

garbage collection! yay!

That being said, there isn't much of a huge difference, and you should just start now. There's no dramatic sea change with 2.0.

 

[whooleytoo]

There's no dramatic sea change with 2.0.

..or... C change?

(sorry!)