From owner-freebsd-commit Mon Sep 11 09:27:09 1995 Return-Path: commit-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA25889 for freebsd-commit-outgoing; Mon, 11 Sep 1995 09:27:09 -0700 Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA25875 for cvs-all-outgoing; Mon, 11 Sep 1995 09:27:07 -0700 Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA25855 for cvs-sys-outgoing; Mon, 11 Sep 1995 09:26:37 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA25848 ; Mon, 11 Sep 1995 09:25:21 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id JAA11339; Mon, 11 Sep 1995 09:24:46 -0700 Message-Id: <199509111624.JAA11339@precipice.shockwave.com> To: Bruce Evans cc: CVS-commiters@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/kern vnode_if.sh In-reply-to: Your message of "Mon, 11 Sep 1995 09:05:18 PDT." <199509111605.JAA25403@freefall.freebsd.org> Date: Mon, 11 Sep 1995 09:24:45 -0700 From: Paul Traina Sender: commit-owner@FreeBSD.org Precedence: bulk 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 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.