all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: xfq.free@gmail.com, ttn@gnu.org, drew.adams@oracle.com,
	emacs-devel@gnu.org
Subject: Re: Changes in revision 114466
Date: Mon, 30 Sep 2013 18:42:17 +0300	[thread overview]
Message-ID: <83ioxie2p2.fsf@gnu.org> (raw)
In-Reply-To: <87txh24n7d.fsf@rosalinde.fritz.box>

> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Mon, 30 Sep 2013 12:29:26 +0200
> Cc: Xue Fuqiao <xfq.free@gmail.com>, Thien-Thi Nguyen <ttn@gnu.org>,
> 	emacs-devel <emacs-devel@gnu.org>
> 
>    [These functions/variables are] not meant to be used by other
>    packages [, which] means that something defined with "--" can
>    completely change (or disappear) from one release to the other.
> 
> This suggests that developers who use them should be working on the
> package they are in, hence reading and using the code and commentary of
> that package.  In contrast, documentation for developers is, I think,
> aimed at explaining the code's public interface to use in developing
> other packages, not its private, internal only interface (at least the
> documentation in the manual; such functions/variables could have doc
> strings).

Indeed.  The ELisp manual is aimed primarily at a Lisp programmer who
develops Lisp programs, not necessarily Emacs per se.  Someone who
develops Emacs can rarely stay at the Lisp level for too long, so the
documentation needed by Emacs developers should have a radically
different orientation, and include information we currently don't have
anywhere except in the comments.

It is a good idea to have such documentation for Emacs developers, but
no one stepped forward to do the job (which is not trivial).



  parent reply	other threads:[~2013-09-30 15:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.53349.1380335551.10747.emacs-diffs@gnu.org>
2013-09-28  7:46 ` Changes in revision 114466 Eli Zaretskii
2013-09-28 22:30   ` Xue Fuqiao
2013-09-29  2:36     ` Eli Zaretskii
2013-09-29  7:24       ` Thien-Thi Nguyen
2013-09-30  4:55         ` Xue Fuqiao
2013-09-30  5:21           ` Drew Adams
2013-09-30 10:29             ` Stephen Berman
2013-09-30 15:05               ` Drew Adams
2013-09-30 15:52                 ` Thien-Thi Nguyen
2013-10-01  2:11                 ` Stephen J. Turnbull
2013-09-30 15:42               ` Eli Zaretskii [this message]
2013-09-30 11:47             ` Andreas Röhler
2013-09-30 15:38           ` Eli Zaretskii
     [not found]           ` <<83k3hye2uq.fsf@gnu.org>
2013-09-30 16:38             ` Drew Adams
2013-10-01  3:40               ` Xue Fuqiao
2013-10-01  4:57                 ` Stephen J. Turnbull
2013-10-01  5:15                   ` Drew Adams
2013-10-01  5:27                     ` Drew Adams
2013-10-01  6:11                     ` Stephen J. Turnbull
2013-10-01  7:44                       ` Drew Adams
2013-10-01  8:29                         ` Stephen J. Turnbull

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=83ioxie2p2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=stephen.berman@gmx.net \
    --cc=ttn@gnu.org \
    --cc=xfq.free@gmail.com \
    /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.