From owner-freebsd-current Sun Feb 21 0:46:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6A1011148C for ; Sun, 21 Feb 1999 00:46:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA18860; Sun, 21 Feb 1999 00:46:22 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Feb 1999 00:46:22 -0800 (PST) From: Matthew Dillon Message-Id: <199902210846.AAA18860@apollo.backplane.com> To: John Polstra Cc: hibma@skylink.it, current@FreeBSD.ORG Subject: Re: const char * References: <199902210456.UAA18273@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :don't think there's any way to get rid of the warning without changing :the declarations. : :In my opinion, the use of "-Wcast-qual" is bogus. Often the whole :point of a cast is to remove a qualifier such as const. It's one :thing to warn when that's done implicitly, and quite another thing to :warn when the programmer has clearly expressed his intent through the :use of a cast. : :John :-- : John Polstra jdp@polstra.com There are only a few cases where cast-qual is bogus. 99% of the warnings it generated were quite real. Maybe not bugs, but definitely programming by misadventure. Volatile and const are only going to become more important as we get deeper into the SMP issues. Especially volatile. cast-qual is necessary to keep people from making bozo mistakes. Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message