From: Ray Lee <ray-lk@madrabbit.org>
To: tomstdenis@yahoo.com
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Prohibited attachment type (was 0xdeadbeef)
Date: Wed, 07 Jul 2004 08:57:36 -0700 [thread overview]
Message-ID: <1089215855.4373.194.camel@orca.madrabbit.org> (raw)
On Wed, Jul 07, 2004 at 04:48:36AM -0700, tom st denis wrote:
> It will warn that 0xDEADBEEF is unsigned (which it isn't).
It is. Either read the standard, or read any of my email messages where
I quote the thing at you.
> Either there is an obscure clause in the C standard
Duuuude. The ANSI C standard is about 40 pages in the back of the K&R
second edition. You could read through it in a few hours. If you're
writing C code for more than just a pastime, you should do yourself a
favor and read it. It's really not all that obscure or hard to
understand.
> [I personally don't have a copy of C99 nor do I plan on reading it
> for this]
Then how about you listen to people who have it, read it, and understand
it? Or how about at least believing that gcc is telling you the truth
when it warns that 0xdeadbeef is an unsigned constant?
Ray
next reply other threads:[~2004-07-07 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 15:57 Ray Lee [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-07 11:10 0xdeadbeef vs 0xdeadbeefL tom st denis
2004-07-07 11:18 ` Prohibited attachment type (was 0xdeadbeef) Richard B. Johnson
2004-07-07 11:48 ` tom st denis
2004-07-07 12:29 ` Jakub Jelinek
2004-07-08 5:52 ` Pavel Machek
2004-07-08 14:03 ` Jakub Jelinek
2004-07-07 12:13 ` R. J. Wysocki
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=1089215855.4373.194.camel@orca.madrabbit.org \
--to=ray-lk@madrabbit.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomstdenis@yahoo.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.