From: Miles Bader <miles@lsi.nec.co.jp>
Cc: Kenichi Handa <handa@m17n.org>, bug-cc-mode@gnu.org, emacs-devel@gnu.org
Subject: Re: Change of C indentation style ('{')
Date: 24 Oct 2003 12:48:17 +0900 [thread overview]
Message-ID: <buobrs72t4u.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <5bhe1zy4z8.fsf@lister.roxen.com>
Martin Stjernholm <mast@lysator.liu.se> writes:
> That is because FOR_EACH_FRAME isn't recognized as
> a substatement introducing keyword, and barring macro oddities
> everything else has to be function definitions.
>
> I'm not sure what to do about it. There are other cases when this new
> heuristic is useful, e.g. for functions in macro arguments or gcc
> nested functions.
The thing is, I wouldn't be surprised if `macro oddities' are actually
more common than the nested functions, or functions in macro arguments...
-Miles
--
I'd rather be consing.
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-10-24 3:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 1:09 Change of C indentation style ('{') Kenichi Handa
2003-10-23 22:16 ` Martin Stjernholm
2003-10-24 1:25 ` Kenichi Handa
2003-10-24 3:48 ` Miles Bader [this message]
2003-10-24 9:56 ` Martin Stjernholm
2003-10-24 10:11 ` Miles Bader
2003-10-24 23:24 ` Richard Stallman
2003-10-25 14:40 ` Martin Stjernholm
2003-10-27 7:02 ` Richard Stallman
2003-10-27 14:24 ` Martin Stjernholm
2003-10-28 20:39 ` Richard Stallman
2003-10-29 19:28 ` Martin Stjernholm
2003-10-29 21:41 ` Miles Bader
2003-10-30 0:03 ` Martin Stjernholm
2003-10-30 0:11 ` Miles Bader
2003-10-30 0:30 ` Stefan Monnier
2003-10-30 18:00 ` Richard Stallman
2003-10-30 18:01 ` 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=buobrs72t4u.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=miles@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).