Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!mips!smsc.sony.com!dce
From: dce@smsc.sony.com (David Elliott)
Newsgroups: comp.sys.mac.programmer
Subject: Re: just to let you know...
Message-ID: <1990Jul5.150741.12535@smsc.sony.com>
Date: 5 Jul 90 15:07:41 GMT
References: <102102@tiger.oxy.edu>
Sender: news@smsc.sony.com (Usenet News System)
Reply-To: dce@smsc.sony.com (David Elliott)
Organization: Sony Microsystems, San Jose, CA
Lines: 25


In article <102102@tiger.oxy.edu>, sonenbli@oxy.edu (Andrew D.
Sonenblick) writes:
|> Boolean    someBoolean,
|> 	   anotherBoolean;
|> 	   monitor[3];

|> Think C (4.00) compiled this with no complaints (don't ask me what it
|> thought monitor[3]; means, I don't know...) so it appears to be a bug.

The 4.3BSD C compiler and the MIPS C compiler (which is pretty close to
ANSI) don't complain about this either.  Technically, the default type
for any variable is the natural integer data type for the machine: int.

This is why you can say things like "register i;" or "unsigned j;"
and it knows that you mean "register int" and "unsigned int" and not
"register short" or "unsigned long".

I personally feel that it should force you to give a type or a
modifier, but it's not a bug for it not to.

David Elliott
dce@smsc.sony.com | ...!{uunet,mips}!sonyusa!dce
(408)944-4073
"If I had a hat the size of Oklahoma, I'd be a happy person."