This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [libobjc] fix to nil_method
- From: Nicola Pero <nicola at brainstorm dot co dot uk>
- To: Andreas Jaeger <aj at suse dot de>
- Cc: Stan Shebs <shebs at apple dot com>, Jan Hubicka <jh at suse dot cz>, gcc-patches at gcc dot gnu dot org
- Date: Fri, 30 Aug 2002 14:17:25 +0100 (BST)
- Subject: Re: [libobjc] fix to nil_method
> > So, it looks to me that the fix should consist in implementing the
> > 'nil_method ()' function so that it can be called in place of any function
> > taking an 'id' argument followed by a 'SEL' argument, followed by zero, or
> > one, or any number of arguments (both a fixed number, or a variable number
> > !).
>
> And here is a new quickly written nil_method-1.m testcase which might help
> you with the work.
Sorry for the confusion - sent too quickly - here is a correct testcase
(only messages to nil returning 'id' are supposed to return 'nil',
messages to nil returning something else return undefined values) -
/* Contributed by Nicola Pero - Fri Aug 30 12:55:37 2002 */
#include <objc/objc.h>
#include <objc/Object.h>
/* Test that calling a method of a nil object results in
nothing to happen (but not a crash), and nil to be
returned. */
@interface TestClass : Object
- (void) testVoid;
- (id) testId;
- (void) testVoidWithA: (int)a;
- (id) testIdWithA: (id)a;
- (void) testVoidWithA: (int)a andB: (int)b;
- (id) testIdWithA: (id)g andB: (id)b;
- (void) voidSum: (int)firstNumber, ...;
- (id) sum: (int)firstNumber, ...;
@end
int main (void)
{
TestClass *t = nil;
[t testVoid];
if ([t testId] != nil)
{
abort ();
}
[t testVoidWithA: 234];
if ([t testIdWithA: t] != nil)
{
abort ();
}
[t testVoidWithA: 12004 andB: -123];
if ([t testIdWithA: t andB: nil] != nil)
{
abort ();
}
[t voidSum: 1, -2, 3, -4, 5, -6, 7, -8, 9, -10,
11, -12, 13, -14, 15, -16, 17, -18, 19, -20];
if ([t sum: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10,
11, 12, 13, 14, 15, 16, 17, 18, 19, 20] != nil)
{
abort ();
}
return 0;
}