Date: Fri, 01 Aug 1997 18:49:34 -0400 (EDT)
From: stunajoh AT ACS DOT EKU DOT EDU
Subject: Re: ifstream (FILENAME, ios::binary). Can't Read!!!
In-reply-to: <33DFDA1A.64AE@cornell.edu>
To: "A. Sinan Unur" <asu1 AT cornell DOT edu>
Cc: djgpp AT delorie DOT com
Message-id: <Pine.PMDF.3.95.970801184410.703847C-100000@ACS.EKU.EDU>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

 

On Wed, 30 Jul 1997, A. Sinan Unur wrote:

> Nate Eldredge wrote:
> > 
> > John M. Aldrich wrote:
> > >Art S. Kagel wrote:
> > >>
> > >> > BTW, I just wrote a little program to print out the maximum value of a
> > >> > 64 bit integer:
> > >> >
> > >> > 18446744073709551615
> > >> Unsigned.  Signed that would be:
> > >> 9223372036854775807
> > >
> > >Showoff.  :)  But how can you read a negative number of bytes from a
> > >file?  That was the implicit assumption in what I said.
> > ALL THIS IS MOOT. You can't even have a file larger than 2^32. DOS 
> > (and I think Unix also) defines the file pointer as being 32 bits. So 
> > there is no possibility to have more than a 4GB file.
> 
> there are 64 bit unices. a year or so ago, there was an article in Unix
> Review (i think) discussing migration issues (32 -> 64 bit)
> -- 
>    Sinan
>  
There is a 64 bit unix.  HP makes a version of HP-UX that is 64 bit,
and we have a DEC alpha at work that runs 64 bit. I've even heard rumors
of a 64 and 128 bit Win NT out there somewhere, but it sounds a little far 
fetched to me.  I have no idea what platform it runs on.