From owner-freebsd-current Thu Jan 28 00:26:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07403 for freebsd-current-outgoing; Thu, 28 Jan 1999 00:26:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07396 for ; Thu, 28 Jan 1999 00:26:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id AAA02016; Thu, 28 Jan 1999 00:26:17 -0800 (PST) (envelope-from dillon) Date: Thu, 28 Jan 1999 00:26:17 -0800 (PST) From: Matthew Dillon Message-Id: <199901280826.AAA02016@apollo.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: -Wall -Wcast-qual and SYSINIT References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :>From my uderstanding, SYSINIT should always point to a function with a :CONST argument because the argument is fixed as a constant at link/compile :time. : :what functions don't expect a const? and why not? : :or am I mising something? : :julian Most of the functions do not expect a const argument, though that may simply be because they didn't bother to use const when they could have. However, I know at least the MALLOC initialization objects *can't* use const objects because the malloc initialization routine modifies the data object. I'm sure that a non-trivial number of the sysinits also modify their data objects. So we need to handle both cases. Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message