linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux prg <linux-c-programming@vger.kernel.org>
Subject: Re: Question about Malloc
Date: Tue, 19 Oct 2004 15:27:38 +0200	[thread overview]
Message-ID: <20041019132738.GR5033@lug-owl.de> (raw)
In-Reply-To: <a3c4234104101905413e127d3e@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]

On Tue, 2004-10-19 09:41:49 -0300, Matías Aguirre <matiasaguirre@gmail.com>
wrote in message <a3c4234104101905413e127d3e@mail.gmail.com>:
> It's not safer to make:
> 
> Recpointer r;
> r=(Recpointer)malloc(Recpointer);

malloc is void, while r isn't. So you don't need the cast here. However,
notice that your malloc call is actually wrong: the argument isn't a
number (or sizeof(something)), but only a type.

General rule of thumb:

	The "output" of malloc should be assigned to a variable whose
	type is a pointer to whatever you give to sizeof(xxx) as the
	malloc argument.

or in short:

	One star more on the left than on the right.

Of course, if you play with types, this doesn't apply any longer...

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-19 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10  5:31 Question about Malloc Edward Parrilla
2004-10-10  6:13 ` Jeff Woods
2004-10-10 11:13 ` Jan-Benedict Glaw
2004-10-19 12:41   ` Matías Aguirre
2004-10-19 13:27     ` Jan-Benedict Glaw [this message]
2004-10-19 13:52       ` Matías Aguirre

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=20041019132738.GR5033@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-c-programming@vger.kernel.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).