Bug? xemacs and large files

[Kyle Jones]

Darryl Okahata writes:
 > Steve Youngs <steve at youngs.au.com> wrote:
 > 
 > > That's cool.  If I was going to open up a >1GB monster file, I'd
 > > expect to have to wait a week for it to load anyway.
 > 
 >      Wouldn't a 64-bit XEmacs be a better solution (does 64-bit XEmacs
 > still work)?  The world is moving that way, anyway.  Why do we need to
 > further mangle XEmacs to handle
 > an-important-but-nonetheless-little-requested feature, when we can get
 > it for free just by going to 64-bits?  (Unless someone really, really,
 > REALLY wants to do that, of course? ;-)

I think a buffer implementation that sanely handles large file
would be a good project.  By sane, I mean don't ever drag the
whole file into memory.  Keep a data structure that maps the
changed parts to the file and when you save the file, use the map
to build the new version of the file.