unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: Why is there no `until' in elisp?
Date: Wed, 17 Oct 2018 01:00:15 +0200	[thread overview]
Message-ID: <87d0s9lcow.fsf@portable.galex-713.eu> (raw)
In-Reply-To: <875zy1fxod.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 16 Oct 2018 13:23:30 -0700")

On 2018-10-16 at 13:23, Eric Abrahamsen wrote:
> 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.

I was to say that when it’s about simple enough things, there’s a way
people agree, especially if we try keeping it minimal, but then Stefan
Monnier proposed a different version of until I didn’t though about, so
I must admit this is more complex (I keep thinking we need different
words / identifiers for non-minimal cases).

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

If we’re effectively speaking of stuff big enough to justify a package,
then we’re going into DSL libraries that might make themselves alien and
less readable to the uninitiated.

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

I’m unsure, it encourages reinventing the wheel, while there are other
measurment to discriminate between what is known, common and popular and
the more experimental rest.



  reply	other threads:[~2018-10-16 23:00 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
2018-10-16 23:00       ` Garreau, Alexandre [this message]
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=87d0s9lcow.fsf@portable.galex-713.eu \
    --to=galex-713@galex-713.eu \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.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 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).