unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 8682@debbugs.gnu.org
Subject: bug#8682: 24.0.50; doc strings of `isearch-mode', `isearch-forward', etc.
Date: Fri, 15 Jul 2011 18:56:07 +0200	[thread overview]
Message-ID: <CAAeL0SSXvoJyNQMPNuXfDc4Y+MsnM2uCjiG-bw_aLyKVpmpsig@mail.gmail.com> (raw)
In-Reply-To: <5DED13DA31E94AF9BF6B244A80E299D4@us.oracle.com>

On Fri, Jul 15, 2011 at 17:06, Drew Adams <drew.adams@oracle.com> wrote:

> "Internal" functions too deserve doc strings, in general.
>
> And nothing in Emacs is truly "internal".  Emacs purposefully documents itself,
> at all levels.  That documentation is available to all users interactively.

Of course there are internal elisp functions. Many of them even use a
convention of having two consecutive dashes in the name to mark that
they are internal, but not all.

And what makes them internal is that they are an implementation detail
and could be removed, or changed beyond all recognition, at any
moment. Documenting them past the simple "This is an internal
function" leads the user-developer to falsely believe that they are
part of the interface, but they are not. Otherwise, nothing could ever
be changed but painstakingly and with lot of ugly compatibility code.
Which is fine for the advertised interfaces, but not for every single
function in every single package in lisp/**/*.el.

First someone asks to document them all, then s/he will use them in
some package, and finally s/he will complain harshly when they are
deleted in some future release. Better to say clearly: don't do that,
or do it under you own responsability, after looking at the code, and
knowing full well that if you do you'll likely need to workaround
changes in the future.

(I'm not talking about the specific changes in this bug thread, but
comments like "Nothing in Emacs is truly 'internal'" cannot be let
pass unchallenged...)

    Juanma





  reply	other threads:[~2011-07-15 16:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 14:25 bug#8682: 24.0.50; doc strings of `isearch-mode', `isearch-forward', etc Drew Adams
2011-05-17 14:39 ` Stefan Monnier
2011-05-17 14:46   ` Drew Adams
2011-05-17 17:32     ` Stefan Monnier
2011-05-17 19:12       ` Drew Adams
2011-07-15 13:40 ` Lars Magne Ingebrigtsen
2011-07-15 15:06   ` Drew Adams
2011-07-15 16:56     ` Juanma Barranquero [this message]
2011-07-15 18:30       ` Drew Adams
2011-07-15 14:43 ` Drew Adams
2011-07-15 15:02   ` Lars Magne Ingebrigtsen
2011-07-15 15:02   ` Lars Magne Ingebrigtsen
2011-07-18 14:06   ` Stefan Monnier
2011-07-18 14:13     ` Drew Adams
2013-05-20 22:50       ` Juri Linkov

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=CAAeL0SSXvoJyNQMPNuXfDc4Y+MsnM2uCjiG-bw_aLyKVpmpsig@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=8682@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.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).