From: Joe Buck <jbuck@synopsys.COM>
To: ac131313@cygnus.com (Andrew Cagney)
Cc: kettenis@chello.nl, gcc@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix PR gdb/290
Date: Sat, 09 Feb 2002 11:37:00 -0000 [thread overview]
Message-ID: <200202091936.LAA24545@atrus.synopsys.com> (raw)
In-Reply-To: <3C657641.1080906@cygnus.com> from "Andrew Cagney" at Feb 09, 2002 02:19:29 PM
Andrew writes:
> static void f3 (void) { return; }
> ...
> so ok so far. Hmm, I think this tells the story:
>
> static void f5 (int a) { return f3(); }
>
> Returning the result from a function that returns void (f3()) doesn't
> attract a warning.
> Bug or feature?
For C++, it is a non-optional feature; the standard requires this to work
correctly (a void function may say "return foop();" if foop's return type
is void). The reason for this will become clear after you write templates
for a while; without it "void" becomes more of an oddball case.
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.
next prev parent reply other threads:[~2002-02-09 19:37 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 [this message]
2002-02-09 11:51 ` Andrew Cagney
2002-02-09 12:18 ` Andreas Schwab
2002-02-09 17:39 ` Joe Buck
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=200202091936.LAA24545@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 \
/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