From: Alan Mackenzie <acm@muc.de>
To: Richard Stallman <rms@gnu.org>
Cc: spacibba@aol.com, 36678@debbugs.gnu.org, psmith@gnu.org
Subject: bug#36678: 27.0.50; imenu not working in C++ (maybe because of namespace)
Date: Sun, 4 Aug 2019 08:51:06 +0000 [thread overview]
Message-ID: <20190804085106.GA14630@ACM> (raw)
In-Reply-To: <E1hu6h1-00007x-7u@fencepost.gnu.org>
Hello, Richard.
On Sat, Aug 03, 2019 at 22:56:19 -0400, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > CC Mode has had imenu type indexing right from its inception. What is
> > changing is the increasing complexity of function definitions, in
> > particular, the slow demise of the convention of function names being in
> > column zero.
> Why is that happening? Is there a practical benefit, or is it just
> a matter of fashion, or what?
In C++, it's largely the namespace, which is being used ever more.
Instead of writing
namespace foo {
int bar (int baz)
{
.....
}
.....
}
, people are indenting within the namespace, something like
namespace foo {
int bar (int baz)
{
....
}
....
}
. Not all the time, but a lot of the time, possibly most of the time.
This indentation inside a namespace seems like a natural way to format a
program, and people are going to carry on doing it.
The issue is how we best deal with this.
> --
> Dr Richard Stallman
> President, Free Software Foundation (https://gnu.org, https://fsf.org)
> Internet Hall-of-Famer (https://internethalloffame.org)
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-08-04 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 20:33 bug#36678: 27.0.50; imenu not working in C++ (maybe because of namespace) Ergus
[not found] ` <mailman.1463.1563222851.2688.bug-gnu-emacs@gnu.org>
2019-07-17 14:39 ` Alan Mackenzie
2019-07-17 16:34 ` Alan Mackenzie
2019-07-31 15:56 ` Ergus
2019-08-02 19:33 ` Alan Mackenzie
[not found] ` <20190802193315.GC11966@ACM>
2019-08-02 19:56 ` Paul Smith
2019-08-03 2:25 ` Richard Stallman
2019-08-03 11:27 ` Alan Mackenzie
2019-08-03 15:09 ` Paul Smith
2019-08-04 3:01 ` Richard Stallman
2019-08-04 13:56 ` Paul Smith
2019-08-05 2:25 ` Richard Stallman
2019-08-04 2:56 ` Richard Stallman
2019-08-04 8:51 ` Alan Mackenzie [this message]
2019-08-05 2:26 ` Richard Stallman
[not found] ` <E1htjjb-0002eO-Fo@fencepost.gnu.org>
2019-08-03 7:20 ` Eli Zaretskii
2019-08-03 14:43 ` Paul Smith
2019-08-05 2:24 ` Richard Stallman
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=20190804085106.GA14630@ACM \
--to=acm@muc.de \
--cc=36678@debbugs.gnu.org \
--cc=psmith@gnu.org \
--cc=rms@gnu.org \
--cc=spacibba@aol.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.
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).