From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <embe8573@student.uu.se>, help-gnu-emacs@gnu.org
Subject: RE: cl-dolist, dolist, cl-return,
Date: Wed, 8 Jul 2015 07:02:16 -0700 (PDT) [thread overview]
Message-ID: <22e63da7-d7e4-42b8-9060-8584e442558b@default> (raw)
In-Reply-To: <87twtf2bt4.fsf@nl106-137-147.student.uu.se>
> there are so many, which overlap...
> In C there are what I remember only three loops (if
> you don't count recursion, or gotos for that matter) -
> the familiar for, while, and 'do while'.
Because it is easy in Lisp to define your own so-called "control
structures".
So people do. And they share them. And they keep defining them
and sharing them. And some of them get large communities of
adherents or get established as "standard" or conventional for a
given Lisp dialect.
This is different from languages where certain structures are
provided as defining the language, and you must learn them and
stick to them.
You like `do'. I like `while'.
You like `loop'. I like `iterate'.
Tomayto, tomahto, potayto, potahto.
Let's call the whole thing Lisp.
(https://common-lisp.net/project/iterate/doc/index.html)
next prev parent reply other threads:[~2015-07-08 14:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6511.1436314595.904.help-gnu-emacs@gnu.org>
2015-07-08 3:25 ` cl-dolist, dolist, cl-return, Pascal J. Bourguignon
2015-07-08 10:17 ` Emanuel Berg
2015-07-08 14:02 ` Drew Adams [this message]
2015-07-08 23:10 ` Emanuel Berg
[not found] ` <mailman.6588.1436397019.904.help-gnu-emacs@gnu.org>
2015-07-08 23:56 ` Pascal J. Bourguignon
2015-07-08 0:14 Emanuel Berg
2015-07-08 0:31 ` John Mastro
2015-07-08 3:09 ` Stefan Monnier
2015-07-08 10:25 ` Emanuel Berg
2015-07-08 14:44 ` Stefan Monnier
2015-07-08 23:19 ` Emanuel Berg
2015-07-09 1:49 ` John Mastro
2015-07-09 22:00 ` Emanuel Berg
[not found] ` <mailman.6636.1436479362.904.help-gnu-emacs@gnu.org>
2015-07-10 18:44 ` Barry Margolin
2015-07-11 18:52 ` Emanuel Berg
2015-07-10 16:57 ` Stefan Monnier
2015-07-08 10:23 ` Emanuel Berg
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=22e63da7-d7e4-42b8-9060-8584e442558b@default \
--to=drew.adams@oracle.com \
--cc=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.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 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.