From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5583 invoked by alias); 18 Jan 2002 16:42:25 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 5520 invoked from network); 18 Jan 2002 16:42:12 -0000 Received: from unknown (HELO cygnus.equallogic.com) (65.170.102.10) by sources.redhat.com with SMTP; 18 Jan 2002 16:42:12 -0000 Received: from deneb.dev.equallogic.com (deneb.dev.equallogic.com [172.16.1.99]) by cygnus.equallogic.com (8.11.6/8.11.6) with ESMTP id g0IGfFJ18342; Fri, 18 Jan 2002 11:41:15 -0500 Received: from PKONING.equallogic.com (localhost.localdomain [127.0.0.1]) by deneb.dev.equallogic.com (8.11.6/8.11.2) with ESMTP id g0IGfEo17025; Fri, 18 Jan 2002 11:41:14 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15432.20522.863000.476056@gargle.gargle.HOWL> Date: Fri, 18 Jan 2002 11:27:00 -0000 From: Paul Koning To: shebs@apple.com Cc: dj@redhat.com, jbuck@synopsys.com, kenner@vlsi1.ultra.nyu.edu, gcc@gcc.gnu.org Subject: Re: Remaining host configuration fragments References: <200201172221.OAA28101@atrus.synopsys.com> <200201172259.g0HMxi403914@greed.delorie.com> <3C479C5E.16268685@apple.com> X-Mailer: VM 6.95 under 21.4 (patch 3) "Academic Rigor" XEmacs Lucid X-SW-Source: 2002-01/txt/msg01301.txt.bz2 Excerpt of message (sent 17 January 2002) by Stan Shebs: > DJ Delorie wrote: > > > > > would be simpler (no need to worry about nesting of comments). > > > > If the idea is to keep users from using the file, why do we need to > > worry about nesting of comments? Just throw a chunk of uncommented > > English text at the top of the file and let it fail. > > Greps and such won't report that a reference is in a doomed file, > and the commenting protects from browsers like S**rc* N*v*g*t*r. I wonder if this is going further than is really necessary. A clean solution for questionable targets is to disallow them in configure, possibly with a --enable-obsolete-targets override as has been suggested. One advantage is that this is a localized change. Given the above, I don't really see the point in causing compile errors when compiling the target components themselves. But if you want that, a very simple way to force errors is just a #error "this file is obsolete" Right? paul