Re: swift and objective-c
Re: swift and objective-c
- Subject: Re: swift and objective-c
- From: Michael Hecht <email@hidden>
- Date: Tue, 03 Jun 2014 14:21:13 +0000
- Thread-topic: swift and objective-c
I think the C thing it mostly gets rid of is pointers. Doing so not only rids us of many memory related programming errors, but potentially enables Fortran-like optimizations that are not possible in C due to pointer aliasing.
It also appears to get rid of many C idioms that lead to bugs, like:
- single-statement if bodies, such as goto fail;
- = where == was meant;
- accidentally falling through a switch case;
- needing/forgetting to litter your code with casts to/from various flavors of int;
Probably more; still reading.
Sent from my iPhone
> On Jun 3, 2014, at 10:10 AM, "Akis Kesoglou" <email@hidden> wrote:
>
>> On 3 Ιουν 2014, at 17:03, Roland King <email@hidden> wrote:
>>
>> ... With some ObjC thrown in there too with the named/typed parameters. ...
>
> And that's exactly the reason I see ObjC being deprecated. From what I've read, Swift *feels* a lot like ObjC -- init/dealloc, designated initialisers, named function arguments, ARC, verbosity, etc.
>
> Akis
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden