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:25:54 +0000
- Thread-topic: swift and objective-c
As for the why, Apple is probably thinking along the lines of these articles:
http://arstechnica.com/staff/2005/09/1372/
http://arstechnica.com/apple/2010/06/copland-2010-revisited/
Sent from my iPhone
> On Jun 3, 2014, at 10:19 AM, "Roland King" <email@hidden> wrote:
>
> I can't comment yet, I just haven't read far enough and tried it out to see if it replaces enough of ObjC for it to be a replacement. You still need C down there somewhere at the least. I need to find the Swift-interface-C chapter.
>
> And if it does, I *still* don't know why. ObjC is an ok language, it does what it does, you learn it, you use it.
>
>> On 3 Jun, 2014, at 10:08 pm, 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