From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: [External] : Emacs object type hierarchy Date: Mon, 23 Oct 2023 20:57:39 -0400 Message-ID: References: Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7616"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acorallo@gnu.org, emacs-devel@gnu.org To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 24 02:58:05 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 1qv5kD-0001k8-8M for ged-emacs-devel@m.gmane-mx.org; Tue, 24 Oct 2023 02:58:05 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qv5jq-00019p-Kh; Mon, 23 Oct 2023 20:57:42 -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 1qv5jp-00018c-Aa for emacs-devel@gnu.org; Mon, 23 Oct 2023 20:57:41 -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 1qv5jo-0000lp-OC; Mon, 23 Oct 2023 20:57:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=mjRs5BP+FsOZteZnpb8vedv3YhQG8xp2oAsEeCUjKbg=; b=MgDxW1t7kooQ B2oqfrLV1CHpH0JrnHD9Fata9p6i2e3zfhSKAczzjTAB6zRA83qhPholBXNHX32rSxnFizZIRU0YT yf4KLkgyhk7ae9fMSspvWU0/imyu/B82XJpBMbWTWrTMrUgIA2HKvnHrs86xKm0dMvUxtcHAz+CFg DcJ0xFDVfz1y1by69sBcDhmrO1R/AvfX1TDdpaIfQMoZNcxH6x2khV4n7lP90+VN1ca+3elXpgZzc EUhm3/Kux2gLxshXnc6aNmhdS+JK6Sv9nIFdLJrBrUYffM0lsZGfa08DhJP4iXpVeTITe0+DspL7s yXCRET68nhtB3iDhC5hTQg==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1qv5jn-0002UA-4h; Mon, 23 Oct 2023 20:57:39 -0400 In-Reply-To: (message from Drew Adams on Sun, 22 Oct 2023 16:11:00 +0000) 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:311735 Archived-At: [[[ 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.) If not, do we want to? What would would that involve? 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? -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)