From owner-freebsd-hackers Sat Aug 7 11:51:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 3AFC715021 for ; Sat, 7 Aug 1999 11:51:10 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id OAA23441; Sat, 7 Aug 1999 14:49:52 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sat, 7 Aug 1999 14:49:52 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Peter Wemm Cc: Don Lewis , Sheldon Hearn , freebsd-hackers@FreeBSD.org Subject: Re: quad_t and portability In-Reply-To: <19990807093848.19DF31C1F@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 7 Aug 1999, Peter Wemm wrote: > "Brian F. Feldman" wrote: > > On Fri, 6 Aug 1999, Don Lewis wrote: > > > > > On Aug 6, 3:29pm, Sheldon Hearn wrote: > > > } Subject: quad_t and portability > > > } > > > } Hi folks, > > > } > > > } I want to patch wc(1) so that it uses quad_t instead of u_long. This is > > > } necessary if wc(1) is to produce sensible results for files containing > > > } more than 4GB of data. > > > > > > Why not off_t, which should be portable and scale properly with the > > > maximum system file size. Then the only problem is figuring a portable > > > means of printing the result ... > > > > > > > You can always use off_t with "%qd", (int64_t)foo. > > But not on the Alpha... int64_t is a long there, and gcc complains unless > you use %ld. And 'q' on the alpha is what exactly, then? > > Cheers, > -Peter > > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message