On Mon, Sep 05, 2011 at 02:56:10PM +0100, Nix wrote: > > Well, we're parsing longs, not ints. If sizeof(long)>sizeof(int), or we > have long long and sizeof(long long)>sizeof(int), then we can always > detect overflows when saving into the appropriate type: but if we don't > have long long, or if we have neither strto(u)ll() nor strto[ui]max(), > we could only detect overflow by looking at the raw text string and > checking it by hand to see if it would fit. I judged this pointless > extra complexity for a very rare edge case (machines with neither > strot(u)ll() nor strto[ui]max() are generally quite old and people > aren't going to be specifying sizes in gigabytes on such machines > anyway.) Is this also true for Windows and other platforms? And I don't think it's about whether or not people are likely to specify sizes in gigabytes on old machines. People are bound to blindly copy configuration files from one machine to another. In any case, my expectation would be for the configuration options to do what I tell them, or error out if they do not make sense. Clemens -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html