From owner-freebsd-current  Sat Sep 23 21:30:08 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA18735
          for current-outgoing; Sat, 23 Sep 1995 21:30:08 -0700
Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA18718
          for <freebsd-current@freefall.freebsd.org>; Sat, 23 Sep 1995 21:30:04 -0700
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA07778; Sat, 23 Sep 1995 22:32:12 -0600
Date: Sat, 23 Sep 1995 22:32:12 -0600
From: Nate Williams <nate@rocky.sri.MT.net>
Message-Id: <199509240432.WAA07778@rocky.sri.MT.net>
To: jleppek@suw2k.ess.harris.com (James Leppek)
Cc: freebsd-current@freefall.freebsd.org
Subject: Re: runtime warnings
In-Reply-To: <9509232113.AA07376@borg.ess.harris.com>
References: <9509232113.AA07376@borg.ess.harris.com>
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???

Originally, it was impossible to generate compile time warnings.  So, by
adding run-time warnings and access to the source you get the user of
the program to quickly fix the problem because it is so annoying. ;)

I'm pretty sure we can generate compile time warnings now, and it would
also be easy to generate run-time warnings only once, rather than for
each call of the program.  Unfortunately, I don't remember how to do it
and I don't have time to look right now.  The place to start would be in
the NetBSD version of gets.c, which has a linker directive to generate
compile time warnings.


Nate