From: Mike Stump <mikestump@comcast.net>
To: Dimitris Papavasiliou <dpapavas@gmail.com>
Cc: "gcc-patches@gcc.gnu.org Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add a couple of dialect and warning options regarding Objective-C instance variable scope
Date: Mon, 12 May 2014 19:14:00 -0000 [thread overview]
Message-ID: <10610AAF-A142-4566-A67E-A03C4716A219@comcast.net> (raw)
In-Reply-To: <53711978.7000404@gmail.com>
On May 12, 2014, at 11:56 AM, Dimitris Papavasiliou <dpapavas@gmail.com> wrote:
> So we [ .. ] expect that they silently shadow the instance variables, that is that warnings are _not_ generated.
Perfect, thanks. I’ve checked it in:
Committed revision 210333.
Thanks for all your hard work.
> So I take it that I should change these to dg-bogus since this is behavior expected in the past but not now, as well as any other expected non-warnings in the other test cases? Is it important in some way that dg-bogus makes no distinction between warning and error messages?
No. One could, but, not necessary.
next prev parent reply other threads:[~2014-05-12 19:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 9:22 Dimitris Papavasiliou
2014-02-13 14:19 ` [PING][PATCH] " Dimitris Papavasiliou
2014-02-20 10:08 ` [PING^2][PATCH] " Dimitris Papavasiliou
2014-02-27 9:41 ` [PING^3][PATCH] " Dimitris Papavasiliou
2014-03-06 17:41 ` [PING^4][PATCH] " Dimitris Papavasiliou
2014-03-13 9:52 ` Dimitris Papavasiliou
2014-03-23 1:32 ` [PING^6][PATCH] " Dimitris Papavasiliou
2014-03-28 10:11 ` [PING^7][PATCH] " Dimitris Papavasiliou
2014-04-03 15:29 ` [PING^8][PATCH] " Dimitris Papavasiliou
2014-04-24 10:39 ` Dimitris Papavasiliou
2014-04-24 20:29 ` Jakub Jelinek
2014-04-25 0:17 ` Dimitris Papavasiliou
2014-04-25 1:07 ` Mike Stump
2014-04-25 11:40 ` Dimitris Papavasiliou
2014-04-24 16:03 ` [PATCH] " Mike Stump
2014-04-24 23:16 ` Dimitris Papavasiliou
2014-04-25 3:20 ` Mike Stump
2014-04-25 16:50 ` Dimitris Papavasiliou
2014-04-25 16:53 ` Mike Stump
2014-04-28 10:37 ` Dimitris Papavasiliou
2014-05-05 7:31 ` Dimitris Papavasiliou
2014-05-12 7:49 ` Dimitris Papavasiliou
2014-05-12 16:25 ` Mike Stump
2014-05-12 18:57 ` Dimitris Papavasiliou
2014-05-12 19:14 ` Mike Stump [this message]
2014-05-12 20:53 ` Mike Stump
2014-05-13 14:17 ` Dimitris Papavasiliou
-- strict thread matches above, loose matches on Subject: below --
2013-06-09 21:44 Dimitris Papavasiliou
2013-06-24 12:09 ` Dimitris Papavasiliou
2013-07-02 8:05 ` Dimitris Papavasiliou
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=10610AAF-A142-4566-A67E-A03C4716A219@comcast.net \
--to=mikestump@comcast.net \
--cc=dpapavas@gmail.com \
--cc=gcc-patches@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).