Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Modules dependencies RE: PATCH: zftp/tcp abstraction

X-seq: zsh-workers 15126
From: Clint Adams <clint@xxxxxxx>
To: zsh-workers@xxxxxxxxxx
Subject: Re: Modules dependencies RE: PATCH: zftp/tcp abstraction
Date: Wed, 27 Jun 2001 09:49:28 -0400
In-reply-to: <001301c0fe32$e11f5200$21c9ca95@xxxxxxxxxxxxxx>; from Andrej.Borsenkow@xxxxxxxxxxxxxx on Tue, Jun 26, 2001 at 03:26:44PM +0400
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <001301c0fe32$e11f5200$21c9ca95@xxxxxxxxxxxxxx> <1010626163333.ZM3779@xxxxxxxxxxxxxxxxxxxxxxx> <E157wrq-0005Ck-00@xxxxxxxxxxxxx> <001301c0fe32$e11f5200$21c9ca95@xxxxxxxxxxxxxx>

AB> - module is represented by its module definition file. It is basically mdd
AB> file with all makefile fragments stripped and any shell code replaced by

BS> Why can't the module definition file itself be a loadable module?

What about just embedding the module dependencies in the module itself?
If it could be scanned without loading the module, it would be less
messy than maintaining "helper files".  Otherwise, couldn't one
load the module, check the dependency symbol, then unload the module
and do things in the correct order?

Follow-Ups:
- Re: Modules dependencies RE: PATCH: zftp/tcp abstraction
  - From: Peter Stephenson

References:
- RE: Modules dependencies RE: PATCH: zftp/tcp abstraction
  - From: Andrej Borsenkow
- Re: Modules dependencies RE: PATCH: zftp/tcp abstraction
  - From: Bart Schaefer
- Re: Modules dependencies RE: PATCH: zftp/tcp abstraction
  - From: Zefram

Messages sorted by: Reverse Date, Date, Thread, Author