From: npostavs@users.sourceforge.net
To: Tino Calancha <f92capac@gmail.com>
Cc: 23550@debbugs.gnu.org
Subject: bug#23550: 25.0.93; cl.texi (for var on list by func): Fix documentation
Date: Sat, 25 Mar 2017 23:01:45 -0400 [thread overview]
Message-ID: <874lyg68rq.fsf@users.sourceforge.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1605170046230.14791@calancha-ilc.kek.jp> (Tino Calancha's message of "Tue, 17 May 2016 00:49:02 +0900 (JST)")
Tino Calancha <f92capac@gmail.com> writes:
> * doc/misc/cl.texi (for var on list by func): Fix documentation
>
> 'cl-loop for var on list by func' behaves as in CL: 'on' expression
> need to be a list.
Well, it only needs to be a cons, because that's what the loop checks
for.
>
> emacs -Q:
>
> (require 'cl-lib)
> (setq preys '("grass" "lion" "rabbit"))
>
> (defun next-prey (x)
> "Return the name of the prey of animal X."
> (cl-loop while (not (atom x))
> do (setq x (car x)))
> (cond ((member x preys) ; elisp
> ;; (cond ((member x preys :test #'string=) ; CL
> (cond ((string= x "lion") "rabbit")
> ((string= x "rabbit") "grass")
> (t nil)))
> (t
> nil)))
> (defun next-prey-list (x)
> "Return a list with the name of the prey of animal X."
> (let ((res (next-prey x)))
> (if res
> (list res)
> nil)))
I guess the idea behind that statement is that the rest of the list can
be implied by the stepping function, e.g.
(cl-loop for y on (list "lion") by #'next-prey-list collect (car y))
;=> ("lion" "rabbit" "grass")
Works with the "in" clause too:
(cl-loop for y in (list "lion") by #'next-prey-list collect y)
;=> ("lion" "rabbit" "grass")
I guess it could be useful in combination with streams? Not sure if
it's worth having this in the manual.
next prev parent reply other threads:[~2017-03-26 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 15:49 bug#23550: 25.0.93; cl.texi (for var on list by func): Fix documentation Tino Calancha
2017-03-26 3:01 ` npostavs [this message]
2017-03-29 13:26 ` Tino Calancha
2017-03-29 14:08 ` npostavs
2017-03-31 8:20 ` Tino Calancha
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=874lyg68rq.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=23550@debbugs.gnu.org \
--cc=f92capac@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.