9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lee Duhem <lee.duhem@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c's feature or bug?
Date: Fri,  9 Feb 2007 02:01:45 +0800	[thread overview]
Message-ID: <20070208180145.GA9556@debian> (raw)
In-Reply-To: <19c957c9b96a78a95e0c7fb973fd89a8@terzarima.net>

On Thu, Feb 08, 2007 at 05:33:32PM +0000, Charles Forsyth wrote:
> you're mixing ANSI prototypes and the original style, and
> in
> 	void f(b)
> 	char b;
> 
> i suspect b is promoted to int, because before prototypes C compilers
> didn't know an argument was a char at point of call, and chars were promoted to int (similarly float to double),
> and the function with the argument so promoted clashes with the earlier void f(char).
> 

I give prototypes of foo and foo1 before use and define them, maybe 8c
just ignore these prototypes when it see the definitions.

> in any case, if you're going to use 8c at all, just commit to ANSI prototypes.
> in fact, even if you're not going to use 8c, just use ANSI prototypes and either way,
> avoid or eliminate the ARGS crud.
> 
> surely it must be at least 20 years old.
> 
> if the code is imported i suppose it doesn't matter, but if it's new code,
> using ARGS or __PROTO or whatever is usually just silly.

It's old code, anyway.

Lee


  reply	other threads:[~2007-02-08 18:01 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 [this message]
2007-02-08 17:59     ` Russ Cox
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=20070208180145.GA9556@debian \
    --to=lee.duhem@gmail.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).