Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!mordor!styx!ames!ucbcad!ucbvax!decvax!necntc!necis!smv
From: smv@necis.UUCP
Newsgroups: comp.lang.c
Subject: Re: Time for 64-bit longs?
Message-ID: <462@necis.UUCP>
Date: Fri, 30-Jan-87 14:10:37 EST
Article-I.D.: necis.462
Posted: Fri Jan 30 14:10:37 1987
Date-Received: Sat, 31-Jan-87 20:27:09 EST
References: <848@epimass.UUCP>
Reply-To: smv@necis.UUCP (Steve Valentine)
Distribution: na
Organization: NEC Information Systems, Acton, MA
Lines: 12

As long as you're going to go hacking up the C language definitions, why not
introduce a new keyword "very" as in a "very long" (or even a "very short").
This has the advantage that when compiling code for a machine which has no
very long type, you can simply #define very /**/ and forget it.  With long long
you can't do this as easily.

I know that adding any new keywords will cause other problems, but after all,
this topic involves biting bullets of some sort anyway you look at it.

-- 
Steve Valentine, NEC Information Systems 289 Great Rd., Acton, MA 01720
smv@necis.nec.com