unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Martin Stjernholm <mast@lysator.liu.se>
Cc: bug-cc-mode@gnu.org, emacs-devel@gnu.org, Kenichi Handa <handa@m17n.org>
Subject: Re: Change of C indentation style ('{')
Date: Fri, 24 Oct 2003 11:56:25 +0200	[thread overview]
Message-ID: <5bllrb5586.fsf@lister.roxen.com> (raw)
In-Reply-To: <buobrs72t4u.fsf@mcspd15.ucom.lsi.nec.co.jp> (Miles Bader's message of "24 Oct 2003 12:48:17 +0900")

Miles Bader <miles@lsi.nec.co.jp> wrote:

> The thing is, I wouldn't be surprised if `macro oddities' are actually
> more common than the nested functions, or functions in macro arguments...

You're probably right when it comes to C which uses cpp a lot. Perhaps
also for C++, ObjC and Pike; they have cpp support too but it's not
used quite as much there.

It should be possible to add some more checks. Afterall, macro
constructs like that can only be ambiguous with really old fashioned
K&R style function definitions.

  reply	other threads:[~2003-10-24  9:56 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 [this message]
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=5bllrb5586.fsf@lister.roxen.com \
    --to=mast@lysator.liu.se \
    --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).