From: "A. Sinan Unur" <asu1 AT cornell DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: ifstream (FILENAME, ios::binary). Can't Read!!!
Date: Wed, 30 Jul 1997 20:19:38 -0400
Organization: Cornell University http://www.cornell.edu
Lines: 31
Sender: asu1 AT cornell DOT edu (Verified)
Message-ID: <33DFDA1A.64AE@cornell.edu>
References: <199707291559 DOT IAA05190 AT adit DOT ap DOT net>
Reply-To: asu1 AT cornell DOT edu
NNTP-Posting-Host: cu-dialup-0087.cit.cornell.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

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
 
*******************************************************************
 A. Sinan Unur                                WWWWWW
                                              |--O+O
 mailto:sinan DOT unur AT cornell DOT edu                C   ^ 
 http://www.people.cornell.edu/pages/asu1/     \  ~/ 

Unsolicited e-mail is _not_ welcome, and will be billed for.
*******************************************************************