Re: ObjC error messages
Re: ObjC error messages
- Subject: Re: ObjC error messages
- From: Malte Tancred <email@hidden>
- Date: Tue, 19 Feb 2002 08:42:42 +0100
On monday, february 18, 2002, at 12:48 , Sherm Pendley wrote:
Then why not check the validity of the message to be sent by first
calling respondsToSelector: on the target? If you only send valid
messages, it won't matter how invalid messages are handled.
Just a thought...
Sure, there's plenty of solutions to my specific problem. In this
specific case, if it's in anyones interest to know, the class sending
the unrecognized message is actually supposed to do just that. It's part
of a test suite to make sure the exception is caught.
The reason I brought up the subject though, was of a more generic
nature, not solely to solve the specific problem.
Thanks everyone for your insightful input!
Cheerio,
Malte
--
Malte Tancred
Computer programmer, Oops AB, Sweden
mailto:email@hidden
http://www.oops.se/
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.