On Thu, 17 Jul 2008, Denys Vlasenko wrote:
> On Thursday 17 July 2008 01:41, Robert P. J. Day wrote:
> > > > in fact, it's misleading since it implies that the max length can be
> > > > up to almost 32K when Config.in clearly restricts the value to 8K.
> > > >
> > > > rday
> > >
> > > These chec
On Thursday 17 July 2008 01:41, Robert P. J. Day wrote:
> > > in fact, it's misleading since it implies that the max length can be
> > > up to almost 32K when Config.in clearly restricts the value to 8K.
> > >
> > > rday
> >
> > These checks are there simply to make sure something didn't go bad..
On Wed, 16 Jul 2008, Poly-poly man wrote:
> On Wednesday 16 July 2008 07:08:29 pm Robert P. J. Day wrote:
> > some redundant or misleading preprocessor tests under libbb/.
> > first, given this range restriction in Config.in:
> >
> > config MD5_SIZE_VS_SPEED
> > int "MD5: Trade Bytes for
On Wednesday 16 July 2008 07:08:29 pm Robert P. J. Day wrote:
> some redundant or misleading preprocessor tests under libbb/.
> first, given this range restriction in Config.in:
>
> config MD5_SIZE_VS_SPEED
> int "MD5: Trade Bytes for Speed"
> default 2
> range 0 3
>
> dup
some redundant or misleading preprocessor tests under libbb/.
first, given this range restriction in Config.in:
config MD5_SIZE_VS_SPEED
int "MD5: Trade Bytes for Speed"
default 2
range 0 3
duplicating that range test in md5.c is redundant:
#if CONFIG_MD5_SIZE_VS_SPEED
