From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14820 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: loff_t definition in (vs. glibc in ) Date: Wed, 16 Oct 2019 17:53:15 -0400 Message-ID: <20191016215315.GU16318@brightrain.aerifal.cx> References: <20191016212835.GA17420@dell5510> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="179908"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-14836-gllmg-musl=m.gmane.org@lists.openwall.com Wed Oct 16 23:53:38 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1iKrEa-000kYM-6i for gllmg-musl@m.gmane.org; Wed, 16 Oct 2019 23:53:32 +0200 Original-Received: (qmail 11339 invoked by uid 550); 16 Oct 2019 21:53:28 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 11318 invoked from network); 16 Oct 2019 21:53:28 -0000 Content-Disposition: inline In-Reply-To: <20191016212835.GA17420@dell5510> Xref: news.gmane.org gmane.linux.lib.musl.general:14820 Archived-At: On Wed, Oct 16, 2019 at 11:28:38PM +0200, Petr Vorel wrote: > Hi Rich, > > what is the reason for loff_t being defined in ? > It was defined some time ago, in v0.9.5. > > glibc (and thus uclibc; + also Bionic) has it in , defined long > time before. Who is correct? I guess loff_t not being posix, therefore it > shouldn't be in ? > > I'm asking because it'd be nice to have it for both in single header > (portability). The reason it's defined in fcntl.h is because that's where the declarations for the only functions which use it in their interfaces reside. If it needs to be made available from multiple places, that could be done at some point, but this is a really minor type that shouldn't be used except with with functions defined in terms of it. Rich