[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Types for the method have to conform?

Subject: Types for the method have to conform?
From: John Calsbeek <email@hidden>
Date: Wed, 10 Aug 2005 20:11:00 -0500
Delivered-to: email@hidden
Delivered-to: email@hidden

Hey,

I've got a method declared as follows:

- (id)initWithData:(NSData *)data options:(NSDictionary *)options error:(NSError **)errorPtr;

I've been running into a certain problem in which gcc seems to think that the actual signature is:

- (id)initWithData:(NSData *)data options:(unsigned int)options error: (NSError **)errorPtr;

because every other method using the selector initWithData:options:error: uses that signature. Will I be perpetually haunted by those warnings when I compile, or will I have to switch to an unsigned int for options? Or should I just change the selector to initWithData:withOptions:error:, as one framework class (don't ask me which) appearently does? Or is there some build option to change this?

-John Calsbeek
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden

This email sent to email@hidden

Follow-Ups:
- Re: Types for the method have to conform?
  - From: Sherm Pendley <email@hidden>

Prev by Date: localized compare and SQLite persistent store
Next by Date: Class clusters and the superclass' initializer implementation
Previous by thread: Re: localized compare and SQLite persistent store
Next by thread: Re: Types for the method have to conform?
Index(es):
- Date
- Thread

Home