From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: weird byte compile message when using (when t ... ) Date: Fri, 12 Feb 2021 09:17:50 -0500 Message-ID: References: <87tuqhbfbh.fsf@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39878"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:RwvJ9/CQhZC/RG5DIdgLhCjbblQ= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Feb 12 15:18:37 2021 Return-path: Envelope-to: geh-help-gnu-emacs@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 1lAZHH-000AEm-BB for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 12 Feb 2021 15:18:35 +0100 Original-Received: from localhost ([::1]:37152 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lAZHG-0006wb-Dh for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 12 Feb 2021 09:18:34 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57336) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lAZGj-0006wP-RX for help-gnu-emacs@gnu.org; Fri, 12 Feb 2021 09:18:01 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:53024) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lAZGi-0000iB-9H for help-gnu-emacs@gnu.org; Fri, 12 Feb 2021 09:18:01 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1lAZGf-0009WH-Ff for help-gnu-emacs@gnu.org; Fri, 12 Feb 2021 15:17:57 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@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-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:127853 Archived-At: > When I enclose .emacs [1] in (when t ... ) or > (if t (progn ... )) the following what I can see (?) incorrect > warnings are reported The byte-compiler treats code differently if it's a "toplevel" or not (where "toplevel" either literally means "not nested inside anything else" or "nested inside a `progn` (or something that expands to one) that is a toplevel"). E.g. of things this affect: - a function definition that's not at toplevel will not be considered as defined when compiling the current file. - a `require` that's not at toplevel will not be executed during compile time. - a `defmacro` that's not at toplevel will not be available for expansion of macros within the same file. - ... So that can make big differences to warnings (and more). This can be used on purpose, of course, such as using `(if t (require 'foo))` to make sure `foo` is only required when the file is loaded, so that compilation of the file will not fail just because `foo` is missing. Stefan