From: Leo Liu <sdl.web@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r117133: * doc/lispref/sequences.texi (Sequence Functions): Update nreverse.
Date: Thu, 22 May 2014 08:22:59 +0800 [thread overview]
Message-ID: <m3ha4ihdb0.fsf@gmail.com> (raw)
In-Reply-To: <jwvlhtvcnpu.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Wed, 21 May 2014 08:38:32 -0400")
On 2014-05-21 08:38 -0400, Stefan Monnier wrote:
> The docstring is good, but the above manual entry is too specific.
> We don't want to specify when side-effects are used and when not.
Do you mean simplify the doc to something like this:
=== modified file 'doc/lispref/sequences.texi'
--- doc/lispref/sequences.texi 2014-05-21 03:49:58 +0000
+++ doc/lispref/sequences.texi 2014-05-22 00:21:12 +0000
@@ -265,12 +265,7 @@
@cindex reversing a list
@cindex reversing a vector
This function reverses the order of the elements of @var{seq}.
-If @var{seq} is a list, @code{nreverse} alters it by reversing the @sc{cdr}s
-in the cons cells. The cons cell that used to be the last one in @var{seq}
-becomes the first cons cell of the value. If @var{seq} is a vector or
-bool vector, its items are placed in the same vector in a reversed
-order. If @var{seq} is a string, it works like @code{reverse} i.e., no
-destructive modifcation in preference to treat strings as immutable.
+The original @var{seq} may be modified.
For example:
next prev parent reply other threads:[~2014-05-22 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Wmxi0-00082E-7A@vcs.savannah.gnu.org>
2014-05-21 12:38 ` [Emacs-diffs] trunk r117133: * doc/lispref/sequences.texi (Sequence Functions): Update nreverse Stefan Monnier
2014-05-22 0:22 ` Leo Liu [this message]
2014-05-22 1: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ha4ihdb0.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.