From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28758 invoked from network); 7 Jun 2001 10:01:17 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 7 Jun 2001 10:01:17 -0000 Received: (qmail 27172 invoked by alias); 7 Jun 2001 10:00:58 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14785 Received: (qmail 27153 invoked from network); 7 Jun 2001 10:00:58 -0000 Message-ID: To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: Modules dependencies RE: PATCH: zftp/tcp abstraction In-reply-to: ""Andrej Borsenkow""'s message of "Thu, 07 Jun 2001 13:41:10 +0400." <000701c0ef35$fc04ebe0$21c9ca95@mow.siemens.ru> Date: Thu, 07 Jun 2001 11:00:43 +0100 From: Peter Stephenson "Andrej Borsenkow" wrote: > Index: Src/Modules/zftp.mdd > +moddeps="zsh/net/tcp" > > The problem is, it is currently ignored for modules without auto stuff. > Dependencies are put only in main zsh in Src/bltinmods.list. > > To make it work in general every module needs a standard function, let's > call it dep_, that is autogenerated out of moddeps and called before module > is attempted to be loaded to register dependencies. We may need the > counterpart to remove dependencies when module is unloaded (seems > reasonable). Yes, possibly we should distinguish explicitly by checks in module.c between modules which provide features directly (builtins, parameters, etc.) and those which only exist as a dependency to provide support for other modules. Then we can tell what it's safe to unload. Currently modules are either one or the other --- maybe we can get away with keeping it like this. -- Peter Stephenson Software Engineer CSR Ltd., Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070 ********************************************************************** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. **********************************************************************