From: IainS <developer@sandoe-acoustics.co.uk>
To: "Nicola Pero" <nicola.pero@meta-innovation.com>
Cc: "gcc-patches@gnu.org" <gcc-patches@gnu.org>
Subject: Re: ObjC/ObjC++: updated documentation on supported standards, and added -fobjc-std=objc1
Date: Tue, 02 Nov 2010 14:10:00 -0000 [thread overview]
Message-ID: <7250274D-80F6-4299-83DB-1004C5EA7CB0@sandoe-acoustics.co.uk> (raw)
In-Reply-To: <1288705446.69544186@192.168.2.229>
On 2 Nov 2010, at 13:44, Nicola Pero wrote:
>
>> .. the only issue with using 'std' is that there are no 'standards'
>> as
>> such
>
> Yes. :-)
>
> But I'd like to use "std" in the name because it does the same
> things that
> -std=... does for C/C++: it makes the compiler conform to a certain
> dialect
> of the language. In this case, the dialect ("Objective-C 1.0") is
> specified
> by referring to a reference implementation (GCC 4.0). I'd say that
> is the
> same as what an option like -std=gnu89 does. Most GCC users are
> aware of
> -std=c90 and similar and it makes sense for them to have an option
> with
> a similar name (-fobjc-std=...) for the Objective-C dialect. (it
> could be
> argued that it should be -objc-std=... to be more similar to -std=...)
>
> If we don't want to use "std", maybe I'd be happy with -fobjc-
> dialect=xxx.
Mike OK'd it already ;-)
Iain
next prev parent reply other threads:[~2010-11-02 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 10:07 Nicola Pero
2010-11-02 10:13 ` IainS
2010-11-02 13:48 ` Nicola Pero
2010-11-02 14:10 ` IainS [this message]
2010-11-02 17:59 ` Mike Stump
2010-11-02 19:19 ` Nicola Pero
2010-11-02 20:03 ` IainS
2010-11-02 10:21 ` 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=7250274D-80F6-4299-83DB-1004C5EA7CB0@sandoe-acoustics.co.uk \
--to=developer@sandoe-acoustics.co.uk \
--cc=gcc-patches@gnu.org \
--cc=nicola.pero@meta-innovation.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).