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 does byte-compile-file copy the input file to a different buffer? Date: Sun, 17 Dec 2023 18:37:52 +0000 Message-ID: References: <83cyv4kc67.fsf@gnu.org> <83bkaokasv.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="5159"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 17 19:38:41 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 1rEw2D-0001Bv-E6 for ged-emacs-devel@m.gmane-mx.org; Sun, 17 Dec 2023 19:38:41 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rEw1Y-0008Lx-Py; Sun, 17 Dec 2023 13:38:00 -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 1rEw1X-0008Lh-1I for emacs-devel@gnu.org; Sun, 17 Dec 2023 13:37:59 -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 1rEw1T-0003wz-Tx for emacs-devel@gnu.org; Sun, 17 Dec 2023 13:37:58 -0500 Original-Received: (qmail 32348 invoked by uid 3782); 17 Dec 2023 19:37:52 +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 19:37:52 +0100 Original-Received: (qmail 13964 invoked by uid 1000); 17 Dec 2023 18:37:52 -0000 Content-Disposition: inline In-Reply-To: <83bkaokasv.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: -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=unavailable 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:313940 Archived-At: Hello, Eli. On Sun, Dec 17, 2023 at 19:18:08 +0200, Eli Zaretskii wrote: > > Date: Sun, 17 Dec 2023 17:09:28 +0000 > > Cc: emacs-devel@gnu.org > > From: Alan Mackenzie > > > The command uses insert-file-contents to insert the file into the > > > input buffer, and works on that, so that looks very natural to me. > > > I'm not sure what is bothering you in that, or why. > > >From inside the reader, the buffer " *Compiler Input*" is effectively > > anonymous: it gives no clue as to what the actual file or buffer is. > This doesn't appear to be true, since byte-compile-file binds > buffer-file-name to the name of the file whose contents it inserted. > It does that only temporarily, for calling normal-mode, but maybe we > could just do that for the entire duration of the compilation. > > All I want is the name of the real buffer, or failing that, the name of > > the real file. When the reader sees " *Compiler Input*" does it have to > > assume that byte-compile-current-file is bound and use that? Even > > recognising " *Compiler Input*-1" in C code is difficult - there're no > > string functions in Emacs which can test that a given string is a prefix > > of another string. There's string-match, but it only works with a > > regular expression, not a plain string. By the time I put that sort of > > code into a C routine, it is so bulky, it drowns out the prime purpose > > of the routine. > > It's difficult. > If all you need is to have buffer-file-name set to the file's name, I > think that can be arranged relatively easily. I've worked out what I need. And that's to be able to identify the text source of a call to the reader on the basis of the parameter STREAM (also know as READCHARFUN). I put a printf into one of read's subroutines, printing out the buffer name for each call where STREAM was a buffer. All it output was *load* and *Compiler Input*. :-( It's all very well binding buffer-file-name for some reader calls, but then for other reader calls it will be load-file-name, and I'd be surprised if there weren't more dynamic variables holding file and buffer names which would need to be examined. If we're loading or compiling a .el file, and it gets fetched into a buffer for that purpose, why can't that buffer be called "bytecomp.el" (or even "bytecomp.el<2>"), rather than "*load*" or " *Compiler Input*"? That way, the source for the read operation would be identified by the buffer name. -- Alan Mackenzie (Nuremberg, Germany).