All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christoph Egger" <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <keir@xensource.com>, Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH] Add -Wcast-qual flag
Date: Thu, 21 Dec 2006 15:56:11 +0100	[thread overview]
Message-ID: <200612211556.11442.Christoph.Egger@amd.com> (raw)
In-Reply-To: <458AA5C8.76E4.0078.0@novell.com>

On Thursday 21 December 2006 15:18, Jan Beulich wrote:
> >>> Keir Fraser <keir@xensource.com> 21.12.06 14:28 >>>
> >
> >On 21/12/06 12:51, "Jan Beulich" <jbeulich@novell.com> wrote:
> >> While I'd really like to see all Xen code become const-correct (because
> >> I do believe this helps with code quality, like does marking read only
> >> data read only in the page tables), I don't think adding the warning
> >> here is appropriate - after all, in C this is one of the purposes of
> >> adding explicit casts (although I agree it's questionable to use casts
> >> for this purpose). And no, I don't think that many people screwing up
> >> const placement is a proper argument for not using const where possible.
> >
> >Well, I'm inclined to take the clean-up parts of the patches but leave out
> >__UNCONST() and -Wcast-qual. I really dislike the compiler thinking it
> > knows better than an explicit cast, and casting via unsigned long is just
> > a kludge.
>
> This I completely agree with.

Me, too. I mentioned in my first mail, these parts with __UNCONST() must be 
reworked to get rid of it. There was no obvious solution for me at least.
If someone knows a way, I am for it.

      reply	other threads:[~2006-12-21 14:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21 10:05 [PATCH] Add -Wcast-qual flag Christoph Egger
2006-12-21 10:41 ` Keir Fraser
2006-12-21 11:12   ` Christoph Egger
2006-12-21 12:51   ` Jan Beulich
2006-12-21 13:25     ` Christoph Egger
2006-12-21 13:28     ` Keir Fraser
2006-12-21 14:18       ` Jan Beulich
2006-12-21 14:56         ` Christoph Egger [this message]

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=200612211556.11442.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=jbeulich@novell.com \
    --cc=keir@xensource.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.