unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: supporting older versions of emacs (was: Re: bootstrap fails AND how about fixing the byte-compiler?)
Date: Wed, 16 Jan 2008 21:31:28 +0000	[thread overview]
Message-ID: <20080116213128.GC2171@muc.de> (raw)
In-Reply-To: <200801160547.m0G5laV0007175@sallyv1.ics.uci.edu>

Hi, Dan!

On Tue, Jan 15, 2008 at 09:47:30PM -0800, Dan Nicolaescu wrote:
> Alan Mackenzie <acm@muc.de> writes:

>   > Anyhow, it seems the best solution for cc-vars.el right now (after
>   > all, it's got to work with Emacs 2[01] and various flavours of
>   > XEmacs, too), is to change c-constant-symbol into a macro.  

> It's obviously your choice, but is it worth it to still support
> emacs-20? 

Yes, I think so, given how little effort that actually takes.

> 21.1 was released in October 2001. 
> Is the number of people that do not upgrade to emacs-21, but still want
> to use the latest cc-mode significant enough to be worth the trouble?

Upgrading an unfamiliar piece of software is a nightmare of fear,
uncertainty and doubt.  (And Emacs is "unfamiliar" to nearly all its
users in this context.)  Will the new version of the software work?  More
to the point how much work will it take to get it to work, iron out the
niggly little differences, and so on?

I think there will be a lot of Emacs users still on old versions, though
they make very little noise.  I don't think giving them compatibility
headaches is the best way of persuading them to upgrade.

However, this is just my personal opinion.  ;-)

-- 
Alan Mackenzie (Nuremberg, Germany).

  parent reply	other threads:[~2008-01-16 21:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1JEXu8-0004C3-Cy@cvs.savannah.gnu.org>
2008-01-15  0:03 ` bootstrap fails Katsumi Yamaoka
2008-01-16  0:13   ` bootstrap fails AND how about fixing the byte-compiler? Alan Mackenzie
2008-01-16  0:58     ` Miles Bader
2008-01-16  2:15     ` Katsumi Yamaoka
2008-01-16  5:47     ` supporting older versions of emacs (was: Re: bootstrap fails AND how about fixing the byte-compiler?) Dan Nicolaescu
2008-01-16  8:12       ` supporting older versions of emacs Glenn Morris
2008-01-16 21:21         ` Alan Mackenzie
2008-01-16 22:29           ` Reiner Steib
2008-01-16 22:58             ` Glenn Morris
2008-01-16 23:41               ` Reiner Steib
2008-01-16 21:31       ` Alan Mackenzie [this message]
2008-01-16 23:40         ` supporting older versions of emacs (was: Re: bootstrap fails AND how about fixing the byte-compiler?) Dan Nicolaescu

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=20080116213128.GC2171@muc.de \
    --to=acm@muc.de \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.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).