From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: Why shouldn't we have a #if .... #else .... #endif construct in Emacs Lisp? Date: Sun, 3 Sep 2023 13:24:53 +0000 Message-ID: References: <834jkca9k0.fsf@gnu.org> <83r0nf98be.fsf@gnu.org> <83sf7v7c4l.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27697"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefankangas@gmail.com, emacs-devel@gnu.org, mattiase@acm.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Sep 03 15:25:30 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 1qcn6X-0006zF-E7 for ged-emacs-devel@m.gmane-mx.org; Sun, 03 Sep 2023 15:25:29 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qcn65-0008HL-Rj; Sun, 03 Sep 2023 09:25:01 -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 1qcn64-0008H9-1L for emacs-devel@gnu.org; Sun, 03 Sep 2023 09:25:00 -0400 Original-Received: from mail.muc.de ([193.149.48.3]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qcn61-0000AU-2Q for emacs-devel@gnu.org; Sun, 03 Sep 2023 09:24:59 -0400 Original-Received: (qmail 70460 invoked by uid 3782); 3 Sep 2023 15:24:54 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=muc.de; i=@muc.de; q=dns/txt; s=default; t=1693747494; h=date : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to : from : from; bh=xe5z6Hmq7+/xy24mcqneFUbxikwGqsNX19630SZaJt4=; b=mOeqJNu6zCyyXQgK5uDHt2Kcpp5m9cMaoyeB70GmZ82z2itLVMefSuqG/9V7ZGybSquhA 0qU2SrwMsK1K/ErHmyusJ2yFdNhjkmt/MpZkfT/2wsd1Uery0u+h1VEdEd5DJOUMQG7x5Lm jsxpIcIXCMxwQ0a9dzQw90Ibukhxx5rMIROFqxzvo3r/0z1mDZCh75/2FP6qFvWD6sWboVK mihDY5YFObyO84KyCOW8mith3tVDPeN6zlcYKftpkoHPF2k8TX05xTjnfmpWzr3LVHKVudk SDWyX+yf2JtFrFHSbT9cBjXIoQCSEmkgs4tCEMwzgkGwRfAr0a+lwyvcHKIQ== Original-Received: from acm.muc.de (p4fe157eb.dip0.t-ipconnect.de [79.225.87.235]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 03 Sep 2023 15:24:53 +0200 Original-Received: (qmail 25226 invoked by uid 1000); 3 Sep 2023 13:24:53 -0000 Content-Disposition: inline In-Reply-To: <83sf7v7c4l.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.3; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:309974 Archived-At: Hello, Eli. On Sun, Sep 03, 2023 at 14:02:50 +0300, Eli Zaretskii wrote: > > Date: Sun, 3 Sep 2023 10:48:50 +0000 > > Cc: stefankangas@gmail.com, emacs-devel@gnu.org, mattiase@acm.org > > From: Alan Mackenzie [ .... ] > > > What is "interpreted compilation" in Emacs? I'm aware of only two > > > compilers in Emacs: the byte compiler and the native compiler. So > > > when you talk about "the compiler" above, what does that allude to? > > I mean the defmacro and defun macros, particularly when invoked by C-M-x, > > etc. Do we have a generic term for these, regardless of whether they are > > called interpretatively or in the context of byte/native compilation? > "Evaluation"? That's not quite there, I don't think. We really want a word which denotes the setting of a symbol's function cell starting off with a "source" form. I'm afraid I forgot to amend the NEWS entry I've just committed. I'll think about that a little more. [ .... ] > > I have proposed catching this error with a condition-case and in the > > handler, calling eval again with just one argument. > > The other party in the email has opined that static-if should not contain > > this condition-case mechanism, and anybody writing for such an old Emacs > > should make their own adjustments. > I tend to agree with "the other party", FWIW. It's worth a lot. I've taken the condition-case mechanism out. I would also be closing the bug, were this a thread on the bug list. ;-) -- Alan Mackenzie (Nuremberg, Germany).