unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: bug-cc-mode@gnu.org, handa@m17n.org, emacs-devel@gnu.org
Subject: Re: Change of C indentation style ('{')
Date: Mon, 27 Oct 2003 02:02:21 -0500	[thread overview]
Message-ID: <E1AE1OP-0007PE-Kw@fencepost.gnu.org> (raw)
In-Reply-To: <5b1xt1l6si.fsf@lister.roxen.com> (message from Martin Stjernholm on Sat, 25 Oct 2003 16:40:29 +0200)

    That would also undo this improvement:

	** Statements are recognized in a more robust way.
	Statements are recognized most of the time even when they occur in an
	"invalid" context, e.g. in a function argument.  In practice that can
	happen when macros are involved.

    As an example, it fixes better indentation in this case:

	void f() {
	  SOME_MACRO (
	    if (successful)
	      fprintf (stderr, "ok\n");
	    else
	      abort();
	  );
	}

i see.

this test case has the { starting a fn body
not at col 0.  does the improvement occur in the same way
when users put the { in col 0?

  reply	other threads:[~2003-10-27  7:02 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
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 [this message]
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=E1AE1OP-0007PE-Kw@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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).