From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mark H Weaver Newsgroups: gmane.lisp.guile.devel Subject: Let's fix how warnings are specified Date: Sat, 11 Feb 2012 22:57:55 -0500 Message-ID: <8739ag66v0.fsf@netris.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1329019169 5962 80.91.229.3 (12 Feb 2012 03:59:29 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 12 Feb 2012 03:59:29 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sun Feb 12 04:59:28 2012 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RwQb2-0001gl-8m for guile-devel@m.gmane.org; Sun, 12 Feb 2012 04:59:28 +0100 Original-Received: from localhost ([::1]:36943 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RwQb1-0000BV-Tp for guile-devel@m.gmane.org; Sat, 11 Feb 2012 22:59:27 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:44792) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RwQay-0000Ah-43 for guile-devel@gnu.org; Sat, 11 Feb 2012 22:59:25 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RwQax-0001lr-5f for guile-devel@gnu.org; Sat, 11 Feb 2012 22:59:24 -0500 Original-Received: from world.peace.net ([96.39.62.75]:55786) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RwQax-0001le-1k for guile-devel@gnu.org; Sat, 11 Feb 2012 22:59:23 -0500 Original-Received: from 209-6-91-212.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([209.6.91.212] helo=yeeloong) by world.peace.net with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1RwQaq-0007UB-Ae; Sat, 11 Feb 2012 22:59:16 -0500 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 96.39.62.75 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:13848 Archived-At: Hello all, At present, compile-time warnings can only be enabled, not disabled, and there is no way to enable all warnings. This means that the set of warnings has to be hard-coded into every build system. This is terrible because it means that every time we add a new warning type, users won't benefit from it unless they update their Makefiles. We need a way for users to ask for a reasonable default set of warnings (which should be almost all of them), possibly with some warnings explicitly enabled or disabled. We should also have a way to enable all warnings. It would also be nice if this could be done in such a way that external build systems can do this without breaking compatibility with Guile 2.0.[0-5]. I'm looking for ideas of how to adjust our 'compile' and 'guild compile' interfaces to accomplish these objectives. Here's a preliminary proposal: * Add new pseudo-warning types 'all' and 'default'. * For each specific warning type 'FOO', we add 'no-FOO'. * These new pseudo-warning types would be honored by both 'compile' and 'guild compile'. What do you think? Mark