Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!bonnie!akgua!mcnc!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!gwyn From: gwyn@brl-tgr.ARPA (Doug Gwyn ) Newsgroups: net.lang.c Subject: Re: lint, pointers, 0 (what else?) Message-ID: <8567@brl-tgr.ARPA> Date: Sun, 24-Feb-85 06:36:13 EST Article-I.D.: brl-tgr.8567 Posted: Sun Feb 24 06:36:13 1985 Date-Received: Wed, 27-Feb-85 08:36:44 EST References: <8412@brl-tgr.ARPA> <282@talcott.UUCP> <766@ucbtopaz.CC.Berkeley.ARPA> Distribution: net Organization: Ballistic Research Lab Lines: 14 > The result of using this system is that you know your programs will get > enough space on strange hardware. If it needs things that are too big, it > won't compile. I think this is backwards. How about writing your code in terms of parameters describing the system (such as those in ), rather than writing code that does not work on systems having perfectly reasonable arithmetic properties that just don't happen to be what you had when you wrote the code. I see the ANSI C committee is attempting to fix the botched floating- point parameters in /usr/group's published set of implementation limits. There are more parameters needed than what they have so far (see the UNIX System V for example).