From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: Re: Shrinking the C core Date: Sat, 12 Aug 2023 05:22:45 +0200 Message-ID: <87fs4pkkqi.fsf@dataswamp.org> References: <20230809094655.793FC18A4654@snark.thyrsus.com> <87il9owg0f.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10635"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:09yPNlHLWgDN/wsdYwT/n95DCK8= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 12 07:28:48 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 1qUhBA-0002Ye-Jh for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Aug 2023 07:28:48 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qUhAn-0008Pl-8f; Sat, 12 Aug 2023 01:28:25 -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 1qUfDM-0004fw-LE for emacs-devel@gnu.org; Fri, 11 Aug 2023 23:22:56 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qUfDL-0004Pr-1x for emacs-devel@gnu.org; Fri, 11 Aug 2023 23:22:56 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qUfDI-0005cc-K3 for emacs-devel@gnu.org; Sat, 12 Aug 2023 05:22:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sat, 12 Aug 2023 01:28:24 -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:308602 Archived-At: Richard Stallman wrote: > There are occasiona when it is useful, for added > flexibility, to move some function from C to Lisp. However, > stability is an important goal for Emacs, so we should not > even try to move large amounts of code to Lisp just for the > sake of moving code to Lisp. It is just cool that Emacs is written in two languages, it is like to continents or something connected by bridges overlapping certain areas. Maybe we can use SBCL to compile Elisp, and after that integrate it into Emacs so you would be able to run all old Elisp without changing the code, only now it would in fact be Common Lisp implementing Elisp, i.e. the opposite of our cl-lib (`cl-loop' etc). Maybe some normalization efforts would have to be done to the syntax here and there as preparatory steps ... -- underground experts united https://dataswamp.org/~incal