public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: patdoyle@ca.ibm.com To: gcc-gnats@gcc.gnu.org Subject: c/8294: Support another archetype in "format" function attribute Date: Sun, 20 Oct 2002 14:16:00 -0000 [thread overview] Message-ID: <20021020211040.14875.qmail@sources.redhat.com> (raw) >Number: 8294 >Category: c >Synopsis: Support another archetype in "format" function attribute >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Sun Oct 20 14:16:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: patdoyle@ca.ibm.com >Release: unknown-1.0 >Organization: >Environment: >Description: A common way to write vararg functions is to have the function take a count of the number of arguments that follow. (Let's call this, say, the "enumerated" format, just so I can refer to it below.) It would be nice if calls to this kind of function were checked by gcc to have the right number of arguments. This could be a variant of the "format" attribute, like the following: void foo(int arg_count, ...) __attribute__ ((format (enumerated(arg_count)))); In fact, even better would be if one could specify any linear function; for example, if the number of arguments should be 2*arg_count+1, then perhaps it could be declared like so: void foo(int arg_count, ...) __attribute__ ((format (enumerated(arg_count, 2, 1)))); This would enable it to handle cases I have seen that do data base queries, where the number of key-value pairs is passed: result_t query(char *table_name, int key_count, ...) __attribute__ ((format(enumerated(key_count, 2, 0)))); I hope this is the right forum for this kind of feature request. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-10-20 21:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021020211040.14875.qmail@sources.redhat.com \ --to=patdoyle@ca.ibm.com \ --cc=gcc-gnats@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).