From: Pink Boy <dasfoo@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] use of C99
Date: Wed, 8 Apr 2009 18:53:17 -0700 (PDT) [thread overview]
Message-ID: <139940.41801.qm@web31807.mail.mud.yahoo.com> (raw)
Premi, Sanjeev sez,
> I was referring to declaring variable within #ifdefs with
> belief that
> use will be contained.
>
> e.g.
> #ifdef CONFIG_COOL_FEATURE
> int i;
> int* ptr ;
> ...
> ...
> #endif
>
> ...
> ... 2 screenful down; in same function...
> ...
>
> #ifdef CONFIG_HOT_FEATURE
> u32 i;
> void* ptr;
> ...
> ...
> #endif
>
> Maybe for sometime the usage seems contained. Until someone
> decides to have both the COOL and HOT feature.
Pops out of hole, looks at shadow, 6 more weeks till we ship...
Um... my feeling is that if one is going to declare a variable
inside a #ifdef then that variable ought to be called something
like
int indx_CONFIG_COOL_FEATURE
and
u32 indx_CONFIG_HOT_FEATURE
Matt Harper
Tehama Wireless
next reply other threads:[~2009-04-09 1:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 1:53 Pink Boy [this message]
2009-04-09 2:12 ` [U-Boot] use of C99 Jerry Van Baren
2009-04-09 5:50 ` Wolfgang Denk
2009-04-09 13:27 ` Larry Johnson
-- strict thread matches above, loose matches on Subject: below --
2009-04-08 18:51 Kumar Gala
2009-04-08 19:28 ` Wolfgang Denk
2009-04-08 19:46 ` Jerry Van Baren
2009-04-08 20:25 ` Timur Tabi
2009-04-08 20:46 ` Premi, Sanjeev
2009-04-08 20:57 ` Timur Tabi
2009-04-08 21:26 ` Premi, Sanjeev
2009-04-08 21:34 ` Timur Tabi
2009-04-08 21:03 ` Ben Warren
2009-04-08 21:23 ` Premi, Sanjeev
2009-04-08 20:52 ` Scott Wood
2009-04-08 21:01 ` Timur Tabi
2009-04-08 22:26 ` Scott Wood
2009-04-08 21:34 ` Wolfgang Denk
2009-04-08 21:38 ` Timur Tabi
2009-04-08 22:39 ` Graeme Russ
2009-04-08 22:45 ` Timur Tabi
2009-04-08 22:59 ` Wolfgang Denk
2009-04-08 23:09 ` Scott Wood
2009-04-08 22:28 ` Scott Wood
2009-04-08 21:27 ` Wolfgang Denk
2009-04-08 23:22 ` Larry Johnson
2009-04-08 23:40 ` Scott Wood
2009-04-09 4:27 ` Kumar Gala
2009-04-09 11:38 ` Jerry Van Baren
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=139940.41801.qm@web31807.mail.mud.yahoo.com \
--to=dasfoo@yahoo.com \
--cc=u-boot@lists.denx.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