unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Why aren't there functions such as filter, take-while, etc. "by  default"?
Date: Sun, 25 Apr 2010 21:09:49 +0200	[thread overview]
Message-ID: <878w8b9wn6.fsf@gmail.com> (raw)
In-Reply-To: <87fx2j5wle.fsf@lola.goethe.zz> (David Kastrup's message of "Sun,  25 Apr 2010 18:24:29 +0200")

David Kastrup <dak@gnu.org> writes:

> Deniz Dogan <deniz.a.m.dogan@gmail.com> writes:
>
>> Why does it have to be so hard to write Emacs Lisp without requiring cl?
>>
>> Why aren't there functions such as filter (the equivalent of
>> remove-if-not in cl-seq.el), take-while, reduce etc. "native" in
>> Emacs?
>
> They make for no-surprise efficient programs primarily when the language
> has lexical closures.

What about `case', though?

Or `position'?

It's ridiculous -- you have to either define helpers again and again all
the time, or write unnecessarily verbose code, or require the whole of
cl (and I don't think `eval-when-compile' makes so much of a difference
outside Emacs core; it's not like people compile all third-party
packages they use).

The Emacs cl.el "policy" seems rather schizophrenic to me -- if there's
something unsatisfactory about it, then it should be fixed instead of
being banished to compile-time-only. Or failing that, some generally
useful forms like the above should be provided in Emacs core.


  Štěpán




  reply	other threads:[~2010-04-25 19:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24 20:13 Why aren't there functions such as filter, take-while, etc. "by default"? Deniz Dogan
2010-04-25 16:24 ` David Kastrup
2010-04-25 19:09   ` Štěpán Němec [this message]
2010-04-25 20:27   ` Deniz Dogan
2010-04-25 22:56     ` Drew Adams
2010-04-25 23:10       ` Deniz Dogan
2010-04-26  3:39   ` Stefan Monnier
2010-04-26  8:29     ` David Kastrup
2010-04-26  8:35       ` David Kastrup

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=878w8b9wn6.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=dak@gnu.org \
    --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).