unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Wilson Snyder <wsnyder@wsnyder.org>
Cc: kaushal.modi@gmail.com, npostavs@users.sourceforge.net,
	Emacs developers <emacs-devel@gnu.org>,
	Tino Calancha <tino.calancha@gmail.com>
Subject: Re: Comment in verilog-mode.el about supported versions
Date: Tue, 20 Dec 2016 00:35:22 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1612200032100.6414@calancha-pc> (raw)
In-Reply-To: <7qzijs6lc6.fsf@emma.svaha.wsnyder.org>



On Mon, 19 Dec 2016, Wilson Snyder wrote:

> Verilog-mode is a bit unique.  It's not just a programming
> mode that is used inside Emacs, but a computer aided design
> tool that extends the Verilog language, relied on in most
> every chip design company, and often run as a standalone
> tool from Emacs batch.
>
> Thus there are often important bugs which need to be fixed
> back into what would otherwise be considered "old" Emacs
> versions. cc-mode and like doesn't have this issue.
>
> Also because of this, verilog-mode.el is often part of the
> source code control system of design environments, which
> need to run regardless that different users and systems may
> have different Emacs versions installed.
>
> Users often upgrade verilog-mode.el themselves, and so
> having a single file, that they can easily install and know
> will work, no matter their version of Emacs, is critical.
>
> Perhaps this path is more development work (though due to
> version maintenance effort I'd argue that). But, I don't see
> any way in which splitting versions nor splitting files
> would help the users.
>
> Anyhow, regardless of these choices, new Emacs features are
> made available.  By no means is the least common denominator
> all that is supported.
>
> -Wilson

Understood.
Thank you very much for your detailed explanation.

Tino



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

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

  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=alpine.DEB.2.20.1612200032100.6414@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=npostavs@users.sourceforge.net \
    --cc=wsnyder@wsnyder.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).