Re: unrecognized selector sent to instance

2009-04-15 Thread Jason Stephenson
Bill Bumgarner wrote: On Apr 15, 2009, at 8:12 AM, BJ Homer wrote: Seems to be concrete to me. Nevertheless, calling it on super does throw an exception; you might just try calling [super init] and see what happens. // NSOutputStream is an abstract class representing the base functionality o

Re: unrecognized selector sent to instance

2009-04-15 Thread John C. Randolph
Jason, I just tried dropping your code into a new Foundation Tool project, and it looks like your problem happens when your subclass of NSOutputStream sends [super initToFileAtPath:append:]. Check the subclassing notes on NSOutputStream. It looks like it's a class cluster, and NSOutputS

Re: unrecognized selector sent to instance

2009-04-15 Thread Bill Bumgarner
On Apr 15, 2009, at 8:12 AM, BJ Homer wrote: Seems to be concrete to me. Nevertheless, calling it on super does throw an exception; you might just try calling [super init] and see what happens. // NSOutputStream is an abstract class representing the base functionality of a write stream. /

Re: unrecognized selector sent to instance

2009-04-15 Thread Jason Stephenson
Thanks to Bill and BJ. Don't I feel silly. I have a new implementation of the output stream class that works. (See attachement.) Now, I have five other NSInputStream/NSOutputStream subclasses to modify and test. Y'know, when I first started coding these classes the other day, I heard a lit

Re: unrecognized selector sent to instance

2009-04-15 Thread Jason Stephenson
Thanks, Bill. I did read the documentation, and in the very documents you point out it says: To create a subclass of NSOutputStream you may have to implement initializers for the type of stream data supported and suitably reimplement existing initializers. You must also provide complete imp

Re: unrecognized selector sent to instance

2009-04-15 Thread BJ Homer
On Wed, Apr 15, 2009 at 9:02 AM, Bill Bumgarner wrote: > On Apr 15, 2009, at 7:04 AM, Jason Stephenson wrote: > >> So, the error that I get at runtime makes it appear that my >> SIGIOBzip2OutputStream does not respond to the -[initToFileAtPath:append:] >> selector, but it does. In the debugger, i

Re: unrecognized selector sent to instance

2009-04-15 Thread Bill Bumgarner
On Apr 15, 2009, at 7:04 AM, Jason Stephenson wrote: So, the error that I get at runtime makes it appear that my SIGIOBzip2OutputStream does not respond to the - [initToFileAtPath:append:] selector, but it does. In the debugger, it looks as though SIGIOBzip2OutputStream's super class is the

Re: unrecognized selector sent to instance

2008-09-26 Thread j o a r
On Sep 25, 2008, at 4:01 AM, pan xuan wrote: Hi, I am having a strange problem of my class declaration. I used to declare some methods of a class in a category, "Private". After I have done some refactoring work (basically moving some classes into another framework), it seems those methods