From: Linus Torvalds <torvalds@osdl.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCHSET] fouled-bitwise handling
Date: Sun, 1 Oct 2006 10:33:44 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610011031280.3952@g5.osdl.org> (raw)
In-Reply-To: <20061001172253.GX29920@ftp.linux.org.uk>
On Sun, 1 Oct 2006, Al Viro wrote:
>
> Hrm... The gut feeling: we mangle expression trees too much to be able
> to do that decently.
Having looked at it a bit now, I think I agree.
We warn about the whole "~" thing too early, so we'd have to remove that
warning anyway (easy enough to do), but then we'd have to track the ops
that don't like using a "~" because of its C semantics.
And at that point, your "fouled" bit is actually probably simpler.
Let me think about this a bit more, but I'm starting to think that you're
right.
As usual.
Linus
prev parent reply other threads:[~2006-10-01 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 13:57 [PATCHSET] fouled-bitwise handling Al Viro
2006-10-01 14:09 ` Al Viro
2006-10-01 16:21 ` Linus Torvalds
2006-10-01 16:45 ` Al Viro
2006-10-01 16:52 ` Linus Torvalds
2006-10-01 17:22 ` Al Viro
2006-10-01 17:29 ` Al Viro
2006-10-01 17:58 ` Linus Torvalds
2006-10-01 17:33 ` Linus Torvalds [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=Pine.LNX.4.64.0610011031280.3952@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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).