unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Generic functions: Specializers like `or' or `memq'?
Date: Thu, 04 Nov 2021 05:01:47 +0100	[thread overview]
Message-ID: <87r1bwr2l0.fsf@zoho.eu> (raw)
In-Reply-To: jwvh7csbqh6.fsf-monnier+emacs@gnu.org

Stefan Monnier via Users list for the GNU Emacs text editor wrote:

>> This is not standard CLOS parlance, because CLOS does not include
>> a mechanism to define new kinds of specializers: you can dispatch on
>> (eql <VAL>) and you can dispatch on types and that's that (tho IIRC, you
>> can actually extend it via the MOP, potentially with the help of some
>> details of your Common-Lisp implementation).
>
> BTW, I took the term "generalizer" from the following article (from
> which I drew a fair bit of inspiration when designing `cl-generic.el`):
>
>     Generalizers: New metaobjects for generalized dispatch
>     http://research.gold.ac.uk/9924/1/els-specializers.pdf

Ah you see... I said it smells like OO spirit. No one likes OO
and everyone likes "functional programming". Well, can you
program as well? It's ridiculous to the point that we should
boast we had it long before and it was functional even then.

Call me poison!

https://www.youtube.com/watch?v=qzBel5-CADE

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2021-11-04  4:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 17:17 Generic functions: Specializers like `or' or `memq'? Michael Heerdegen
2021-11-03 18:21 ` Philip Kaludercic
2021-11-03 21:10   ` Michael Heerdegen
2021-11-03 21:32     ` Eric Abrahamsen
2021-11-03 23:19       ` Michael Heerdegen
2021-11-03 23:38         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-04  0:26           ` Michael Heerdegen
2021-11-04  1:31       ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-04  2:34         ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-04  4:01           ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-11-06 22:32         ` Michael Heerdegen
2021-11-06 23:36           ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-07  1:48             ` Michael Heerdegen
2021-11-21 19:43               ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-23  8:16                 ` Michael Heerdegen
  -- strict thread matches above, loose matches on Subject: below --
2021-11-04 17:31 Eric Abrahamsen
2021-11-05 21:17 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-05 21:36   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-06 23:29     ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-06 23:52       ` Emanuel Berg via Users list for the GNU Emacs text editor

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=87r1bwr2l0.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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.
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).