Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!wuarchive!decwrl!nsc!pyramid!athertn!joshua
From: joshua@athertn.Atherton.COM (Flame Bait)
Newsgroups: comp.lang.c
Subject: Re: typecasting constants
Keywords: ack phfft
Message-ID: <15614@joshua.athertn.Atherton.COM>
Date: 21 Dec 89 01:29:30 GMT
References: <563@sagpd1.UUCP>
Reply-To: joshua@Atherton.COM (Flame Bait)
Organization: Atherton Technology, Sunnyvale, CA
Lines: 21

In article <563@sagpd1.UUCP> jharkins@sagpd1.UUCP (Jim Harkins) writes:
>Our customer is trying to force a coding standard rule down our throats...
>This means we'll have
>
>#define FRED ((long) 4)
>#define WILMA  ((short) 9)
>
>whats a good argument against this?

If you have something like this:
#define NAME_SIZE (long)300
and then this code:
char name[NAME_SIZE] ;

Then some (all?) VMS C compilers will become very angry.  I do not think
they will compile the code, but I know they will complain.   

Why does your customer want you to do this?  

Joshua Levy                          joshua@atherton.com  home:(415)968-3718
                        {decwrl|sun|hpda}!athertn!joshua  work:(408)734-9822