From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: uzibalqa Newsgroups: gmane.emacs.help Subject: RE: [External] : Re: Add code from other files Date: Fri, 05 Jul 2024 19:59:59 +0000 Message-ID: References: <2fa9f251-0c84-46b5-9a88-b525eb79a413@starynkevitch.net> <_PaeWZsPmOkMG6EHs5Q_pGgCKfPN6KS5G97LT-TdrvMPSwG-KP24LmGkPsei8HjCBOai36qQUA5h-XeSeyQ2OoB49djwEFS5RjWzONWiAG4=@proton.me> <87sewplyk9.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17025"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Drew Adams , Emanuel Berg , "help-gnu-emacs@gnu.org" To: uzibalqa Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 05 22:01:14 2024 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 1sPp7K-0004FS-EJ for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 05 Jul 2024 22:01:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sPp6a-0007RB-Tm; Fri, 05 Jul 2024 16:00:28 -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 1sPp6N-0007JI-O6 for help-gnu-emacs@gnu.org; Fri, 05 Jul 2024 16:00:16 -0400 Original-Received: from mail-40132.protonmail.ch ([185.70.40.132]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sPp6H-0004Zx-4k for help-gnu-emacs@gnu.org; Fri, 05 Jul 2024 16:00:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=tkp7eja3qnhzhclzcgw4hvb4xu.protonmail; t=1720209603; x=1720468803; bh=72twnkmJXJbgy09Fy06k+8xOvDUqE4MZpwuVHai9Ndw=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=VgNQxS+d+SRZncnoSwY5mwFAYIF84v4NdhKHkN3iGrFWinGrvg8+MoGDWwQssdC95 iPNdOkipeHe8fGbs2nbJ8lobImNS283wl/ogbrtPTZH3kgmRZot5TpGK2EBK1H8Jlo mnQNoaz4xyscNVAMsl7X90pwVO+9DKMDfZlf2HFfxwKN/6MimM7sqT6+MiChXs8jsz AFbMBz1onQWKpsKM5+FwKuoi9h5k4N+EqCt7XkZx+A4MsxUKgoH/3yrn2MiIoJYLV7 qrVPbIZb4xY+Ro+VgUYeUGOe1ii/mkE3weZdD4J6T/W3YSckXtFDCql5XqBtjBd/gC JKQA4bszAvqzw== In-Reply-To: Feedback-ID: 52887082:user:proton X-Pm-Message-ID: b0d733d43368be199e885e48d6c4bd7bf5284a7c Received-SPF: pass client-ip=185.70.40.132; envelope-from=uzibalqa@proton.me; helo=mail-40132.protonmail.ch 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, TO_EQ_FM_DIRECT_MX=0.001, T_SPF_TEMPERROR=0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 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-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:147079 Archived-At: On Thursday, July 4th, 2024 at 11:20 PM, uzibalqa wrot= e: > On Thursday, July 4th, 2024 at 10:07 PM, uzibalqa uzibalqa@proton.me wrot= e: >=20 > > On Thursday, July 4th, 2024 at 9:32 PM, Drew Adams drew.adams@oracle.co= m wrote: > >=20 > > > > Use `provide' downmost in all your files, and whenever one function= is needed in some other file, you` require' that file > > > > first (topmost) in THAT file. > > > >=20 > > > > Is a good way to do it. > > > >=20 > > > > If you byte-compile it will tell you, if some file uses > > > > something not defined in that file, and also not require'd > > > > from another where it is. > > > >=20 > > > > So you can both find bugs that way and find out what needs to > > > > be required by what. > > >=20 > > > In addition, there's this case (not too common), > > > mentioned in (elisp) `Named Features': > > >=20 > > > Although top-level calls to 'require' are evaluated > > > during byte compilation, 'provide' calls are not. > > > Therefore, you can ensure that a file of definitions > > > is loaded before it is byte-compiled by including a > > > 'provide' followed by a 'require' for the same feature, > > > as in the following example. > > >=20 > > > (provide 'my-feature) ; Ignored by byte compiler, > > > ; evaluated by 'load'. > > > (require 'my-feature) ; Evaluated by byte compiler. > >=20 > > Please do not complicate my life. Do I really need to use this not too > > common case ? >=20 > Can someone explain to me why I should not use `load` ? What is load usef= ul for, > but not useful in my case ? >From what I could find, the 'require' function is generally preferred over= 'load'=20 to avoid duplicate loading. Still, the auxiliary files will only be used b= y the=20 master file and not in other places.