unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Martin Stjernholm <mast@lysator.liu.se>
Cc: Alan Mackenzie <acm@muc.de>,
	Tim Van Holder <tim.vanholder@gmail.com>,
	bug-cc-mode@gnu.org, emacs-devel@gnu.org,
	emacs-pretest-bug@gnu.org
Subject: Re: c-macro-expand isn't part of CC Mode
Date: Tue, 10 May 2005 23:56:12 +0200	[thread overview]
Message-ID: <5bbr7ibv9f.fsf@lister.roxen.com> (raw)
In-Reply-To: <17015.62876.255539.37519@farnswood.snap.net.nz> (Nick Roberts's message of "Wed, 4 May 2005 10:05:16 +1200")

Nick Roberts <nickrob@snap.net.nz> wrote:

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

Maybe so, but it's more relevant to note what the respective
maintainers are inclined to support. If the CC Mode maintainers aren't
prepared to support a certain feature then it's better to not add that
feature to the cc-*.el files. That avoids confusion with bug reports
sent to the wrong places, bitrot and possible lossage in merges.

In this particular case the added feature was outside the scope of CC
Mode, so it's good that it was taken out again (although I'm sure the
feature in itself is very neat). The scope of CC Mode isn't spelled
out anywhere, so I don't blame anyone for missing it. Anyway, it is
something like this:

o  Provide functionality for syntax parsing in the supported
   languages.
o  Implement basic major mode operations for the supported languages,
   meaning buffer setup, movement/mark commands and miscellaneous
   simple tools for handling language constructs (e.g. aligning the
   backslashes in cpp macros).
o  Implement syntactically sensitive indentation and font locking.

Some noteworthy things that are outside the scope:

o  Tracking of symbols, e.g. for providing tooltips containing symbol
   docs and type info etc, or for locating symbol definitions.
o  Stuff that requires knowledge of the compilation environment, e.g.
   pulling in include files, expand macros, tracking cross file
   references.
o  Templates for source constructs, e.g. to quickly insert a more or
   less complete class or method.

These are not left out just because I personally don't consider them
nice features (I do), but because implementing those things well is
nontrivial and requires quite a bit of dedicated effort. I, and I
probably speak for Alan Mackenzie as well here, have enough with
getting the things inside the current scope to work as well as we
would like. Also, there's no particular reason why stuff like that
can't be in separate packages.


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click


  reply	other threads:[~2005-05-10 21:56 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
2005-05-10 21:56     ` Martin Stjernholm [this message]
2005-05-04 20:54   ` 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=5bbr7ibv9f.fsf@lister.roxen.com \
    --to=mast@lysator.liu.se \
    --cc=acm@muc.de \
    --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).