public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/8506: 3.3 (1104) disallowing omission of parameters in fn def Date: Fri, 08 Nov 2002 10:06:00 -0000 [thread overview] Message-ID: <20021108180607.2003.qmail@sources.redhat.com> (raw) The following reply was made to PR c/8506; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: jdonner0@earthlink.net Cc: gcc-gnats@gcc.gnu.org Subject: Re: c/8506: 3.3 (1104) disallowing omission of parameters in fn def Date: Fri, 8 Nov 2002 13:02:33 -0500 On Fri, Nov 08, 2002 at 05:52:24PM -0000, jdonner0@earthlink.net wrote: > >Description: > gcc now makes it an error to omit parameter names, eg > > int foo(int /* note, omitted parameter name*/){} > now gives an error. > > $ gcc foo.c > foo.c: In function `foo': > foo.c:1: error: parameter name omitted It's correct C++, but I don't believe it's correct C. Try renaming the file and running "gcc -c foo.cc" (or .cpp or whatever) instead. You can always omit the names in declarations, of course, but not definitions. Phil -- I would therefore like to posit that computing's central challenge, viz. "How not to make a mess of it," has /not/ been met. - Edsger Dijkstra, 1930-2002
next reply other threads:[~2002-11-08 18:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-08 10:06 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-08 11:59 pme 2002-11-08 10:36 Christian Ehrhardt 2002-11-08 10:16 Richard Earnshaw 2002-11-08 9:56 jdonner0
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=20021108180607.2003.qmail@sources.redhat.com \ --to=phil@jaj.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).