Re: #warning
Re: #warning
- Subject: Re: #warning
- From: Art Isbell <email@hidden>
- Date: Mon, 19 Dec 2005 17:31:21 -1000
On Dec 19, 2005, at 2:09 PM, Robert Dell wrote:
i also tried (this weekend) pulling out one procedure and putting
it in a file all by itself and then doing the following:
#include "initWithBundle.m"
Not cool.
If this large class really can't be broken up into smaller classes,
splitting a large class into categories is what NeXT did and Apple does.
it properly showed 4 files but it then complained when compiling
that file saying it doesn't know anything about my globals.
Globals! <cough> These violate encapsulation and can lead to bugs
that are difficult to debug. Instead, you can emulate ObjC class
variables by limiting the scope of these globals to their file and
defining class setter/getter methods. Then these globals must be
accessed via the class object which avoids the need to create an
instance to access them.
Aloha,
Art
_______________________________________________
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