Subject: Re: [PATCH/RFC v2 1/1] Use size_t instead of 'unsigned long' for data in memory

From: Torsten Bögershausen <[email-masked]>
Date: Tue, 20 Nov 2018 06:16:49 +0100

On Tue, Nov 20, 2018 at 06:04:54AM +0100, [email-masked] wrote:
> From: Torsten Bögershausen <[email-masked]>
> 
> Currently the length of data which is stored in memory is stored
> in "unsigned long" at many places in the code base.
> This is OK when both "unsigned long" and size_t are 32 bits,
> (and is OK when both are 64 bits).
> On a 64 bit Windows system am "unsigned long" is 32 bit, and
> that may be too short to measure the size of objects in memory,
> a size_t is the natural choice.
> 
> Improve the code base in "small steps", as small as possible.
> The smallest step seems to be much bigger than expected.

Ops, it seems as if I send this message out twice -
please ignore the "PATCH/RFC v2 1/1"
Sorry for the noise.