From owner-freebsd-bugs  Wed Sep 25 18:40: 6 2002
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 48BE937B401
	for <freebsd-bugs@hub.freebsd.org>; Wed, 25 Sep 2002 18:40:05 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0055043E6A
	for <freebsd-bugs@hub.freebsd.org>; Wed, 25 Sep 2002 18:40:05 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id g8Q1e4Co004416
	for <freebsd-bugs@freefall.freebsd.org>; Wed, 25 Sep 2002 18:40:04 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.6/8.12.6/Submit) id g8Q1e4Ue004415;
	Wed, 25 Sep 2002 18:40:04 -0700 (PDT)
Date: Wed, 25 Sep 2002 18:40:04 -0700 (PDT)
Message-Id: <200209260140.g8Q1e4Ue004415@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Garrett Wollman <wollman@lcs.mit.edu>
Subject: Re: bin/43372: Broken struct ufs_args in ufsmount.h
Reply-To: Garrett Wollman <wollman@lcs.mit.edu>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR bin/43372; it has been noted by GNATS.

From: Garrett Wollman <wollman@lcs.mit.edu>
To: Alexander Langer <alex@big.endian.de>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: bin/43372: Broken struct ufs_args in ufsmount.h
Date: Wed, 25 Sep 2002 21:34:26 -0400 (EDT)

 <<On Thu, 26 Sep 2002 02:37:58 +0200, Alexander Langer <alex@big.endian.de> said:
 
 > That's not always possible, e.g. we are needing the mount stuff for
 > libh, which is written in C++.
 
 Certainly it is: you can link your C++ program with a module written
 in C that does what you want.
 
 Although this particular interface has very few clients, we shouldn't
 make a precedent that our C API has to change every time C++
 introduces a new incompatibility.
 
 -GAWollman
 

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