unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Why is there no `until' in elisp?
Date: Tue, 16 Oct 2018 12:16:57 -0700	[thread overview]
Message-ID: <877eihbt1y.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87murdu6to.fsf@portable.galex-713.eu

"Garreau, Alexandre" <galex-713@galex-713.eu> writes:

> Sometimes I have the strong feeling that the symetric of “while”,
> “until” [0], unlike in many languages such as C, exists in elisp.  That
> happened to me several times, and usually I bug for about an hour before
> to realize I do this confusion because it has the symetric of “when”:
> “unless”, but not the same for “while”.
>
> However, “until” exists, for instance in bash (which has no “unless”…
> maybe because it has no “when” because it has guarded “if”s?), and I
> find it pretty handy for making stuff more readable and avoiding making
> stuff more complex…
>
> Is there a particular rational or style reason for not using a such
> trivial and obvious (both in terms of implementation and
> understandement) construct?
>
> If not so, why isn’t it in elisp, aside of `when' and `unless' in
> subr.el (if that ought to be the correct file?)?
>
> [0] such as: (defmacro until (test &rest body) (declare (indent 1))
> `(while (not ,test) ,@body))

I have nothing to do with this, but my feeling is that Lisp developers
in general drag their feet about adding trivial/obvious constructs to
the standard library. As your footnote makes clear, it's a two-line code
addition to make `until' work. There are different schools of thought
about this: one that says "why?", and one that says "why not"? The "why
not"s contribute to subr.el and subr-x.el :)




  reply	other threads:[~2018-10-16 19:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 17:42 Why is there no `until' in elisp? Garreau, Alexandre
2018-10-16 19:16 ` Eric Abrahamsen [this message]
2018-10-16 19:31   ` Garreau, Alexandre
2018-10-16 20:23     ` Eric Abrahamsen
2018-10-16 23:00       ` Garreau, Alexandre
2018-10-19 15:28   ` Stefan Monnier
2018-10-16 21:28 ` Stefan Monnier
2018-10-17  0:12   ` Garreau, Alexandre
2018-10-17  2:04     ` Stefan Monnier
2018-10-17  9:14       ` Garreau, Alexandre
2018-10-17 15:06         ` Stefan Monnier
2018-10-17 16:51           ` Garreau, Alexandre
2018-10-19 15:34     ` Stefan Monnier
2018-10-19 18:08       ` Garreau, Alexandre
2018-10-17  8:04   ` Yuri Khan
2018-10-17  9:23     ` Garreau, Alexandre
2018-10-17  9:46       ` Yuri Khan
2018-10-17 11:06         ` Garreau, Alexandre
2018-10-17 17:50         ` Paul Eggert
2018-10-17 21:15           ` Garreau, Alexandre
2018-10-17 21:35             ` Paul Eggert
2018-10-17 21:49               ` Garreau, Alexandre
2018-10-17 22:33                 ` Paul Eggert
2018-10-17 22:54                   ` Garreau, Alexandre
2018-10-17 12:41     ` Elias Mårtenson
2018-10-17 15:03     ` 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

  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=877eihbt1y.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).