Re: Nit-picking

[Eli Zaretskii]

[Moving this to emacs-devel, where it belongs.]

> Date: Sat, 12 Apr 2008 09:35:59 +0000
> Cc: address@hidden, address@hidden
> From: Alan Mackenzie <address@hidden>
> 
> > Perhaps it's just me, but there appear to be too many threads on this
> > list that I need to skip entirely, due to their endless discussions of
> > issues of miniscule importance.  OTOH, I don't remember any
> > discussions of important new features for quite some time.  It almost
> > looks like no important development is going on.
> 
> Down at CC Mode, I receive a constant trickle of "little" bugs, things
> that go wrong in unusual (but perfectly reasonable) source code.
> Languages like C++ and Java (and even C itself) are astonishingly
> complicated.
> 
> In the medium future, I'll be concentrating on fixing long-standing,
> difficult bugs: font locking going wrong in the middle of a long struct
> declaration (for lack of syntactic context); inadequate handling of
> template/generic bracketing (by < and >) in C++/Java.  Also, somewhat
> easier, things like making C-M-a go to the beginning of the real
> function/class in C++, not the enclosing outermost class or namespace;
> and somebody asked me for a command to switch between C-style (/* .. */)
> and C++-style (// .... \n) comments.  :-)
> 
> I've got vague ideas for adding "decluttering" commands: commands to
> render things like casts and "frivolous compound statements" (where a
> brace block contains only a single statement) invisible.  These are a
> real eyesore in certain types of proprietary source code.  :-(
> 
> And there's continual refactoring to be done - software this
> complicated, more than a decade old, doesn't stay cleanly implemented
> all by itself.
> 
> All in all, nothing very exciting or earth shattering - but important,
> nevertheless.

CC-Mode is a veteran feature.  I was rather talking about something
radically new, like IDE-like features in CEDET and Semantic, or
function signature and C++ class member tooltips.  (I'm not sure they
are part of CC-Mode's scope, but just to give you an idea.)  These are
great usability aids, IMO, and today's programmers expect to find them
in any development environment.

Elsewhere, there's lot of turf to be covered in the Unicode support
department, like Unicode collation and line breaking, Unicode regular
expressions, script properties, etc.  (See
http://www.unicode.org/reports/index.html for more about these and
other Unicode-related features.)  These all require extensive changes
in core Emacs infrastructure and its main features, so how come all
these changes are never discussed here, nor worked upon?  After all,
Unicode support is the main new feature of Emacs 23, isn't it?

If I think a bit more, I'm sure I will come up with a longer list of
important developments that IMO should keep us busy for some time to
come, instead of being bogged down in disagreement about how to paint
the selected region.