From: meillo@marmaro.de (markus schnalke)
Subject: [TUHS] Did realloc ever zero the new memory?
Date: Sun, 13 Sep 2015 09:06:48 +0200 [thread overview]
Message-ID: <1Zb1NA-5he-00@marmaro.de> (raw)
In-Reply-To: <20150913011501.GF2103@mcvoy.com>
[2015-09-12 18:15] Larry McVoy <lm at mcvoy.com>
>
> That's a really good point. Anyone like these?
>
> void *alloc(size_t bytes);
> void *realloc(void *old, size_t want);
>
> void *zalloc(size_t bytes);
> void *zealloc(void *old, size_t want);
Please note, that identifiers are usually remembered by sound
not by letter sequence. `zalloc' and `zealloc' are likely to
be pronounced similar and thus there is a good chance that
this leads to confusion and errors. Furthermore, `calloc' and
`zalloc' are prone to be pronounced equally or understood
equally, especially by non-native speakers.
Choosing good identifiers is a tough task.
meillo
next prev parent reply other threads:[~2015-09-13 7:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 0:32 Doug McIlroy
2015-09-13 1:15 ` Larry McVoy
2015-09-13 6:09 ` Dave Horsfall
2015-09-14 3:20 ` Greg 'groggy' Lehey
2015-09-17 4:42 ` Jonathan Gevaryahu
2015-09-13 7:06 ` markus schnalke [this message]
2015-09-13 10:32 ` Dave Horsfall
2015-09-13 11:06 ` markus schnalke
2015-09-13 12:13 ` Derek Fawcus
2015-09-13 13:45 ` John Cowan
2015-09-13 1:30 ` Random832
2015-09-13 2:29 ` Charles Anthony
[not found] <1441931343.25526.for-standards-violators@oclsc.org>
2015-09-12 5:16 ` Dave Horsfall
2015-09-12 6:47 ` Greg 'groggy' Lehey
-- strict thread matches above, loose matches on Subject: below --
2015-09-11 15:41 Norman Wilson
2015-09-11 16:44 ` scj
2015-09-10 19:52 David
2015-09-10 20:10 ` Jim Capp
2015-09-10 20:21 ` Larry McVoy
2015-09-10 20:22 ` David
2015-09-10 20:27 ` Larry McVoy
2015-09-10 20:29 ` David
2015-09-10 20:41 ` Clem Cole
2015-09-11 6:30 ` arnold
2015-09-11 14:36 ` Clem Cole
2015-09-11 0:13 ` Dave Horsfall
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=1Zb1NA-5he-00@marmaro.de \
--to=meillo@marmaro.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).