From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.help Subject: Re: (require ...) and file dependencies. Date: Sun, 28 Dec 2014 02:09:27 +0200 Message-ID: <549F4A37.1040504@yandex.ru> References: <87iogwd5h8.fsf@gavenkoa.example.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1419725404 26326 80.91.229.3 (28 Dec 2014 00:10:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 28 Dec 2014 00:10:04 +0000 (UTC) To: Oleksandr Gavenko , help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Dec 28 01:09:57 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Y51Qh-0003ou-EB for geh-help-gnu-emacs@m.gmane.org; Sun, 28 Dec 2014 01:09:55 +0100 Original-Received: from localhost ([::1]:57178 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y51Qg-0008Eg-KO for geh-help-gnu-emacs@m.gmane.org; Sat, 27 Dec 2014 19:09:54 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42456) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y51QV-0008Eb-PI for help-gnu-emacs@gnu.org; Sat, 27 Dec 2014 19:09:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y51QQ-0000cc-R3 for help-gnu-emacs@gnu.org; Sat, 27 Dec 2014 19:09:43 -0500 Original-Received: from mail-wg0-x22e.google.com ([2a00:1450:400c:c00::22e]:52026) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y51QQ-0000cM-J2 for help-gnu-emacs@gnu.org; Sat, 27 Dec 2014 19:09:38 -0500 Original-Received: by mail-wg0-f46.google.com with SMTP id x13so16529624wgg.19 for ; Sat, 27 Dec 2014 16:09:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=npxXD+LqMhS8NSUCwsM3x/gNtZRvHk6LboL/2cP56WE=; b=bFwDzGDBJMbI1VWzyhqYv2Lg/SnhIb0Fwq1pJWq3fKO/YX6RzqSjQh412Qc3vGSE5v tT3cNuK1C/gPuwtWYy+C5DdTNh1IOrl8TGhvQ7kXdv23ncjfHiHftQjzIjJqwofGqyMA YccWR5iseZYh7rfW4sEkJGcb6bx2c6KwsdM/cGCb+HISTCPs65UkNlZAyHMDftdsKwlt y+ir33j+hakNVfjy0viy/yRRwaY08sPJv7hCspy9ODRZZBan5w/Z0Z5qM5rDNu5wEqIZ RxNljrbTxluUsffarP3M5XgJfMrg7HJLcUEX8kPpnHDAGY8pSD8a95q/4DAt19u14aDt YUtA== X-Received: by 10.180.76.144 with SMTP id k16mr80338940wiw.3.1419725376963; Sat, 27 Dec 2014 16:09:36 -0800 (PST) Original-Received: from [192.168.1.3] ([82.102.93.54]) by mx.google.com with ESMTPSA id ej10sm33550705wib.2.2014.12.27.16.09.33 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 27 Dec 2014 16:09:36 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Thunderbird/33.0 In-Reply-To: <87iogwd5h8.fsf@gavenkoa.example.com> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:101737 Archived-At: On 12/28/2014 01:42 AM, Oleksandr Gavenko wrote: > But what to do with: > > Warning: the function `...' is not known to be defined. > > I have: > > xxx-mode.el > xxx-update.el > > and both files mix uses of variables and functions. "xxx-mode.el" have > > (require 'xxx-update) > > and designed to be loaded by user. So "xxx-update.el" can't use > > (require 'xxx-mode) > > or you get: > > Error: Recursive `require' for feature `xxx-mode' You can use `declare-function' in this case. And then make sure than the other package is actually loaded at runtime. > Seems that proper way to fix issue is by rearranging dependency hierarchy by > breaking dependency cycles, isn't? That would be even better, of course.