From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1111a3,5ee869da42505971
X-Google-Attributes: gid1111a3,public
X-Google-Thread: 109fba,b87849933931bc93
X-Google-Attributes: gid109fba,public
X-Google-Thread: fac41,b87849933931bc93
X-Google-Attributes: gidfac41,public
X-Google-Thread: 114809,b87849933931bc93
X-Google-Attributes: gid114809,public
X-Google-Thread: 103376,b87849933931bc93
X-Google-Attributes: gid103376,public
X-Google-Thread: 1108a1,b87849933931bc93
X-Google-Attributes: gid1108a1,public
From: Marc De Scheemaecker <marc@netvision.be>
Subject: Re: Combining dynamic and static typing
Date: 1997/01/29
Message-ID: <32EF2E2A.577C0709@netvision.be>#1/1
X-Deja-AN: 212968452
references: <5celpp$n3r@csugrad.cs.vt.edu>
 <1997Jan28.160420.28915@schbbs.mot.com> <32EEC441.4B7@erols.com>
content-type: text/plain; charset=us-ascii
organization: EUnet Belgium, Leuven, Belgium
mime-version: 1.0
newsgroups: 
 comp.lang.eiffel,comp.lang.ada,comp.lang.c++,comp.lang.smalltalk,comp.lang.objective-c,comp.object
x-mailer: Mozilla 3.01 (X11; I; Linux 2.0.27 i586)
Date: 1997-01-29T00:00:00+00:00
List-Id: <comp.lang.ada>


Luther Hampton wrote:
> 
> You must use a different Objective-C than I do. The Objective-C compiler
> supplied by Next performs type checking to the maximum extent possible
> at compile time. It's only when the compiler encounters the type "id"
> that it gives up type checking.  If you wrote your entire Objective-C

Even if you use the "id" type, you still get a warning if you send a 
message that's nowhere defined.
If you type e.g. [myObject relaese] (typo!) and "relaese" is nowhere
defined, you will get a warning.

> program without referencing the type "id" (admittedly pretty impossible
> in the Next environment), you would get complete compile-time type
> checking.  These errors would be reported as warnings, but reported
> nonetheless.  There is runtime checking to, but it is hardly the only

If you want them to be reported as errors, use the -Werr compile flag.
This works in gcc and I think also in the NeXTstep compiler (which is
based on gcc).

Marc
-- 
                      | Marc De Scheemaecker
                      | Jr. Development Engineer
                      | 
             NetVision nv
        marc@netvision.be
  http://www.netvision.be
                      |
                      | T. 016-31.00.15
                      | F. 016-31.00.29

  Geek Code: http://www.netvision.be/marc/geekcode.html