From: Joe Buck <Joe.Buck@synopsys.COM>
To: Andreas Schwab <schwab@suse.de>,
gcc@gcc.gnu.org, linux-gcc@vger.kernel.org
Subject: Re: Incorrect warning message?
Date: Mon, 17 Jan 2005 08:48:59 -0800 [thread overview]
Message-ID: <20050117084859.A1627@synopsys.com> (raw)
In-Reply-To: <20050116033242.B3181@natasha.ward.six>; from zzz@anda.ru on Sun, Jan 16, 2005 at 03:32:42AM +0500
On Sun, Jan 16, 2005 at 03:32:42AM +0500, Denis Zaitsev wrote:
> On Sat, Jan 15, 2005 at 11:05:44PM +0100, Andreas Schwab wrote:
> > Read question 11.10 of the C faq.
> >
> > http://www.eskimo.com/~scs/C-faq/q11.10.html
>
> Thanks. It's interesting. :)
That FAQ answer is poor. You can find the real reason in the answer
to question 1 in
http://www.jamesd.demon.co.uk/csc/faq.html#PartC
(this is for C++ but the reasoning applies to C as well).
next prev parent reply other threads:[~2005-01-17 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 21:08 Incorrect warning message? Denis Zaitsev
2005-01-15 22:05 ` Andreas Schwab
2005-01-15 22:32 ` Denis Zaitsev
2005-01-17 16:48 ` Joe Buck [this message]
2005-01-18 23:12 ` Denis Zaitsev
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=20050117084859.A1627@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=linux-gcc@vger.kernel.org \
--cc=schwab@suse.de \
/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.