At this point it seems as if you're just blathering. -learning- a
language means you know the standard libraries with it. Most people
don't need the standard c libraries because they have the objc
foundation framework. But again, if you're willing to believe that by
programming in objc (which is vastly different although built on c), be
my guest. You'll come closer to knowing c after using c++ than you would
if you just used objc, since there are much more similarities.
Sure ARC is a compiler feature that people don't need, but it is still
frequently used. C doesn't have: ARC, interfaces/protocols, messages,
anonymous functions, different preprocessor commands (#import vs
#include for objc), syntactic sugar (foreach loop, for example), etc. If
it follows that by learning objc one knows c, then by learning c one
should be a lot closer to objc. I've used c and c++ for years now and
stilll have to learn a lot when it comes to objc. The same could be said
for any c programmer: you're going to go in and have to learn what c
doesn't have and what exactly it does differently. mainly, you're going
to be working at a much lower level than you were with objc, which many
people have problems with.
Apple might be moving away from objc, but they can't ever fully phase it
out entirely until Swift is to the point where they can rewrite
everything. That's got a long ways to go yet.
On 7/6/2014 12:23 AM, Sabahattin Gucukoglu wrote:
But again, those are simply features of Objective-C. If you simply don't use
Objective-C features and therefore Objective-C syntax, your program is valid C
source. So if you learn the entire grammar of Objective-C, you also know the
entire grammar of C, no matter how incidental it is to your use of Objective-C.
This simply can't be said for C++ or Java (the latter, BTW, much closer to
Smalltalk in OO semantics, and also to Objective-C).
Now if you were to say that "Learning Objective-C does not result in a
well-disciplined C programmer capable of withstanding the rigours of procedural
programming", I'd definitely be inclined to agree with you. But if people are going
to learn to write iOS and Mac apps, it seems to me that Objective-C is a much better
place to be if you intend writing other C programs in future, because you'll be able to
use your knowledge to understand both C and many other languages. Swift simply breaks
from C in order to emphasise Apple's frameworks, which makes me sad.
Anyway, I think I've gone way off-course for this list, so I'll stop now. But
feel free to write me privately if you'd like to continue. :)
Cheers,
Sabahattin
--
Take care,
Ty
http://tds-solutions.net
He that will not reason is a bigot; he that cannot reason is a fool; he that
dares not reason is a slave.
--
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.
