From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lute Kamstra Newsgroups: gmane.emacs.devel Subject: Re: Removing unloaded functions from auto-mode-alist. Date: Sun, 24 Apr 2005 22:52:36 +0200 Message-ID: <87wtqraodn.fsf@xs4all.nl> References: <87zmvu6ba2.fsf@xs4all.nl> <85ll7e68ei.fsf@lola.goethe.zz> <854qe2ihhi.fsf@lola.goethe.zz> <8764yi4awh.fsf@xs4all.nl> <873btlsalu.fsf@xs4all.nl> <87pswo84vv.fsf@xs4all.nl> <857jiucz6r.fsf@lola.goethe.zz> <87oec5p5rq.fsf@xs4all.nl> <85fyxhcff8.fsf@lola.goethe.zz> <87ekd0apu8.fsf@xs4all.nl> <85oec3rk50.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1114375866 12432 80.91.229.2 (24 Apr 2005 20:51:06 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 24 Apr 2005 20:51:06 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 24 22:51:03 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DPo3V-00069c-T8 for ged-emacs-devel@m.gmane.org; Sun, 24 Apr 2005 22:50:18 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DPo8t-0002M1-WD for ged-emacs-devel@m.gmane.org; Sun, 24 Apr 2005 16:55:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DPo8U-0002Dh-PB for emacs-devel@gnu.org; Sun, 24 Apr 2005 16:55:26 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DPo8T-0002Co-4p for emacs-devel@gnu.org; Sun, 24 Apr 2005 16:55:26 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DPo8T-0001uL-16 for emacs-devel@gnu.org; Sun, 24 Apr 2005 16:55:25 -0400 Original-Received: from [194.109.24.35] (helo=smtp-vbr15.xs4all.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DPo9H-00046P-Jw; Sun, 24 Apr 2005 16:56:15 -0400 Original-Received: from pijl (a80-127-67-124.adsl.xs4all.nl [80.127.67.124]) by smtp-vbr15.xs4all.nl (8.12.11/8.12.11) with ESMTP id j3OKqbAZ068741; Sun, 24 Apr 2005 22:52:37 +0200 (CEST) (envelope-from Lute.Kamstra@xs4all.nl) Original-Received: from lute by pijl with local (Exim 3.36 #1 (Debian)) id 1DPo5k-0001jr-00; Sun, 24 Apr 2005 22:52:36 +0200 Original-To: David Kastrup In-Reply-To: <85oec3rk50.fsf@lola.goethe.zz> (David Kastrup's message of "Sun, 24 Apr 2005 22:32:11 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) Original-Lines: 38 X-Virus-Scanned: by XS4ALL Virus Scanner X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:36341 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:36341 David Kastrup writes: > Lute Kamstra writes: > >> David Kastrup writes: >> >> [...] >> >>> Well, the idea explored a bit later later was that "load" will >>> record autoloads, but not do anything with them by itself, instead >>> letting "provide" handle it. >> >> Ah, now I understand your post. I think letting provide record >> autoloads is a bad idea. provide can occur anywhere in a file. So >> when provide records autoloads it won't record the autoloads that >> get replaced after that position. > > No, the idea was that load initiates the recording of autoload data > alright, but will throw the recorded data away at the end of the load > unless a `provide' occured at its top level. If the provide occured > at the top level of the load, then the end of the load will tag all > the functions with the autoload data, like do_autoload does now at the > end of its load sequence. > > So the "provide" merely sets a flag, and this flag causes the > encompassing load not to throw the collected previous autoload data > away at the end of the load sequence, but use it for marking the > changed functions with the old autoloads in their properties. > > Clearer now? Yup. (I hope so. ;-)) But you want that autoloads are recorded in Fload, after loading the file is complete, right? That would be a complicated change, best done after the release. Lute.