Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Mar 2005 20:48:53 +0100
From:      Stefan Farfeleder <stefan@fafoe.narf.at>
To:        src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org
Cc:        John Baldwin <jhb@FreeBSD.org>
Subject:   Re: cvs commit: src/sys/compat/linux linux_ioctl.c
Message-ID:  <20050324194852.GJ46915@wombat.fafoe.narf.at>
In-Reply-To: <20050324192502.GB7294@odin.ac.hmc.edu>
References:  <200503241751.j2OHpFQg063306@repoman.freebsd.org> <200503241333.53622.jhb@FreeBSD.org> <20050324192502.GB7294@odin.ac.hmc.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 24, 2005 at 11:25:02AM -0800, Brooks Davis wrote:
> On Thu, Mar 24, 2005 at 01:33:53PM -0500, John Baldwin wrote:
> > On Thursday 24 March 2005 12:51 pm, Brooks Davis wrote:
> > > brooks      2005-03-24 17:51:15 UTC
> > >
> > >   FreeBSD src repository
> > >
> > >   Modified files:
> > >     sys/compat/linux     linux_ioctl.c
> > >   Log:
> > >   Compile errors are way more useful then panics later.
> > >
> > >   Replace a KASSERT of LINUX_IFNAMSIZ == IFNAMSIZ with a preprocessor
> > >   check and #error message.  This will prevent nasty suprises if users
> > >   change IFNAMSIZ without updating the linux code appropriatly.
> > 
> > There's a CTASSERT() macro that you can use for compile time assertions.
> 
> Ah, intresting.  It produces a less informative error, but I guess the
> fact that it should work on any C compiler makes up for it.  I'll switch
> to that.

Do you imply there's a C compiler which can't handle #if and #error?

Stefan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050324194852.GJ46915>