From owner-freebsd-hackers  Mon Sep  2 17:41:44 2002
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6379137B400
	for <hackers@freebsd.org>; Mon,  2 Sep 2002 17:41:42 -0700 (PDT)
Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0E71843E65
	for <hackers@freebsd.org>; Mon,  2 Sep 2002 17:41:38 -0700 (PDT)
	(envelope-from tlambert2@mindspring.com)
Received: from pool0137.cvx40-bradley.dialup.earthlink.net ([216.244.42.137] helo=mindspring.com)
	by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 17m1ku-00045s-00; Mon, 02 Sep 2002 17:41:20 -0700
Message-ID: <3D7404F5.B316FBA4@mindspring.com>
Date: Mon, 02 Sep 2002 17:40:21 -0700
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, hackers@FreeBSD.ORG
Subject: Re: 64 bit API/ABI changes proposal for -current
References: <55509.1030995196@critter.freebsd.dk> <200209021942.g82JgIZn032728@apollo.backplane.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.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-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Matthew Dillon wrote:
>     Ok, we have an issue in regards to libc/user function visibility.
>     The bintime structures and functions are surrounded by __BSD_VISIBLE.
> 
>     The question to you and to the list in general is:  what to call the
>     user-visible structure.  'bintime' is a cute name, I certainly like
>     it better then timeval64, and we could probably get away with calling
>     the user visible structure bintime, but I don't know if we can get
>     away with including all the supporting inline functions (not that we
>     necessarily have to include them for the syscall work, but it would
>     be nice).

What do Linux, Solaris, SCO, etc. call it?  Whatever it is, it
should be the same, so that source code does not need to be
"#if"'ed.

-- Terry

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