From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: "James A. Morrison" <ja2morri@csclub.uwaterloo.ca>, gcc@gcc.gnu.org
Subject: Re: Static nested functions
Date: Wed, 01 Dec 2004 17:43:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0412011741500.19970@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87wtw1kjg6.fsf@codesourcery.com>
On Wed, 1 Dec 2004, Zack Weinberg wrote:
> > (with appropriate tests for static declarations at block scope with
> > extern and static ones at file scope, and for auto declarations at
> > block scope which should shadow outer static or extern declarations
> > with the same name, and that auto declarations or nested function
> > definitions with implied auto conflict with extern declarations at
> > the same scope but not with other auto declarations at the same
> > scope).
>
> I can't parse this sentence; is it just a list of appropriate tests?
> If so, would you be willing to implement such a test and file a 4.1-
> target PR?
Yes, it's a list of appropriate tests. I can write the tests (minus the
diagnostics which may depend on the exact patch; the point of the tests
being that certain errors are detected and do not cause a crash, the exact
errors following the first one not being so important).
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
next prev parent reply other threads:[~2004-12-01 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 7:12 James A. Morrison
2004-12-01 7:36 ` Zack Weinberg
2004-12-01 11:05 ` Joseph S. Myers
2004-12-01 17:38 ` Zack Weinberg
2004-12-01 17:43 ` Joseph S. Myers [this message]
2004-12-02 1:22 ` James A. Morrison
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=Pine.LNX.4.61.0412011741500.19970@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=ja2morri@csclub.uwaterloo.ca \
--cc=zack@codesourcery.com \
/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).