From: Philipp Stephani <p.stephani2@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 29339@debbugs.gnu.org
Subject: bug#29339: 27.0.50; CC-mode doesn't know about .mm and .M suffixes for Objective-C++
Date: Thu, 21 Dec 2017 19:22:05 +0000 [thread overview]
Message-ID: <CAArVCkSuiUq1dB+7CiFrJmxOG3K3erOKxOhRiA3rT0H9ZPuzFQ@mail.gmail.com> (raw)
In-Reply-To: <20171117190035.77279.qmail@mail.muc.de>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Alan Mackenzie <acm@muc.de> schrieb am Fr., 17. Nov. 2017 um 20:00 Uhr:
> In article <mailman.3878.1510925890.27995.bug-gnu-emacs@gnu.org> you
> wrote:
>
> > GCC uses .mm or .M for Objective-C++,
> > cf. https://gcc.gnu.org/onlinedocs/gcc-7.2.0/gcc/Overall-Options.html.
> > However, neither `auto-mode-alist' nor `cc-other-file-alist' contain
> > these file extensions.
>
> I don't think there's an Objective-C++ mode out there in the wild. So
> what existing mode should be used for *.mm and *.M? Is that mode a good
> enough fit to be able, in good conscience, to use it for Obj-C++?
>
According to https://www.emacswiki.org/emacs/ObjectiveCMode#toc2 objc-mode
is the most appropriate mode for now, until a true objc++-mode is added.
[-- Attachment #2: Type: text/html, Size: 1336 bytes --]
next prev parent reply other threads:[~2017-12-21 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 13:36 bug#29339: 27.0.50; CC-mode doesn't know about .mm and .M suffixes for Objective-C++ Philipp
[not found] ` <mailman.3878.1510925890.27995.bug-gnu-emacs@gnu.org>
2017-11-17 19:00 ` Alan Mackenzie
2017-12-21 19:22 ` Philipp Stephani [this message]
2017-12-22 12:56 ` Alan Mackenzie
2017-12-22 16:50 ` Glenn Morris
2021-06-03 10:07 ` bug#2732: 23.0.91; Please add support " Lars Ingebrigtsen
2021-06-03 12:08 ` Philipp
2021-06-03 12:42 ` bug#29339: " Lars Ingebrigtsen
2021-06-03 12:45 ` Lars Ingebrigtsen
2021-06-03 12:39 ` Alan Mackenzie
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAArVCkSuiUq1dB+7CiFrJmxOG3K3erOKxOhRiA3rT0H9ZPuzFQ@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=29339@debbugs.gnu.org \
--cc=acm@muc.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).