Re: Making --with-wide-int the default

[Random832 <random832@fastmail.com>]

Paul Eggert <eggert@cs.ucla.edu> writes:
> Really, integer overflow is not a significant problem with
> --with-wide-int.  As Eli says, if it were a problem it'd also be a
> problem with 64-bit platforms, which it's not.

I think the issue some people are bringing up is that the concrete cases
that would actually trigger the bugs, if there are any (very large
files, very large strings, very large buffers) are rare even on 64-bit
machines. Sure, it's nice to be _able_ to edit 2GB files, but how many
of those does the average user have lying around?