Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!houxm!whuxl!whuxlm!akgua!gatech!seismo!brl-sem!brl-smoke!smoke!gwyn@BRL.ARPA
From: gwyn@BRL.ARPA
Newsgroups: net.lang.c
Subject: Re:  A simple non-portable expression tha
Message-ID: <234@brl-smoke.ARPA>
Date: Wed, 23-Apr-86 15:22:54 EDT
Article-I.D.: brl-smok.234
Posted: Wed Apr 23 15:22:54 1986
Date-Received: Thu, 1-May-86 02:26:02 EDT
Sender: news@brl-smoke.ARPA
Lines: 7

The reason "lint" doesn't warn about possible overflow on
	INT + INT + LONG
is that ANY addition/subtraction can potentially overflow.
"lint" warns when a (long) is being converted implicitly
to a shorter integral type, because this is often a source
of inadvertent bugs.  But if it were to warn about every
addition, people would stop using "lint".