From owner-freebsd-current Tue May 9 16:42:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id C4FC337BA63; Tue, 9 May 2000 16:42:13 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA20940; Tue, 9 May 2000 16:42:13 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005092342.QAA20940@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: obrien@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: One more question (different now) In-reply-to: Your message of "Tue, 09 May 2000 16:38:28 PDT." <20000509163828.A67002@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 May 2000 16:42:13 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, May 09, 2000 at 04:27:10PM -0700, Mike Smith wrote: > > The only answer I've seen for this one is to kick, hard, whoever it was > > that added -Wcast-qual to the kernel options. > > Or we should just delete it from the options. Ugh. I don't actually like that, because it serves a valid purpose. What irritates me mostly is just that there is no way of casting a volatile object into a non-volatile type, so you can't implement any sort of conditional volatility exclusion. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message