Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.COM>
To: schwab@suse.de (Andreas Schwab)
Cc: jbuck@synopsys.COM (Joe Buck),
	ac131313@cygnus.com (Andrew Cagney),
	kettenis@chello.nl, gcc@gcc.gnu.org,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix PR gdb/290
Date: Sat, 09 Feb 2002 17:39:00 -0000	[thread overview]
Message-ID: <200202100138.RAA25290@atrus.synopsys.com> (raw)
In-Reply-To: <jelme2pfxc.fsf@suse.de> from "Andreas Schwab" at Feb 09, 2002 09:18:39 PM

> Joe Buck <jbuck@synopsys.COM> writes:
> 
> |> For C89, I don't think it's legal though it may be reasonable to accept
> |> as an extension; I don't know about C99.
> 
> The C99 standard is quite clear about this:
> 
>     6.8.6.4[#1] A return statement with an expression shall not appear in
>     a function whose return type is void.  A return statement without an
>     expression shall only appear in a function whose return type is void.

OK, then this can only be done in C++.  Any C code should avoid it.

for 
void foo();
void bar() { return foo();}

(which is legal C++)

I've just checked, and gcc 2.95.2 and 3.0.3 reject this type of C code
iff -ansi -pedantic is specified.  By default they accept it.  Anyone
developing code that must compile with many compilers probably should
be using -pedantic.


      reply	other threads:[~2002-02-10  1:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09  9:27 kettenis
2002-02-09 11:19 ` Andrew Cagney
2002-02-09 11:37   ` Joe Buck
2002-02-09 11:51     ` Andrew Cagney
2002-02-09 12:18     ` Andreas Schwab
2002-02-09 17:39       ` Joe Buck [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=200202100138.RAA25290@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=ac131313@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --cc=schwab@suse.de \
    /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