public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] FAT: remove ifdefs to make the code more readable
Date: Thu, 13 Dec 2012 14:12:31 +0100	[thread overview]
Message-ID: <201212131412.32065.marex@denx.de> (raw)
In-Reply-To: <CACQ1gAgwU2suxp8mJ5nW_60i3C+uR8KS=hd=9AtCTqnfozY=vw@mail.gmail.com>

Dear Richard Genoud,

> 2012/12/13 Marek Vasut <marex@denx.de>:
> > Dear Richard Genoud,
> > 
> >> ifdefs in the code are making it harder to read.
> >> The use of simple if(VFAT_ENABLED) makes no more code and is cleaner.
> >> (the code is discarded by the compiler and linker instead of the
> >> preprocessor.)
> >> 
> >> and bonus, now the code compiles even if CONFIG_SUPPORT_VFAT is not
> >> defined.
> >> 
> >> Signed-off-by: Richard Genoud <richard.genoud@gmail.com>
> >> ---
> >> 
> >>  fs/fat/fat.c       |   55
> >> 
> >> +++++++++++++++++++++++++++------------------------ fs/fat/fat_write.c |
> >> 11 ++-------
> >> 
> >>  2 files changed, 32 insertions(+), 34 deletions(-)
> >> 
> >> diff --git a/fs/fat/fat.c b/fs/fat/fat.c
> >> index 393c378..c79e3e3 100644
> >> --- a/fs/fat/fat.c
> >> +++ b/fs/fat/fat.c
> >> @@ -34,6 +34,12 @@
> >> 
> >>  #include <malloc.h>
> >>  #include <linux/compiler.h>
> >> 
> >> +#ifdef CONFIG_SUPPORT_VFAT
> >> +#define VFAT_ENABLED 1
> >> +#else
> >> +#define VFAT_ENABLED 0
> >> +#endif
> > 
> > [...]
> > 
> > Make it static const int maybe ?
> 
> I hesitate to make them static const, I can't figure why it's better
> to use static const variable instead of defines.
> Could you enlighten me ?

Because you get the type-checking. Preprocessor is evil ;-)

Best regards,
Marek Vasut

  reply	other threads:[~2012-12-13 13:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 13:04 [U-Boot] [PATCH] FAT: make FAT compile without VFAT Richard Genoud
2012-12-04 14:24 ` Marek Vasut
2012-12-04 15:32   ` Richard Genoud
2012-12-04 16:16 ` Stefano Babic
2012-12-13 10:47   ` [U-Boot] [PATCH 0/2] clean some FAT code Richard Genoud
2012-12-13 12:45     ` Marek Vasut
2012-12-13 12:57       ` Richard Genoud
2012-12-13 10:47   ` [U-Boot] [PATCH 1/2] FAT: remove ifdefs to make the code more readable Richard Genoud
2012-12-13 12:46     ` Marek Vasut
2012-12-13 13:00       ` Richard Genoud
2012-12-13 13:12         ` Marek Vasut [this message]
2012-12-13 13:16           ` Richard Genoud
2012-12-13 13:19             ` Marek Vasut
2012-12-13 13:30               ` [U-Boot] [PATCHv2] " Richard Genoud
2013-02-04 16:42                 ` [U-Boot] [U-Boot, PATCHv2] " Tom Rini
2012-12-13 13:09     ` [U-Boot] [PATCH 1/2] " Tom Rini
2012-12-13 13:15       ` Richard Genoud
2012-12-13 13:51       ` Marek Vasut
2012-12-13 14:24         ` Richard Genoud
2012-12-13 14:41           ` Tom Rini
2012-12-13 10:47   ` [U-Boot] [PATCH 2/2] FAT: use toupper/tolower instead of recoding them Richard Genoud
2012-12-13 12:47     ` Marek Vasut
2012-12-14  8:56     ` Stefano Babic
2013-02-04 16:41     ` [U-Boot] [U-Boot, " Tom Rini

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=201212131412.32065.marex@denx.de \
    --to=marex@denx.de \
    --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