public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Lemings <elemings@lemings.com>
To: eljay@adobe.com, eric@lemings.com, gcc-help@gcc.gnu.org
Subject: Re: Const in default function arguments?
Date: Fri, 04 Apr 2003 18:10:00 -0000	[thread overview]
Message-ID: <200304041808.h34I8PS8024622@cyberia.lemings.com> (raw)

void foo (int i) {
  ++i;
}

This function foo doesn't make sense either but it's not a
compile error.  Just because something doesn't make sense
doesn't mean it's illegal.  Sounds like the non-const
parameter should be a warning, not an error.

An error means that it's illegal and the standard defines
what is legal and what is not.  Can somebody not point to
the standard that says you can't use a default function
argument for a non-const parameter?

Thanks.

             reply	other threads:[~2003-04-04 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 18:10 Eric Lemings [this message]
2003-04-04 19:59 ` John Love-Jensen
2003-04-05 10:27   ` Nathan Sidwell
2003-04-05 16:24 ` LLeweLLyn Reese
  -- strict thread matches above, loose matches on Subject: below --
2003-04-05 11:30 Eric Lemings
2003-04-05 12:24 ` Nathan Sidwell
2003-04-04 20:12 Eric Lemings
2003-04-03 22:10 Eric Lemings
2003-04-04 12:32 ` John Love-Jensen

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=200304041808.h34I8PS8024622@cyberia.lemings.com \
    --to=elemings@lemings.com \
    --cc=eljay@adobe.com \
    --cc=eric@lemings.com \
    --cc=gcc-help@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).