From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] stdio.h va_list declarations
Date: Wed, 9 Oct 2002 17:10:24 +0100 [thread overview]
Message-ID: <30104453414fc13051b235708f7e74f0@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
vfprintf etc don't take variable argument lists, but have one
parameter of type va_list that points to a variable argument list. since you're
outside the APE environment (or it would be using /sys/include/ape/stdio.h)
you need to include <u.h> before <stdio.h>, as for nearly any
other Plan 9 include file (despite the comment to the contrary in
intro(2)). in practice, you'll typically also need <libc.h> for any real program
(eg, to declare exits).
[-- Attachment #2: Type: message/rfc822, Size: 2092 bytes --]
From: "Skip Tavakkolian" <fst@centurytel.net>
To: 9fans@cse.psu.edu
Subject: [9fans] stdio.h va_list declarations
Date: Wed, 9 Oct 2002 08:08:17 -0400
Message-ID: <16d2a7daabbaf56b66e19efb07d17c32@centurytel.net>
I get:
/sys/include/stdio.h:79[temp.cp:405] mixed ansi/old function declaration: vfprintf
/sys/include/stdio.h:80[temp.cp:406] mixed ansi/old function declaration: vprintf
/sys/include/stdio.h:81[temp.cp:407] mixed ansi/old function declaration: vsprintf
/sys/include/stdio.h:82[temp.cp:408] mixed ansi/old function declaration: vsnprintf
/sys/include/stdio.h:83[temp.cp:409] mixed ansi/old function declaration: vfscanf
it is complaining about the use of va_list instead of '...' in the
prototype declaration.
next reply other threads:[~2002-10-09 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 16:10 Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 17:05 Russ Cox
2002-10-09 15:56 Russ Cox
2002-10-09 13:56 Skip Tavakkolian
2002-10-09 13:47 Skip Tavakkolian
2002-10-09 13:20 Skip Tavakkolian
2002-10-09 12:08 Skip Tavakkolian
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=30104453414fc13051b235708f7e74f0@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).