Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!whuxl!whuxlm!akgua!gatech!seismo!rlgvax!hadron!jsdy
From: jsdy@hadron.UUCP
Newsgroups: net.lang.c,net.micro,net.micro.pc
Subject: Re: weird C behavior
Message-ID: <347@hadron.UUCP>
Date: Sun, 30-Mar-86 20:41:49 EST
Article-I.D.: hadron.347
Posted: Sun Mar 30 20:41:49 1986
Date-Received: Wed, 2-Apr-86 03:14:21 EST
References: <330@hadron.UUCP> <5190@alice.uUCp>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 19
Xref: watmath net.lang.c:8330 net.micro:14209 net.micro.pc:7622
Summary: "Passed arguments" -> "passed constants"  (ENDIT!)

In article <5190@alice.uUCp> ark@alice.UucP (Andrew Koenig) writes:
>> Passed arguments should always be passed as an "int", I do believe.
>Absolutely not!

Folks, I'm not going to spend the rest of my life apologising for
those two stupid articles I wrote last week.  I hope.  Let's accept
that my brain was tied up with something else and get on with it.

What I  m e a n t  to say above was "Passed integer constants ... ".
As we all know, we can force a constant to be anything at all.  What
caught me was the surprise promotion of a constant to a long, with
no request from the user, if the constant is > the larget integer.
This, though a valid part of the language for years, I think is a
problem.  Then again, writing code that uses that kind of a constant
may be seen to be a problem also.  I have spent some effort in diverse
programs avoiding this.
-- 

	Joe Yao		hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}