I found a workaround. First, I'll answer Greg's questions
On 2008 Mar, 25, at 22:39, Greg Parker wrote:
Don't add +initialize in a category. The category's method will
replace any present in the original class, which could break that
class.
Agreed. As I said, I just wanted to "apply
Jerry Krinock wrote:
Now, please understand that I'm not sure whether or not it's kosher
to add +initialize in a category on a Cocoa class
Don't add +initialize in a category. The category's method will
replace any present in the original class, which could break that
class. However, I don
An off-list respondent suggested that possibly Panther is not
correctly initializing the NSString category in my framework into the
NSString class. I added a +initialize method to my category, and got
a strange result which might give someone a clue...
@implementation NSString (Crash)
+ (
On 2008 Mar, 21, at 17:04, Kyle Sluder wrote:
My guess is that since dyld doesn't support @loader_path on 10.3.9,
your framework isn't loading,
H...but the first NSLog() in the framework executes and logs.
Does that not prove that the framework must be loaded?
and therefore your cat
On Fri, Mar 21, 2008 at 6:16 PM, Jerry Krinock <[EMAIL PROTECTED]> wrote:
> The framework adds a category with a single method onto NSString, as
> shown. Code, Project Settings, links to Build Transcripts and
> projects, Console and Crash Log snippets are all given below.
My guess is that sinc
