From owner-freebsd-current  Thu Jan 28 02:40:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA24376
          for freebsd-current-outgoing; Thu, 28 Jan 1999 02:40:48 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24369
          for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 02:40:44 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA03357;
	Thu, 28 Jan 1999 21:40:39 +1100
Date: Thu, 28 Jan 1999 21:40:39 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901281040.VAA03357@godzilla.zeta.org.au>
To: dillon@apollo.backplane.com, julian@whistle.com
Subject: Re: -Wall -Wcast-qual and SYSINIT
Cc: current@FreeBSD.ORG
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?

Probably most.

>or am I mising something?

Only the initial value of the arg is determined at link/compile time.
The arg can point to non-const storage, and it is not unreasonable to
put the initial value in non-const storage so that it can be frobbed.
Linker sets sometimes get frobbed.  I once made execsw_set const and
had to change it back after it started causing warnings.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message