From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org, Matt Rice <ratmice@gmail.com>
Subject: Re: [doc patch] coding style: 0 vs. NULL + [patch] Code cleanup: skip.c
Date: Tue, 11 Dec 2012 12:01:00 -0000 [thread overview]
Message-ID: <20121211120057.GO31477@adacore.com> (raw)
In-Reply-To: <50C7093F.5000600@redhat.com>
> > I find '(first)' OK myself but IIRC Pedro recently in some mail
> > wrote he likes more an explicit NULL comparison there. Although I
> > cannot find his mail now so I hope I do not put these words in
> > Pedro's mouth.
>
> Yes, indeed I mentioned it recently somewhere. Personally, I find
> implicit boolean conversions make the code harder to grok, so I prefer the
> latter.
Same here. I tend to prefer explicit checks. From a purely
accademic, sadistic, theoretical perspective, NULL isn't
required to be zero, is it? The C99 draft I have says...
expands to an implementation-defined null pointer constant
... and I know some architectures did use nonzero null pointers.
> That's about the same level of badness as '!strcmp(a, b)' to me.
Argh, yes, I hate those :-).
--
Joel
next prev parent reply other threads:[~2012-12-11 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 18:42 Jan Kratochvil
2012-12-11 1:54 ` Joel Brobecker
2012-12-11 6:07 ` Jan Kratochvil
2012-12-11 6:51 ` Jan Kratochvil
2012-12-11 10:22 ` Pedro Alves
2012-12-11 12:01 ` Joel Brobecker [this message]
2012-12-11 20:22 ` [doc patchv2] " Jan Kratochvil
2012-12-11 20:39 ` Eli Zaretskii
2012-12-11 20:43 ` Jan Kratochvil
2012-12-12 4:29 ` Joel Brobecker
2012-12-16 19:00 ` [commit] " Jan Kratochvil
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=20121211120057.GO31477@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=ratmice@gmail.com \
/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