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: Wed, 23 Aug 2023 01:55:21 +0200 Message-ID: <87sf8a7hue.fsf@dataswamp.org> References: <20230809094655.793FC18A4654@snark.thyrsus.com> <87fs4pkkqi.fsf@dataswamp.org> <87jztzkgct.fsf@dataswamp.org> <87y1if8j8t.fsf@linux-m68k.org> <87y1ifi9fv.fsf@dataswamp.org> <87zg2uqdmv.fsf@localhost> <87edk3gbh3.fsf@dataswamp.org> <87jztvnuyb.fsf@localhost> <875y5bdutt.fsf@dataswamp.org> <87y1i6e1uh.fsf@localhost> <874jkub40o.fsf@dataswamp.org> <87jztqdw2l.fsf@localhost> <87msym9i4r.fsf@dataswamp.org> <87a5ula1zt.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17835"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:29lblPKUzlsE3NdLBpI953se1Ug= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 23 04:24:51 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 1qYdYB-0004LI-G2 for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Aug 2023 04:24:51 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qYdXX-0002ZQ-5B; Tue, 22 Aug 2023 22:24:11 -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 1qYbDr-0002zF-Gd for emacs-devel@gnu.org; Tue, 22 Aug 2023 19:55:43 -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 1qYbDo-0001xl-S7 for emacs-devel@gnu.org; Tue, 22 Aug 2023 19:55:43 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qYbDk-0008sy-KI for emacs-devel@gnu.org; Wed, 23 Aug 2023 01:55:36 +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: Tue, 22 Aug 2023 22:24:09 -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:309121 Archived-At: Alfred M. Szmidt wrote: >>> Please keep the CC intact, not everyone subscribed. >> >> Yes, that is some Gnus configuration "ghost" I must have >> done, several people have pointed it out, but I have been >> unable to locate it - so far. > > I suppose that is also why I get a bounce from you? No, that is something else, and only happens on MLs. In ~/.fdm.conf I have a line like this match case "emacs-devel@gnu.org" in headers action "drop" I put it there since I read those messages with Gnus and Gmane, thus can dispose of the e-mails copies saying the same thing - maybe that is what is causing the failure delivery messages. Let's comment it out then and see if it helps. > That is not the meaning of dynamically or statically typed. > Statically typed languages you know every type at compile > time, in a dynamically typed language you have no clue about > it either at compile time or run time. The article in > question claims that Lisp is statically typed, which is > a total misunderstanding of the term. > >> That would be really nice to have BTW, are you saying that >> isn't possible with Lisp? Why not? > > Because you literally always have to check the type, even > with a declare/declaim you are allowed to pass garbage. > The compiler can produce a warning, but it isn't an error in > Lisp, while it is an error in a statically typed language > already at compile time. In Lisp you never know the types > of things. In C types are explicit in the source and in SML the types of everything, including functions and by extention combinations of functions, can be inferred, so that the type of a function to add two integers is described as a mapping from integer, integer to another integer. Those methods cannot be used to get a statically typed Lisp? Why not? Because of the Lisp syntax? -- underground experts united https://dataswamp.org/~incal