From: Iain Sandoe <iain_sandoe@mentor.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: [PATCH] objc: update documetation and add test-case of constructor/destructor attr.
Date: Tue, 27 Sep 2016 12:50:00 -0000 [thread overview]
Message-ID: <C54FCCF7-7762-4544-9811-817190D949D6@mentor.com> (raw)
In-Reply-To: <57ABE897.9010807@codesourcery.com>
> On 10 Aug 2016, at 19:53, Sandra Loosemore <sandra@codesourcery.com> wrote:
>
> On 08/10/2016 03:11 AM, Martin Liška wrote:
>> Hi.
>>
>> Following patch clarifies usage of ctor and dtor attributes for Objective C.
>> Patch survives (on x86_64-linux-gnu):
>>
>> make -k check-objc RUNTESTFLAGS="execute.exp"
>>
>> Ready for trunk?
>
> The documentation fix looks fine, but probably an objc maintainer needs to confirm that it's not just an accident that the test case works.
Appologies; traveling this week so won’t be able to give this proper attention until I get back to the office (Mike might have something to add however).
I don’t believe it’s an accident that the test-case works.
Objective-C / Objective-C++ are supposed to be supersets of the parent language, and the test case is pure C compiled with an Objective-C FE (so the underlying C should ‘just work’).
What I don’t expect to be supported is to try to apply that attribute to any Objective-C entity (but I would like to qualify that statement with some double-checking once i’m back in the office).
thanks,
Iain
next prev parent reply other threads:[~2016-09-27 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 9:11 Martin Liška
2016-08-11 2:53 ` Sandra Loosemore
2016-09-27 12:50 ` Iain Sandoe [this message]
2016-09-27 11:27 ` Martin Liška
2016-09-28 19:12 ` Mike Stump
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=C54FCCF7-7762-4544-9811-817190D949D6@mentor.com \
--to=iain_sandoe@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=sandra@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).