all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Philip Kaludercic" <philipk@posteo.net>,
	"Mattias Engdegård" <mattiase@acm.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: The FIXME in `dotimes'
Date: Wed, 7 Sep 2022 15:18:58 +0000	[thread overview]
Message-ID: <SJ0PR10MB54889B32068BFAD6FBB94399F3419@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87o7vrnu65.fsf@posteo.net>

> >>   (dotimes (count) ...)
> >
> > Lisp syntax rarely make the first element optional, and in this case
> > it's both the first and the last one:
> >
> >   (dotimes ([VAR] COUNT [RESULT]) BODY...)
> >
> > which is a bit alien, and it's perhaps not worth the trouble for just
> > omitting an underscore?
> >
> >>   (dotimes count ...)
> >
> > That wouldn't allow for arbitrary expressions so it's of limited
> > utility (and Lisp-alien, again). There's also the risk that someone
> > will eventually replace a variable by a function call, turning
> > (dotimes x ...) into (dotimes (f x) ...).
> 
> I agree, the idea was not well thought out and not worth the
> complication.

In addition to what's been said - It's not bad,
other things being equal, to keep it more or
less in sync with what it's taken from, which
is Common Lisp DOTIMES (and which apparently
was inspired by Interlisp's RPTQ).


  parent reply	other threads:[~2022-09-07 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 10:22 The FIXME in `dotimes' Philip Kaludercic
2022-09-07 12:13 ` Mattias Engdegård
2022-09-07 13:35   ` Philip Kaludercic
2022-09-07 13:37   ` Philip Kaludercic
2022-09-07 14:08     ` Mattias Engdegård
2022-09-07 14:19       ` Philip Kaludercic
2022-09-07 14:29         ` Robert Pluim
2022-09-07 15:18         ` Drew Adams [this message]
2022-09-07 15:26           ` [External] : " Philip Kaludercic

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=SJ0PR10MB54889B32068BFAD6FBB94399F3419@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.org \
    --cc=philipk@posteo.net \
    /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.