From owner-freebsd-ports Tue Nov 14 07:15:05 1995 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA07791 for ports-outgoing; Tue, 14 Nov 1995 07:15:05 -0800 Received: from mozart.american.com (mozart.american.com [204.253.96.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA07778 for ; Tue, 14 Nov 1995 07:15:02 -0800 Received: from localhost (localhost [127.0.0.1]) by mozart.american.com (8.6.12/8.6.9) with SMTP id KAA15674 for ; Tue, 14 Nov 1995 10:14:23 -0500 Message-Id: <199511141514.KAA15674@mozart.american.com> X-Authentication-Warning: mozart.american.com: Host localhost didn't use HELO protocol To: freebsd-ports@freebsd.org Subject: how do you deal with quad_t? Reply-to: pgf@American.COM Date: Tue, 14 Nov 1995 10:14:22 -0500 From: Paul Fox Sender: owner-ports@freebsd.org Precedence: bulk i guess this is less a "ports" question, and more of a "porting" question, but i've been burned by this a couple of times now, and i'm hoping someone here has some ideas... say you're trying to port older non-ansi code to freebsd, and it contains a lot of unsafe assumptions about off_t being sizeof(long). one approach is to attempt to fully prototype the code, but that can quickly become a nightmare of signed/unsigned worries, and default prototion problems. and finding the quad_t vs. long problems with gdb has obvious inefficiencies. are there any "quick" tricks to deal with the long long stuff? i can't be the first person to wish for a panacea, right? :-) --------------------- paul fox american internet corporation pgf@american.com (home: pgf@foxharp.boston.ma.us)