From: "Torsten Bögershausen" <tboegi@web•de>
To: git@vger•kernel.org
Subject: Re: [PATCH/RFC v2 1/1] Use size_t instead of 'unsigned long' for data in memory
Date: Tue, 20 Nov 2018 06:16:49 +0100 [thread overview]
Message-ID: <20181120051649.GA16814@tor.lan> (raw)
In-Reply-To: <20181120050454.16673-1-tboegi@web.de>
On Tue, Nov 20, 2018 at 06:04:54AM +0100, tboegi@web•de wrote:
> From: Torsten Bögershausen <tboegi@web•de>
>
> 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.
prev parent reply other threads:[~2018-11-20 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 5:04 [PATCH/RFC v2 1/1] Use size_t instead of 'unsigned long' for data in memory tboegi
2018-11-20 5:16 ` Torsten Bögershausen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181120051649.GA16814@tor.lan \
--to=tboegi@web$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox