unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: Tim Van Holder <tim.vanholder@gmail.com>,
	bug-cc-mode@gnu.org, emacs-devel@gnu.org,
	emacs-pretest-bug@gnu.org
Subject: c-macro-expand isn't part of CC Mode  [Was: cpp use in cc-mode is broken]
Date: Wed, 4 May 2005 10:05:16 +1200	[thread overview]
Message-ID: <17015.62876.255539.37519@farnswood.snap.net.nz> (raw)
In-Reply-To: <Pine.LNX.3.96.1050503204007.426B-100000@acm.acm>

Alan Mackenzie writes:
 > >As of a few days ago, the cc-mode in cvs emacs seems to preprocess the
 > >source file in order to determine the C macros present.

Actually to generate a list of #define directives.

 > Please Note: `c-macro-expand', despite its name, is _NOT_ part of CC
 > Mode.  Its name prefix "c-" is misleading here.  That, and the fact that
 > it has a binding in some of the CC Mode keymaps, is its only connection
 > with CC Mode.  (If you look carefully, you'll find it's not in the CC
 > Mode manual.  ;-)

Within Emacs CVS, I think both cc-mode.el and cmacexp.el are part of
Emacs.

 > `c-macro-expand' actually lives in the file
 > .../list/progmodes/cmacexp.el.  This file was last updated 3 years 8
 > months ago by Eli.

Thats why I'm interested in updating the variable c-macro-preprocessor.

 > There seem to have been a lot of patches to cc-mode.el and friends for
 > c-macro-expand in the last week.  Would somebody please take all these
 > changes out of the CC Mode files and put them into cmacexp.el instead.
 > Otherwise, there's going to be confusion and significant lack of
 > happiness when the time comes to merge the upcoming version of CC Mode
 > (5.31) into savannah.

They wouldn't work in cmacexp.el because they were part of c-mode. I've
already moved them now into gud.el and gdb-ui.el, anyway. Not because
cc-mode.el is part of CC Mode but because they were bad changes. If someone
makes good changes to cc-*.el files in Emacs CVS, then they would presumably
become part of your merge.

Nick


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20


  reply	other threads:[~2005-05-03 22:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d69e7f6a05042907184bd4842d@mail.gmail.com>
2005-05-03 21:00 ` c-macro-expand isn't part of CC Mode [Was: cpp use in cc-mode is broken] Alan Mackenzie
2005-05-03 22:05   ` Nick Roberts [this message]
2005-05-10 21:56     ` c-macro-expand isn't part of CC Mode Martin Stjernholm
2005-05-04 20:54   ` c-macro-expand isn't part of CC Mode [Was: cpp use in cc-mode is broken] Eli Zaretskii
2005-05-05 19:44   ` 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=17015.62876.255539.37519@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=tim.vanholder@gmail.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).