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: Why does byte-compile-file copy the input file to a different buffer? Date: Sun, 17 Dec 2023 16:06:44 +0000 Message-ID: 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="39732"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 17 17:07:55 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 1rEtgI-000A9V-By for ged-emacs-devel@m.gmane-mx.org; Sun, 17 Dec 2023 17:07:54 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rEtfY-0005uD-K7; Sun, 17 Dec 2023 11:07:08 -0500 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 1rEtfV-0005u1-07 for emacs-devel@gnu.org; Sun, 17 Dec 2023 11:07:05 -0500 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 1rEtfR-0000Op-Qf for emacs-devel@gnu.org; Sun, 17 Dec 2023 11:07:03 -0500 Original-Received: (qmail 59731 invoked by uid 3782); 17 Dec 2023 17:06:45 +0100 Original-Received: from acm.muc.de (p4fe15b7c.dip0.t-ipconnect.de [79.225.91.124]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 17 Dec 2023 17:06:44 +0100 Original-Received: (qmail 2070 invoked by uid 1000); 17 Dec 2023 16:06:44 -0000 Content-Disposition: inline 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: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 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:313930 Archived-At: Hello, Emacs. On executing a byte-compile-file command, rather than working on the file's buffer directly, the byte compiler first copies the buffer/file into another buffer with a boring name like " *Compiler Input*" or " *Compiler Input*-1". Why does it do this? It makes it difficult, in the reader, to determine the identity of the actual source buffer. (Yes, I have reasons for wanting to do this.) Would it not be simpler just to compile directly from the source buffer, thus avoiding a needless copying and making it clear what the actual source buffer is? -- Alan Mackenzie (Nuremberg, Germany).