all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Comment in verilog-mode.el about supported versions
Date: Mon, 19 Dec 2016 10:02:28 -0500	[thread overview]
Message-ID: <jwvvaugezp8.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: alpine.DEB.2.20.1612192241320.6414@calancha-pc

> Sorry, I don't understand why it should be difficult or what makes more
> difficult to handle this file that, for instance tramp or cc-mode.

Note that the cc-mode in Emacs is also full of compatibility code (and
the fact that it's not 100% identical to the code distributed separately
is a serious problem that has caused Alan to reject some changes simply
because they were too hard to sync back to the other version).

Having compatibility code is normal and accepted.  It's more important
to make maintenance easy than to streamline the Emacs's builtin code.

> Wouldn't it better to keep one verilog-mode.el version in ELPA fully
> compatible with Emacs-21?
> And let the file in the master branch to benefit of all that
> has come since Emacs-21?

It's better to have a single version for both cases.  It does not mean
that you can't benefit from all that has come since Emacs-21 (well,
maybe in some cases you can't benefit from 100% but still a very large
percentage).

> I also notice that the file is very large (> 14 klines).
> Maybe it would be easier to maintain if the file is split in 4-5 files.

A single file also has its benefits (I don't have an opinion either way,
really: just pointing out that it's a very valid choice as well).


        Stefan




  reply	other threads:[~2016-12-19 15:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19 13:37 Comment in verilog-mode.el about supported versions Wilson Snyder
2016-12-19 14:02 ` Tino Calancha
2016-12-19 15:02   ` Stefan Monnier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-12-19 14:32 Wilson Snyder
2016-12-19 15:35 ` Tino Calancha
2016-12-19 11:49 Tino Calancha
2016-12-19 13:02 ` Kaushal Modi
2016-12-19 13:09   ` Noam Postavsky
2016-12-19 13:47 ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvvaugezp8.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.