Path: utzoo!attcan!uunet!nems!ark1!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!usc!apple!apple.com!casseres
From: casseres@apple.com (David Casseres)
Newsgroups: comp.sys.mac.programmer
Subject: Re: just to let you know...
Message-ID: <9008@goofy.Apple.COM>
Date: 6 Jul 90 00:28:38 GMT
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 27
References:<102102@tiger.oxy.edu> <1990Jul5.150741.12535@smsc.sony.com>

In article <1990Jul5.150741.12535@smsc.sony.com> dce@smsc.sony.com (David 
Elliott) writes:
> In article <102102@tiger.oxy.edu>, sonenbli@oxy.edu (Andrew D.
> Sonenblick) writes:
> |> Boolean    someBoolean,
> |>         anotherBoolean;
> |>         monitor[3];

> ...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".

Whether you actually DO mean int or not, it "knows" that you do...

> 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.

Yes.  Isn't C a wonderful "language"?  Even C++ preserves this kind of 
wonderful feature.  I wish I could have a compiler control of some kind 
that would turn off all that defaulting;  it would be like telling the 
compiler "When I want something to be an int, I'll tell you so."

David Casseres
     Exclaimer:  Hey!