Date: Mon, 11 Sep 1995 09:24:45 -0700 From: Paul Traina <pst@shockwave.com> To: Bruce Evans <bde@freefall.freebsd.org> Cc: CVS-commiters@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/kern vnode_if.sh Message-ID: <199509111624.JAA11339@precipice.shockwave.com> In-Reply-To: Your message of "Mon, 11 Sep 1995 09:05:18 PDT." <199509111605.JAA25403@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Maybe it's time to ask the general question:
Why do we care about non-ansi compilers?
Almost every compiler out there today can handle ansi definitions.
For people engaging in bootstrap/porting, they can always use ansi2knr.
Let's just settle on one standard. I don't care which, but I wish to
hell we'd just answer the general question first.
Paul
From: Bruce Evans <bde@freefall.freebsd.org>
Subject: cvs commit: src/sys/kern vnode_if.sh
bde 95/09/11 09:05:17
Modified: sys/kern vnode_if.sh
Log:
Generate prototypes for VOP functions. I decided to keep the old-style
definitions even though the functions are inline. If vnode_if.h was
compiled by a non-ANSI compiler, then `inline' would be defined away,
so vnode_if.h might compile correctly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509111624.JAA11339>