:Anyway, GCC actually does have an extension that addresses this
:problem. See "Labeled Elements in Initializers" in the info pages.
:Note, this extension should NOT be used, in my opinion.
:
:John
:--
: John Polstra j...@polstra.com
: John D. Polstra & Co., Inc. Seattle, Washington USA
I'm going to clarify the situation by comitting a separation of
SYSINIT to SYSINIT ( for void * stuff ) and C_SYSINIT ( for const void *
stuff ). However, they will use the same structure and thus will
not address the warning at all. This is simply a clarification of
the problem. This is in sys/kernel.h, of course. The auxillary
macros, such as in sys/vnode.h, simply use the 'correct' *SYSINIT
macro.
What we need is a solution for C_SYSINIT that allows the const void *
callback and data case through without warning, but does not allow
the void * callback and data case. Just as the current SYSINIT case
allows the void * callback/data case without warning but complaints
on const void * callback/data.
-Matt
Matthew Dillon
<dil...@backplane.com>
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
