From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c's feature or bug?
Date: Thu, 8 Feb 2007 12:59:21 -0500 [thread overview]
Message-ID: <ee9e417a0702080959t15825ce6p19c1dbd253077d93@mail.gmail.com> (raw)
In-Reply-To: <20070208180145.GA9556@debian>
> I give prototypes of foo and foo1 before use and define them, maybe 8c
> just ignore these prototypes when it see the definitions.
What Charles said is right:
void foo(b) char b; { }
void foo(int b);
produces no warnings, but
void foo(b) char b; { }
void foo(char b);
does.
Russ
next prev parent reply other threads:[~2007-02-08 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 17:28 Lee Duhem
2007-02-08 17:33 ` Charles Forsyth
2007-02-08 18:01 ` Lee Duhem
2007-02-08 17:59 ` Russ Cox [this message]
2007-02-08 18:48 ` Charles Forsyth
2007-02-09 10:09 ` Lee Duhem
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=ee9e417a0702080959t15825ce6p19c1dbd253077d93@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).