unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Matthias Meulien <orontee@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Calling C++ hackers.  Please try out the new handling of C++11 lambda functions in CC Mode.
Date: Sun, 21 Aug 2016 00:06:30 +0200	[thread overview]
Message-ID: <1471730790.1410.16.camel@gmail.com> (raw)
In-Reply-To: <20160820151955.GB2529@acm.fritz.box>

> I'm hoping to get C++11 uniform initialisation working sometime in
> the next few days.

Interesting. As I am using this style of initialization now., so I'll
test your work on my code base.

To test your implementation of C++ lambda functions handling, I've had
to build Emacs from a fresh checkout and just realized that it now
handles C++11 keywords like `nullptr' or `override'; Many thanks to
those who are bringing Emacs to modern C++!

By the way, did you experience the same strange behavior of font
locking when the `override' keyword is added to a constructor? I mean
in:

struct foo : public bar {
  foo() {}

  ~foo() override {}

  void do_something() {}
};

the function name `~foo' is not fontified. It is if the `override'
keyword is removed...

Shall I fill a bug report? 
-- 
Matthias



  reply	other threads:[~2016-08-20 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 12:24 Calling C++ hackers. Please try out the new handling of C++11 lambda functions in CC Mode Alan Mackenzie
2016-08-15 16:17 ` Eli Zaretskii
2016-08-19 21:45 ` Matthias Meulien
2016-08-20 15:19   ` Alan Mackenzie
2016-08-20 22:06     ` Matthias Meulien [this message]
2016-08-21 12:24       ` Alan Mackenzie
2016-08-27 15:35         ` Matthias Meulien
2016-08-27 20:27           ` Alan Mackenzie
2016-08-21 16:22       ` Alan Mackenzie
2016-08-24 19:27         ` Richard Copley
2016-08-24 19:43           ` Alan Mackenzie
2016-08-24 21:10             ` Richard Copley
2016-08-27 15:37         ` Matthias Meulien

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=1471730790.1410.16.camel@gmail.com \
    --to=orontee@gmail.com \
    --cc=acm@muc.de \
    --cc=emacs-devel@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.
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).