From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] varargs question
Date: Thu, 20 Aug 2009 11:32:11 -0400 [thread overview]
Message-ID: <2e6a7f21164b7acb613947bc62fcff3d@quanstro.net> (raw)
In-Reply-To: <dd6fe68a0908200805q677254a5q4541b71f0b89745a@mail.gmail.com>
> what problem are you trying to solve?
>
> the limit would check only that the right number of
> argument bytes are consumed, but not that they are
> interpreted correctly. print("%s %d", 1, "hello") would
> still crash, as would print("%s", 1, "hello").
>
> #pragma varargck is more precise and can be
> done at compile time instead of needing to wait
> until the code trips at run time.
varargck is very effective. but it only works if the pragma
is used. (i count 47 functions with ... in /sys/include and
only 27 #pragma varargck argpos.) and it only works with
functions taking print verbs. anyone else, is out-of-luck.
for example, the stdio functions.
here are some functions that don't appear to have varargck
that likely should:
auth_wep
ctlerror
hfail
vtDebug
vtFatal
threadsetname
vtlogprint
vtlog
- erik
prev parent reply other threads:[~2009-08-20 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 13:56 erik quanstrom
2009-08-20 15:05 ` Russ Cox
2009-08-20 15:32 ` erik quanstrom [this message]
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=2e6a7f21164b7acb613947bc62fcff3d@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).