Comments on: Cocoa Tutorial: Creating your very own framework http://www.cimgf.com/2008/09/04/cocoa-tutorial-creating-your-very-own-framework/ Taglines are for Windows programmers Mon, 26 Jul 2010 16:50:30 +0000 hourly 1 http://wordpress.org/?v=3.0 By: stompy http://www.cimgf.com/2008/09/04/cocoa-tutorial-creating-your-very-own-framework/comment-page-1/#comment-800 stompy Thu, 04 Sep 2008 21:00:27 +0000 http://www.cimgf.com/?p=229#comment-800 <p>For a hands on tutorial: Uli Kusterer has a video available from the Mac Developer Network:</p> <p>http://www.mac-developer-network.com/videocourses/frameworks/index.html</p> For a hands on tutorial: Uli Kusterer has a video available from the Mac Developer Network:

http://www.mac-developer-network.com/videocourses/frameworks/index.html

]]> By: benzado http://www.cimgf.com/2008/09/04/cocoa-tutorial-creating-your-very-own-framework/comment-page-1/#comment-799 benzado Thu, 04 Sep 2008 19:57:34 +0000 http://www.cimgf.com/?p=229#comment-799 <p>You don't have to throw away type checking just because you don't want to expose a class. You can use the @class directive to declare the existence of an Objective-C class without exposing the whole interface. For example:</p> <p>@class InternalObject;</p> <p>@interface AbstractExample : NSObject { InternalObject *object; }</p> <p>If you do this, you don't have to expose the "InternalObject.h" file. Granted, somebody reading your header files will know of the existence of InternalObject, but giving up type checking to keep the class name a secret is kind of petty.</p> <p>I use @class in all of my header files; the only time a header needs to include the header of another class is when it is a subclass of that other class.</p> <p>(P.S. Logging in with openid doesn't seem to work.)</p> You don’t have to throw away type checking just because you don’t want to expose a class. You can use the @class directive to declare the existence of an Objective-C class without exposing the whole interface. For example:

@class InternalObject;

@interface AbstractExample : NSObject { InternalObject *object; }

If you do this, you don’t have to expose the “InternalObject.h” file. Granted, somebody reading your header files will know of the existence of InternalObject, but giving up type checking to keep the class name a secret is kind of petty.

I use @class in all of my header files; the only time a header needs to include the header of another class is when it is a subclass of that other class.

(P.S. Logging in with openid doesn’t seem to work.)

]]>