git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] diff --stat: allow custom diffstat output width.
Date: Thu, 28 Sep 2006 22:58:10 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0609282252430.3952@g5.osdl.org> (raw)
In-Reply-To: <7vr6xvp7jm.fsf@assigned-by-dhcp.cox.net>



On Thu, 28 Sep 2006, Junio C Hamano wrote:
> 
> This is simply too clever; -pedantic does not like assignment of
> arg to end (constness -- and strtoul takes pointer to non-const
> char *, so making the type of end const char * is not an answer
> either).

The _code_ really is right. The problem is "strtoul()" interfaces and a 
C typing oddity.

> And I do not like casting constness away: end = (char *) arg.

You could fix it by doing something like this:

	static inline unsigned long sane_strtoul(const char *n,
						 const char **p,
						 int base)
	{
		char *end;
		unsigned long res;

		res = strtoul(n, &end, base);
		*p = end;
		return res;
	}

because the only reason strtoul() warns now is that C type-rules don't 
allow the (obviously safe - but pointers migth have strange 
representations) conversion of "char **" into "const char **", even though 
"char *" can be converted into "const char *".

At that point, the cast is probably simpler, but the above should be 
strictly correct pedantic ANSI C.

I didn't even try it, though.

			Linus

  reply	other threads:[~2006-09-29  5:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27  2:40 [PATCH 1/3] diff --stat: allow custom diffstat output width Junio C Hamano
2006-09-27  3:11 ` David Rientjes
2006-09-28 20:54 ` Linus Torvalds
2006-09-28 21:27   ` Junio C Hamano
2006-09-28 22:07     ` Linus Torvalds
2006-09-29  1:35       ` Junio C Hamano
2006-09-29  5:26       ` Junio C Hamano
2006-09-29  5:58         ` Linus Torvalds [this message]
2006-09-29  6:11           ` Junio C Hamano
2006-09-29  6:17           ` Linus Torvalds
2006-09-28 22:24   ` Adrian Bunk
2006-09-28 22:26     ` Johannes Schindelin

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=Pine.LNX.4.64.0609282252430.3952@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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;
as well as URLs for NNTP newsgroup(s).