From: Roland Winkler <Roland.Winkler@physik.uni-erlangen.de>
Subject: Re: replacing a certain element in a list with another
Date: 23 Oct 2003 14:46:39 +0200 [thread overview]
Message-ID: <m3u160cea8.fsf@tfkp07.physik.uni-erlangen.de> (raw)
In-Reply-To: 9PBlb.171$lK3.18@news.level3.com
Barry Margolin <barry.margolin@level3.com> writes:
> When you start, you have the following:
>
> Cell A: car = 1
> cdr = reference to Cell B
> Cell B: car = 2
> cdr = reference to Cell C
> Cell C: car = 3
> cdr = reference to Cell D
> Cell D: car = 4
> cdr = nil
> x's value cell = reference to Cell A
>
> When you call nreverse, it is passed the contents of x's value cell,
> i.e. the reference to Cell A. It reverses the list by keeping all the
> car's the same, but reversing the cdr links; this changes things to:
>
> Cell A: car = 1
> cdr = nil
> Cell B: car = 2
> cdr = reference to Cell A
> Cell C: car = 3
> cdr = reference to Cell B
> Cell D: car = 4
> cdr = reference to Cell C
>
> Now the first cons in the reversed list is Cell D, and nreverse returns
> this as its value.
>
> But x's value cell still contains a reference to Cell A, which has become
> the last cons in the chain. So when you print it, you just see the
> 1-element list containing the last element of the reversed list.
>
> Why is it done this way? Because this is the simplest way to reverse a
> list in place. It can just step through the list, replacing each cdr with
> a reference to the preceding cons cell. This is much easier than swapping
> all the car's in order to keep the order of the conses intact.
Thank you very much!
It might be helpful to add a comment to the docstring or info page
for nreverse saying that its argument is modified such that
afterwards it is a 1-element list containing the last element of the
reversed list.
Roland
next prev parent reply other threads:[~2003-10-23 12:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 8:38 replacing a certain element in a list with another Klaus Berndl
2003-09-30 9:05 ` David Kastrup
2003-09-30 9:59 ` Klaus Berndl
2003-09-30 10:03 ` David Kastrup
2003-09-30 10:19 ` Klaus Berndl
2003-09-30 12:12 ` Pascal Bourguignon
2003-09-30 14:14 ` Stefan Monnier
2003-09-30 14:26 ` Klaus Berndl
2003-09-30 14:16 ` Stefan Monnier
2003-09-30 14:28 ` Klaus Berndl
2003-09-30 15:03 ` Stefan Monnier
2003-09-30 15:30 ` Kevin Rodgers
2003-09-30 15:47 ` Stefan Monnier
2003-09-30 18:27 ` Roland Winkler
2003-09-30 20:01 ` Barry Margolin
2003-10-16 20:52 ` Kai Grossjohann
2003-10-22 20:06 ` Roland Winkler
2003-10-22 20:32 ` Barry Margolin
2003-10-23 12:46 ` Roland Winkler [this message]
2003-10-23 14:25 ` Stefan Monnier
2003-10-23 15:30 ` Kevin Rodgers
2003-10-23 15:18 ` Barry Margolin
2003-10-23 22:03 ` Roland Winkler
2003-10-23 22:20 ` Barry Margolin
2003-10-24 12:02 ` Roland Winkler
2003-10-24 15:06 ` Barry Margolin
2003-10-25 11:25 ` Oliver Scholz
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=m3u160cea8.fsf@tfkp07.physik.uni-erlangen.de \
--to=roland.winkler@physik.uni-erlangen.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).