From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: [PATCH v2] shadow: Implement putspent
Date: Wed, 6 Nov 2013 11:36:40 -0500 [thread overview]
Message-ID: <20131106163640.GN24286@brightrain.aerifal.cx> (raw)
In-Reply-To: <1383744054.23727.44.camel@eris.loria.fr>
On Wed, Nov 06, 2013 at 02:20:54PM +0100, Jens Gustedt wrote:
> Hi Rich,
>
> Am Dienstag, den 05.11.2013, 18:31 -0500 schrieb Rich Felker:
> > While it doesn't really matter in this file, in general, macro
> > arguments should be properly parenthesized, as in:
>
> > +#define NUM(n) ((n) == -1 ? 0 : -1), ((n) == -1 ? 0 : (n))
>
> for such a macro that is replacing two function arguments, I'd go for
> a much more descriptive name, something like NUM2ARGS
I agree with you in principle, but I don't think it really matters
here. The file is small enough that you see both the definition and
usage together. A better improvement might be adding a comment that
the macro expands to two arguments to fprintf, a precision and a
value, but we're getting well into bikeshed territory here. :-)
> > +#define STR(s) ((s) ? (s) : "")
>
> in the context of the actual function that would certainly overkill,
> but generally it is not a good idea to mix user strings and string
> literals without consting them. So in a general context I'd go for
> something like
>
> #define STR(S) ((char const*)((S) ? (S) : ""))
>
> or even
>
> #define STR(S) ((S) ? (char const*){ (S) } : "")
>
> to have a better type check for the argument
I disagree with this change. The type of string literals is char *,
not const char *, so it's not a type consistency issue. Even if it
were, the ?: operator handles the type correctly anyway. My view is
that casts are a code smell, and no-op casts are harmful in that they
obfuscate the correctness of types (since the reader has to question
whether the cast is hiding a type mismatch).
Rich
next prev parent reply other threads:[~2013-11-06 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 7:47 [PATCH] " Michael Forney
2013-11-05 19:24 ` Rich Felker
2013-11-05 22:30 ` [PATCH v2] " Michael Forney
2013-11-05 23:31 ` Rich Felker
2013-11-06 13:20 ` Jens Gustedt
2013-11-06 16:36 ` Rich Felker [this message]
2013-11-07 22:35 ` Jens Gustedt
2013-11-08 0:37 ` Szabolcs Nagy
2013-11-24 6:10 ` [PATCH v3] " Michael Forney
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=20131106163640.GN24286@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).