From: Pete Turnbull <pete@dunnington.plus.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] C++ / Kernel
Date: Fri, 24 Aug 2018 11:41:36 +0100 [thread overview]
Message-ID: <0b4dd231-93f5-dbf2-fe5c-42b4a3fb464d@dunnington.plus.com> (raw)
In-Reply-To: <4130AFB4-1740-46BC-AA98-F9D01549049C@bitblocks.com>
On 24/08/2018 02:41, Bakul Shah wrote:
>From what I recall {c,m,re}alloc() returned a char*, not a void *. > I don't have K&R1 handy at the moment so can't recall if void* was
> mentioned in the book (if not, that could be one reason for a lack of
> its use).
Yes, K&R1 specifically states that alloc(n) returns a char* (page 97),
calloc(n, sizeof(obj)) returns a pointer to whatever type you specify
(page 157), and void isn't mentioned anywhere in the book that I can see.
--
Pete
Pete Turnbull
next prev parent reply other threads:[~2018-08-24 10:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 14:42 ron
2018-08-23 17:24 ` Clem Cole
2018-08-23 20:21 ` Bakul Shah
2018-08-23 22:17 ` ron
2018-08-23 22:28 ` Nevin Liber
2018-08-23 22:48 ` Clem Cole
2018-08-23 23:14 ` Steffen Nurpmeso
2018-08-24 14:13 ` Steffen Nurpmeso
2018-08-24 14:32 ` ron
2018-08-24 18:15 ` Steffen Nurpmeso
2018-08-26 16:34 ` Paul Winalski
2018-08-27 16:31 ` Steffen Nurpmeso
2018-08-24 1:41 ` Bakul Shah
2018-08-24 10:41 ` Pete Turnbull [this message]
2018-08-24 12:17 ` ron
2018-08-24 18:36 ` Bakul Shah
2018-08-24 18:38 ` ron
2018-08-24 1:58 ` Dan Cross
2018-08-24 3:04 ` Clem cole
2018-08-24 14:01 ` Dan Cross
2018-08-24 13:22 ` Derek Fawcus
2018-08-24 16:59 ` Steffen Nurpmeso
2018-08-23 23:29 Noel Chiappa
2018-08-23 23:42 ` ron
2018-08-24 0:30 ` Clem Cole
2018-08-24 2:05 ` Bakul Shah
2018-08-24 12:21 ` ron
2018-08-24 1:27 Noel Chiappa
2018-08-24 2:52 ` Clem cole
2018-08-24 7:30 Paul Ruizendaal
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=0b4dd231-93f5-dbf2-fe5c-42b4a3fb464d@dunnington.plus.com \
--to=pete@dunnington.plus.com \
--cc=tuhs@minnie.tuhs.org \
/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).