Gnus development mailing list
 help / color / mirror / Atom feed
From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: Emacs 20.4 & Pterodactyl & pop3.el
Date: 29 Aug 1999 17:45:13 +0200	[thread overview]
Message-ID: <byd7w6y4ja.fsf@bolzano.math.ethz.ch> (raw)
In-Reply-To: Stainless Steel Rat's message of "Sun, 29 Aug 1999 13:27:15 GMT"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> But on the other hand, the XEmacs developers did the same thing, just on a
> much larger scale.  Compare my code with the pop3 in XEmacs 21 and you will
> see very, very significant differences.  The XEmacs develpers never
> informed me of these changes, either, nor have they honored my request that
> they change the name so as to avoid confusion.

This is indeed very bad :-( and is in fact very much against "XEmacs
policy". I can only apologize. It seems to be working in other cases
(for instance for EFS, ediff and reftex we forward the patches to the
respective maintainers, they release a new version and then _that_
gets out in the respective XEmacs package).
One of the reasons for having such a policy is that is extremely hard
to get out of such a mess.

Changing name is unfortunately not always an option, especially not
for libraries that are required. Say you write an (almost) completely
compatible implementation of some elisp file, then for the user to
easily make use of is you want the interface (feature name, variable & 
function names) to be identical.

For instance I wrote lazy-shot.el, apart from the replacement of
string "lazy-lock" by "lazy-shot" it is a complete, XEmacs specific,
re-implementation of lazy-lock v2 as shipped with GNU Emacs. The only
things I copied from lazy-shot are doc strings. I tried very hard to
make the interface identical as I wanted the users customization to
work under both Emacs versions. I originally wanted to rename my
variables and functions to lazy-lock for that reason. However Simon
Marshall (the author of lazy-lock) wants me keep the names different
in order to avoid confusion. I have not done the renaming but still
don't like the situation. The problem here is that the name of
variables and function indicates both the interface and a particular
implementation.

To get back to pop3. I don't know why your weren't informed of the
initial changes, however I can see why don't see the newer ones: Andy
seems to have made the fork "official":

;; Maintainer:      Andy Piper <andy@xemacs.org>

;; Keywords: mail, pop3
;; Version: 2.04

;; [..]

;; mostly stolen from epop3mail. Please address problems with this
;; version (2.xx) to [Andy Piper].

Jan


  reply	other threads:[~1999-08-29 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Jan Vroonhof's message of "29 Aug 1999 17:45:13 +0200">
1999-08-27 14:10 ` Emacs 20.4 & Pterodactyl Lars Magne Ingebrigtsen
1999-08-27 15:07   ` Nicolas Chuche
1999-08-27 15:23     ` Lars Magne Ingebrigtsen
1999-08-27 15:35       ` Nicolas Chuche
1999-09-25  6:27         ` Lars Magne Ingebrigtsen
1999-08-27 15:32     ` What's Gnus 5.7? (was: Re: Emacs 20.4 & Pterodactyl) Kai Großjohann
1999-08-28  0:07   ` Emacs 20.4 & Pterodactyl & pop3.el Stainless Steel Rat
1999-08-28 17:34     ` Jan Vroonhof
1999-08-29 13:24       ` Stainless Steel Rat
1999-08-29 15:45         ` Jan Vroonhof [this message]
1999-08-29 20:51           ` Stainless Steel Rat
1999-08-29 21:04             ` Andy Piper

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=byd7w6y4ja.fsf@bolzano.math.ethz.ch \
    --to=vroonhof@math.ethz.ch \
    /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.
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 NNTP newsgroup(s).