From: Ben Nizette <ben.nizette@iinet.net.au>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Coding style RFC: convert "for (i=0;i<ARRAY_SIZE(array);i++)" to "array_for_each(index, array)"
Date: Tue, 13 Feb 2007 11:20:48 +1100 [thread overview]
Message-ID: <45D10460.6000903@iinet.net.au> (raw)
In-Reply-To: <1171324070.1528.25.camel@localhost>
Joe Perches wrote:
> Now that most of the sizeof(array)/sizeof(array[0])
> conversions have been done (there are about 800 done
> and about another 130 left), perhaps it could be
> useful to change the code to use a define similar
> to the list_for_each
>
> #define list_for_each(pos, head) \
> for (pos = (head)->next; prefetch(pos->next), pos != (head); \
> pos = pos->next)
>
> perhaps
>
> #define array_for_each(index, array) \
> for ((index) = 0; (index) < ARRAY_SIZE((array)); (index)++)
>
I like the idea, my only concern would be potential confusion. That is,
the list_for_each macro sets pos to each list_head in turn where
array_for_each just sets the index /in to/ the array. While I think the
way you have is nicer, for compatibility between the two styles maybe
something more like
#define array_for_each(element, array) \
for (int __idx = 0; __idx < ARRAY_SIZE((array)); \
__idx++, (element) = &(array[__idx]))
would help. Of course the other option is to name array_for_each
something different to avoid comparisons with list_for_each.
--Ben.
next prev parent reply other threads:[~2007-02-13 0:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 23:47 Joe Perches
2007-02-13 0:20 ` Ben Nizette [this message]
2007-02-13 0:47 ` Joe Perches
2007-02-13 4:19 ` Nick Piggin
2007-02-13 7:34 ` Joe Perches
2007-02-13 7:42 ` Nick Piggin
2007-02-13 10:36 ` Bernd Petrovitsch
2007-02-13 10:54 ` Nick Piggin
2007-02-13 11:07 ` Bernd Petrovitsch
2007-02-13 7:37 ` Muli Ben-Yehuda
2007-02-13 16:28 ` Randy Dunlap
2007-02-13 7:48 ` YOSHIFUJI Hideaki / 吉藤英明
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=45D10460.6000903@iinet.net.au \
--to=ben.nizette@iinet.net.au \
--cc=joe@perches.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®