From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: [External] : Emacs object type hierarchy Date: Tue, 24 Oct 2023 04:39:16 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19368"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Drew Adams , emacs-devel@gnu.org To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 24 10:40:58 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qvCyA-0004tL-A3 for ged-emacs-devel@m.gmane-mx.org; Tue, 24 Oct 2023 10:40:58 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qvCxS-0002fO-Tj; Tue, 24 Oct 2023 04:40:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qvCxJ-0002dz-0d for emacs-devel@gnu.org; Tue, 24 Oct 2023 04:40:07 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qvCwz-0002mU-VE; Tue, 24 Oct 2023 04:40:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=Y3Tu6U8r9W7eH7UjiMG2ymDM21zourgBssMgJ5zr/dI=; b=dRidFPcHVtQfzk68JuHI L3+w4utg0c0FLnwkKae26qs1NeGdtZzN5dITaceA2Gwd9OMiHv2mHxGqo1wWs9adRKZImVpTxTTWt HLAJUPLJErmXr6SZGh957qhKvauvTHs+hQBUgZHORGzcLKdDwHC2as8gxbkcuBxVJuTOJsUiik8Aw cnEKfigE0wBbpoq/p3kes6HGpyQt5NHK7HyUrbjq9GY4Y9sbU/OonmlwOIlUYD2eh3bKq9S7G7CaI lvc+7RvuJv6nqa8Gn1MSnzdmqAzb6v1S3fvSzpo62Yvhhqhdyqmo6091DhzwC7UMBRwy/UWEESKXD +hjh71RkhdYB7A==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1qvCwW-0004bP-5w; Tue, 24 Oct 2023 04:39:16 -0400 In-Reply-To: (Richard Stallman's message of "Mon, 23 Oct 2023 20:57:39 -0400") X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:311757 Archived-At: Hello Richard, Richard Stallman 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