Comments on: Objective-C: What is .m?

By: John C. Bland II

John C. Bland II — Tue, 09 Jun 2009 08:53:12 +0000

No sweat.

By: John C. Bland II

John C. Bland II — Tue, 09 Jun 2009 08:52:58 +0000

I’ve been living in about 4 other languages comfortably. Objective-C had 0 appeal until recently. Heck…I just bought my first Mac in October 09.

By: Jimmy V

Jimmy V — Thu, 04 Jun 2009 18:37:34 +0000

It is 2009 and you are just now writing about objective C? Where have you been for the past several years.

By: FredJouldd

FredJouldd — Thu, 28 May 2009 18:11:18 +0000

Thanks, good article.

By: John C. Bland II

John C. Bland II — Wed, 20 May 2009 05:01:33 +0000

@bbum
Good stuff. Thanks for providing more clarity.

I have a blog post coming up about @synthesize. It is interesting and I want to learn more about it.

By: bbum

bbum — Sat, 16 May 2009 02:59:00 +0000

Or you can think of it terms of object oriented encapsulation.

The .h file contains the public facing interface for your class; all the stuff that you expect folks using your code to see and understand.

The .m file contains all the implementation details of your class; all the stuff that you might change at a whim as long as it doesn’t change the meaning of something in the .h.

.m files can contain more than @implementations, they can contain private interfaces, too. And on the iPhone or 64 bit Mac OS X runtimes, they can implement private instance variables through class extensions and @synthesize.