Path: utzoo!attcan!uunet!tiamat!jim
From: jim@tiamat.fsc.com (Jim O'Connor)
Newsgroups: comp.sources.d
Subject: Re: pax on 16 bit machine, tar filesize field
Summary: pax seems to assume "int > 16 bits"
Message-ID: <401@tiamat.fsc.com>
Date: 1 Mar 89 21:15:36 GMT
References: <228@libove.UUCP>
Organization: Filtration Sciences Corp., Chattanooga, TN
Lines: 22

In article <228@libove.UUCP>, root@libove.UUCP (Jay M. Libove) writes:
> 
> In "pax" on my 16 bit Xenix (80286) machine, it seems that the filesize
> field (in tar listings anyway, haven't tried cpio or pax format) is
> a 16 bit signed integer, because:
> 

pax seems to use "int" in contexts where very large numbers are expected
on a consistent basis.  The routines in buffer.c that set up and manage the
buffers use int or unsigned int for most of their arguments, but I'm probably
not wrong in assuming the author did not intend to restrict buffering on
large machines to <= 64K-1, so "int" was probably assumed to be > 16 bits.

Short of changing several int definitions to long's, I'm not sure what else
could be done.

--jim
------------- 
James B. O'Connor			jim@tiamat.fsc.com
Filtration Sciences Corporation		615/821-4022 x. 651

*** Altos users unite! mail to "info-altos-request@tiamat.fsc.com" ***