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 13:23:30 -0700	[thread overview]
Message-ID: <875zy1fxod.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87o9btr8m2.fsf@portable.galex-713.eu

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

> On 2018-10-16 at 12:16, Eric Abrahamsen wrote:
>> "Garreau, Alexandre" <galex-713@galex-713.eu> writes:
>>> [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.
>
> Why?  If this is because of the triviality of reimplementing, wouldn’t
> they do, once they want to use it in contributing emacs (I keep seeing
> many (while (not …) …))?  or do they restrain themselves for some
> rational/useful reason I still ignore?
>
> The “it’s one macro more to learn fully the language” doesn’t stand that
> much (especially about elisp) to me as it is easy to read source code,
> easy to find definitions, and “unless” is as much an english word as
> “while” (maybe even more widespread, outside of programming).

Again, I'm not one of these developers, so I'm putting words in others'
mouths...

I don't think it has anything to do with making the language harder to
learn. It's just the fact that the constructs are so easy to add (this
is the power of lisp, after all), and different developers might want
very slightly different versions of the same thing, so people just put
in their own versions of things.

Obviously there are plenty of people who feel differently about it,
which is why we have all these supplementary packages within Emacs and
the package repositories.

But the core of the language remains conservative about additions.
Personally, I think that's a good thing.

Eric




  reply	other threads:[~2018-10-16 20:23 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
2018-10-16 19:31   ` Garreau, Alexandre
2018-10-16 20:23     ` Eric Abrahamsen [this message]
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=875zy1fxod.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).