all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Richard Stallman <rms@gnu.org>
Cc: Drew Adams <drew.adams@oracle.com>,  emacs-devel@gnu.org
Subject: Re: [External] : Emacs object type hierarchy
Date: Tue, 24 Oct 2023 04:39:16 -0400	[thread overview]
Message-ID: <yp1il6wjtxn.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1qv5jn-0002UA-4h@fencepost.gnu.org> (Richard Stallman's message of "Mon, 23 Oct 2023 20:57:39 -0400")

Hello Richard,

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > Yes, it would be good to have the Elisp type hierarchy
>   > spelled out.  This is what the Common Lisp doc says
>   > about its hierarchy, FWIW:
>
> Have we ever defined such a hierarchy for Emacs Lisp?
> (I don't think so.)

I'm not the best one to answer this but I think as well was never
explicitly defined, OTOH traces of it are in many places of our
codebase.

> If not, do we want to?

I think so, documenting it would be good.

> What would would that involve?

Essentially just making it explicit in our documentation.

> And would having such a defined hierarchy tend to lead us to think we
> need to do other work -- work which, arguably, we don't really need to
> do?

I don't think so, OTOH new code could make use of it easily and reliably
instead of having to reverse engineer the current implementation.

Best Regards

  Andrea



  parent reply	other threads:[~2023-10-24  8:39 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22  8:44 Emacs object type hierarchy Andrea Corallo
2023-10-22  9:08 ` Gerd Möllmann
2023-10-22  9:37   ` Gerd Möllmann
2023-10-23 15:08     ` Andrea Corallo
2023-10-23 16:36       ` Gerd Möllmann
2023-10-23 16:48         ` Gerd Möllmann
2023-10-24  8:28         ` Andrea Corallo
2023-10-22 16:11 ` [External] : " Drew Adams
2023-10-24  0:57   ` Richard Stallman
2023-10-24  2:03     ` Emanuel Berg
2023-10-24  8:39     ` Andrea Corallo [this message]
2023-10-24  9:32       ` Emanuel Berg
2023-10-22 22:08 ` Yuan Fu
2023-10-23 15:06   ` Andrea Corallo
2023-10-23 15:49     ` John Yates
2023-10-24  3:37     ` Yuan Fu
2023-10-23 15:20 ` Andrea Corallo
2023-10-23 15:46   ` Eli Zaretskii
2023-10-24  9:21     ` Andrea Corallo
2023-10-24 11:55       ` Eli Zaretskii
2023-10-24 12:02         ` Andrea Corallo
2023-10-24 12:53           ` Emanuel Berg
2024-02-15 17:28           ` Andrea Corallo
2024-02-15 17:40             ` Andrea Corallo
2024-02-17  9:04               ` Emanuel Berg
2024-02-18 19:25                 ` Andrea Corallo
2024-02-17  9:19               ` Eli Zaretskii
2024-02-17  9:38                 ` Emanuel Berg
2024-02-17  9:41                 ` Emanuel Berg
2024-02-18 19:23                 ` Andrea Corallo
2024-02-18 19:33                   ` Eli Zaretskii
2024-02-18 19:37                     ` Eli Zaretskii
2024-02-19  7:52                     ` Andrea Corallo
2024-02-19 16:51                       ` Andrea Corallo
2024-02-26 17:50                         ` Andrea Corallo
2024-03-01  8:36                           ` Andrea Corallo
2024-03-01  8:56                             ` Eli Zaretskii
2024-03-01  9:46                               ` Andrea Corallo
2024-02-16 20:31             ` Basil L. Contovounesios
2024-02-18 19:14               ` Andrea Corallo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yp1il6wjtxn.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.