Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-sdd!ncr-sd!sagpd1!jharkins
From: jharkins@sagpd1.UUCP (Jim Harkins)
Newsgroups: comp.lang.c
Subject: typecasting constants
Keywords: ack phfft
Message-ID: <563@sagpd1.UUCP>
Date: 20 Dec 89 01:09:19 GMT
Organization: Scientific Atlanta-GPD, San Diego
Lines: 15

Our customer is trying to force a coding standard rule down our throats
that we don't like, but can't give an argument on why we hate it.  The
rule is "All constants will have their types explicitly specified."
This means we'll have

#define FRED ((long) 4)
#define WILMA  ((short) 9)

Outside of the fact that nobody else ever does this, and we've never had
a problem omitting the typecasts, whats a good argument against this?
Note we don't have a problem with things like '0x42L' when we know it
has to be a long.

jim
"Only dead fish go with the flow"