From owner-freebsd-arch@FreeBSD.ORG Sat May 19 18:53:48 2012 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D09110656B9; Sat, 19 May 2012 18:53:48 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 4B1088FC18; Sat, 19 May 2012 18:53:48 +0000 (UTC) Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id q4JIoOkc006929 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Sat, 19 May 2012 12:50:25 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <15087.1337452249@critter.freebsd.dk> Date: Sat, 19 May 2012 12:50:24 -0600 Content-Transfer-Encoding: 7bit Message-Id: References: <15087.1337452249@critter.freebsd.dk> To: "Poul-Henning Kamp" X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Sat, 19 May 2012 12:50:26 -0600 (MDT) Cc: Konstantin Belousov , Robert Millan , freebsd-arch@FreeBSD.org Subject: Re: headers that use "struct bintime" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2012 18:53:48 -0000 On May 19, 2012, at 12:30 PM, Poul-Henning Kamp wrote: > In message <20120520004236.D1313@besplex.bde.org>, Bruce Evans writes: >> On Sat, 19 May 2012, Poul-Henning Kamp wrote: > >>>>> Or maybe "struct bintime" be defined unconditionally? >>> >>> I think this is the best/right way to go. >> >> Not permitted. > >> sys/time.h is still massively polluted in other ways: >> [...] >> Not permitted in POSIX.1, [...] > > I think at this time, we can either religiously stick to POSIX > and become irellevant with it, or we can develop our APIs to > become useful and desirable, and have a chance to survive. Doesn't __BSD_VISIBLE do just that? Warner > Strictly 1980-compatible APIs will not gain FreeBSD 10+ any > new users. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > >