🚀 go-pugleaf

In article <3575@richsun.cpg.trs.reuter.com> jack@richsun.cpg.trs.reuter.com  
(Jack Gidding) writes:
> 
> Hmmmm..... this is really strange and very undesired behavior from
> Objective-C.
> When I include the header files from two different classes into a third  
> class, and each of the included classes have a single init: method defined,  
> I get messages similar to the following:
> 
> main2.m:18: warning: multiple declarations for method `init:'
> /Clib/RP.h:32: using `-init:(int )pSize'
> /Clib/RS.h:31: also found `-init:(OBJPTR )s'
> 
> Why is this happening??? Sometimes it tells me that it resolved which init to  
> use, sometimes not, and sometimes it resolves it to the wrong init:.

[...]

> So, why is it telling me that it is using one method or another...shouldn't  
> this be left up until run-time? 
> 

It's happening because the two init: methods are declared with different
argument *types*: one is an int and the other is an OBJPTR. This is a
Bad Thing. If you can statically type the object receiving the init:
message, the compiler can determine which one to use, and make sure
that a bad type conversion doesn't get applied. You don't want a bad
type conversion to get applied, because squishing a signed long int to
an unsigned char (for example) is likely to result in an error....

--
Nik Gervae
Software Publications, NeXT Computer, Inc.
ngervae@next.com
[[[[NXDisclaimer alloc] init] disclaim] free];