From: Sverre Rabbelier <srabbelier@gmail.com>
Date: Mon, 05 Sep 2011 13:49:07 GMT
Subject: Re: [PATCH 2/2] Support sizes >=2G in various config options accepting 'g' sizes.
Message-ID: <CAGdFq_gFNHq9Cgv4F4Q6VQ=G7odfUJ5pUFWn=OYE-BfXzP=Enw@mail.gmail.com>
In-Reply-To: <1315223155-4218-2-git-send-email-nix@esperi.org.uk>

Heya,

On Mon, Sep 5, 2011 at 13:45, Nix <nix@esperi.org.uk> wrote:
> 32-bit platforms with no type larger than 'long' cannot detect this
> case and will continue to silently misbehave, but the misbehaviour
> will be somewhat different and more useful, since bigFileThreshold was
> also being mistakenly treated as a signed value when it should have
> been unsigned.

Is it not possible to detect that the target value won't fit in the
max size of an int when parsing the config value?

-- 
Cheers,

Sverre Rabbelier