All of
 help / color / mirror / Atom feed
From: Srdjan Todorovic <>
Subject: Re: [KJ] memory zeroing macros
Date: Mon, 12 Feb 2007 01:51:20 +0000	[thread overview]
Message-ID: <Pine.LNX.4.63.0702120137330.5352@thor.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0702101731480.6852@CPE00045a9c397f-CM001225dbafb6>

On Sun, 11 Feb 2007, Greg KH wrote:

> On Sun, Feb 11, 2007 at 03:34:34PM -0500, wrote:
> > On Sun, Feb 11, 2007 at 04:32:11AM -0500, Robert P. J. Day wrote:
> > > or maybe this really is just not worth the effort.  who knows?
> > 
> > I don't think its worth the effort.  Changing the name on this wouldn't add
> > any readability.  memset(dest, 0, len) is very clear, in my opinion.  Also,
> > there's nothing really error prone about it...  I see no advantage.
> Not true at all, 0 and len get switched a lot accidentally.  See the
> archives for times people have swept the kernel tree to fix this issue
> up.

I agree with you here, Greg, about accidentally switching the args to
memset(). However just because someone (I've done this in the past,
damn hard to debug since you don't expect to make this silly mistake)
can do:

  if (x = 0)  { }

doesn't mean that we should discourage if statements.

The macros from the wiki page add yet another set of macros/functions
that someone has to learn. memset() should be really well-known to
anyone doing C for a while. Plus with new code, comes the possibility
of abuse and bugs (eg. the macros in the wiki page don't protect the
arguement with brackets).


Kernel-janitors mailing list

  parent reply	other threads:[~2007-02-12  1:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10 22:32 Robert P. J. Day
2007-02-10 23:42 ` Alexey Dobriyan
2007-02-11  8:55 ` Robert P. J. Day
2007-02-11  9:24 ` Alexey Dobriyan
2007-02-11  9:32 ` Robert P. J. Day
2007-02-11 20:34 ` burns.ethan
2007-02-11 21:33 ` Greg KH
2007-02-12  1:51 ` Srdjan Todorovic [this message]
2007-02-12  4:43 ` Greg KH
2007-02-12  5:28 ` Richard Knutsson
2007-02-12  8:59 ` Robert P. J. Day

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.63.0702120137330.5352@thor.lan \ \ \
    --subject='Re: [KJ] memory zeroing macros' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.