From: Tom Vier <tmv5@home.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT] fputc vs putc Re: horrible disk thorughput on itanium
Date: Sun, 9 Dec 2001 14:14:08 -0500 [thread overview]
Message-ID: <20011209141408.A17671@zero> (raw)
In-Reply-To: <p73n10v6spi.fsf@amdsim2.suse.de> <20011207.130316.39156883.davem@redhat.com> <20011208201907.A937@zero> <m1d71pw51p.fsf@frodo.biederman.org> <9uvaqn$u4s$1@cesium.transmeta.com>
In-Reply-To: <9uvaqn$u4s$1@cesium.transmeta.com>; from hpa@zytor.com on Sun, Dec 09, 2001 at 01:27:51AM -0800
On Sun, Dec 09, 2001 at 01:27:51AM -0800, H. Peter Anvin wrote:
> putc() is frequently defined as
>
> #define putc(__C) fputc((__C), stdout)
>
> ... or some equivalent; I think the best way to say it's that it's a
> shorthand.
according to the putc man page in debian stable, it takes the same args as
fputc. maybe it varies by glibc version (mine is 2.1.3-19). i guess anyone
using putc better use autoconf. also, "unix system programming for SVr4"
says the only difference is that putc is an inlined macro version of fputc.
--
Tom Vier <tmv5@home.com>
DSA Key id 0x27371A2C
next prev parent reply other threads:[~2001-12-09 19:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <p73r8q86lpn.fsf@amdsim2.suse.de.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0112070710120.747-100000@mikeg.weiden.de.suse.lists.linux.kernel>
[not found] ` <9upmqm$7p4$1@penguin.transmeta.com.suse.lists.linux.kernel>
2001-12-07 13:54 ` horrible disk thorughput on itanium Andi Kleen
2001-12-07 14:20 ` Padraig Brady
2001-12-07 16:14 ` Richard Gooch
2001-12-07 17:18 ` Robert Love
2001-12-07 17:40 ` Richard Gooch
2001-12-07 17:48 ` Robert Love
2001-12-07 17:45 ` Linus Torvalds
2001-12-07 17:58 ` Andi Kleen
2001-12-07 18:14 ` Michael Poole
2001-12-07 18:35 ` Padraig Brady
2001-12-07 21:22 ` Michael Poole
2001-12-07 21:37 ` Padraig Brady
2001-12-07 22:26 ` Michael Poole
2001-12-07 18:15 ` Linus Torvalds
2001-12-07 18:41 ` Padraig Brady
2001-12-07 18:33 ` Padraig Brady
2001-12-07 20:44 ` Greg Hennessy
2001-12-07 21:37 ` Marco Colombo
2001-12-07 20:42 ` David S. Miller
[not found] ` <3C112DE4.60206@antefacto.com>
[not found] ` <20011207.130316.39156883.davem@redhat.com>
2001-12-09 1:19 ` [OT] fputc vs putc " Tom Vier
2001-12-09 1:33 ` Eric W. Biederman
2001-12-09 9:27 ` H. Peter Anvin
2001-12-09 19:14 ` Tom Vier [this message]
2001-12-09 22:15 ` H. Peter Anvin
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=20011209141408.A17671@zero \
--to=tmv5@home.com \
--cc=linux-kernel@vger.kernel.org \
/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