Date: Tue, 14 Nov 1995 10:14:22 -0500 From: Paul Fox <pgf@American.COM> To: freebsd-ports@freebsd.org Subject: how do you deal with quad_t? Message-ID: <199511141514.KAA15674@mozart.american.com>
next in thread | raw e-mail | index | archive | help
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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511141514.KAA15674>