Thanks, I'll check these out as well! .m
On Sat, Mar 20, 2010 at 7:43 AM, Greg Ligierko <[email protected]> wrote: > I am learning ObjC for about a month. The purpose is porting and > existing AS2 application to iphone/ipad. Having very poor C experence > I can say, that knowing C is not something essential to familiarize > and then working fore real with apple frameworks. > > Before I started XCode for good, I bought some books: > > 1) "Programming in Objective-C 2.0 (2nd Edition)" by Stephen G. Kochan. > It's about complete basics of ObjC, this one explains details of the > ObjC syntax, classes, interfaces, implementation, protocols, special > characters, memory management... in general - roots. > > In Kochan's book, there is an interesting paragraph related directly to > your question about C (chapter "Underlaying C Language Features"): > "This chapter describes features of the ObjC language that you don't > necessarily need to know to write ObjC programs. In fact, most of > these come from the underlaying C programming language. (...) some of > these features go against the grain of object oriented programming. > They can also interfere with some of strategies implemented by > Foundation framework such as memory allocation methodology or work > with character strings containing multibyte (UTF8) characters." > > > 2) "Cocoa Design Patterns" Erik M. Buck > This one is great. It is like GOF translated to Apple frameworks. But > it is not as general as GOF. It is really based on the Cocoa language > features. > > Kochan's book is like looking at ObjC through a microscope and Buck's > book is more like looking from a mountain into the cocoa valley :) > > 3,4) Two others by Dave Mark, dedicated to pure iPhone development. > They provide good intro to Interface Builder and iPhone features - > accelerometer, giro, multitouch, but most important - outlets and > delegates: > "Beginning iPhone 3 Development: Exploring the iPhone SDK" > "More iPhone 3 Development: Tackling iPhone SDK 3 (Beginning)" > > g. > > > > Tuesday, March 16, 2010 (9:36:01 PM): > >> I think of the .h files as interfaces - it makes sense after that > >> Sent from my iPhone > >> On 16 Mar 2010, at 18:59, "Eric E. Dolecki" <[email protected]> wrote: > >>> I have heard that one should know C before diving into Obj-C. I did >>> not do >>> that as I wanted to dive in quicker. Once you get your head around >>> memory >>> management and how to manipulate NSString, etc. you'll be well on >>> your way. >>> The whole .h .m thing is strange, etc. I'm not sure if it would have >>> made a >>> big difference for me to learn C first or not, but I chose not to >>> and spent >>> a lot of time reading tutorials and books about Obj-C. I suppose it >>> all >>> depends on what kind of sponge you are. >>> >>> Eric >>> >>> On Tue, Mar 16, 2010 at 2:30 PM, .matt <[email protected]> wrote: >>> >>>> So is it a fools errand to try to dive into iPhone dev without >>>> knowing C >>>> going in? Can one bypass C and dive directly into O-C? >>>> >>>> .m >>>> > > > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

