unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 6018@debbugs.gnu.org
Subject: bug#6018: 23.1.96; doc of version(-list)*
Date: Fri, 23 Apr 2010 23:39:10 +0300	[thread overview]
Message-ID: <831ve53nv5.fsf@gnu.org> (raw)
In-Reply-To: <A9CF931065A1473786DF0126CF65310E@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Fri, 23 Apr 2010 12:04:59 -0700
> Cc: 
> 
> There is no explanation (spec) of the elements in the *-list functions.

They are internal functions.  Perhaps we should say that explicitly in
the doc strings.

The doc strings that should be reviewed are those for version<,
version=, and version<=.  They are the ``entry points'' to this group
of functions.  The rest are internal subroutines.

> There is a little more info in the doc strings of `version-regexp-alist'
> and `version-to-list', but again, there are only examples, no
> explanation.  Please describe the _mapping_ between parts of version
> strings (e.g. the sub regexps "pre", "beta", "alpha" etc.) and negative
> integers as list elements.

What description is needed, given that you can see the value?






  reply	other threads:[~2010-04-23 20:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 19:04 bug#6018: 23.1.96; doc of version(-list)* Drew Adams
2010-04-23 20:39 ` Eli Zaretskii [this message]
2010-04-23 21:06   ` Drew Adams
2011-07-13 18:06   ` Lars Magne Ingebrigtsen
2011-07-13 18:20     ` Drew Adams
2011-07-14  2:04       ` Chong Yidong
2011-07-14  2:51         ` Drew Adams
2011-07-14  6:30           ` Eli Zaretskii
2011-07-14 14:05             ` Drew Adams
2011-07-14 15:58               ` Eli Zaretskii
2012-01-07  6:15                 ` Lars Magne Ingebrigtsen
2011-07-16 18:42       ` 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=831ve53nv5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=6018@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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).