From owner-freebsd-current  Sat Sep 23 14:16:30 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id OAA01416
          for current-outgoing; Sat, 23 Sep 1995 14:16:30 -0700
Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id OAA01405
          for <freebsd-current@freefall.cdrom.com>; Sat, 23 Sep 1995 14:16:26 -0700
Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4)
	id AA05193; Sat, 23 Sep 1995 17:16:21 -0400
Received: by borg.ess.harris.com (4.1/SMI-4.1)
	id AA07376; Sat, 23 Sep 95 17:13:43 EDT
Date: Sat, 23 Sep 95 17:13:43 EDT
From: jleppek@suw2k.ess.harris.com (James Leppek)
Message-Id: <9509232113.AA07376@borg.ess.harris.com>
To: freebsd-current@freefall.FreeBSD.org
Subject: runtime warnings
Sender: owner-current@FreeBSD.org
Precedence: bulk

I am not sure if this is current or hackers topic but since I
run current...

This may have come up before but what is the purpose of
having runtime warnings for things like gets. Compile time warnings
I can understand, but runtime??? I give someone the latest gnuchess
and everytime they start it, up pops this warning about gets being
unsafe. To most folks that means "don't run this program, it's broken".

If this has been discussed before I guess I had forgotten the reason
and it once again strikes me as a "no win" warning.
If you have the sources and are compiling it, a compile time warning
would be fine, if you just have a binary you are stuck with the warning.

Jim Leppek