From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21801 invoked from network); 2 Jun 2000 14:25:21 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Jun 2000 14:25:21 -0000 Received: (qmail 14336 invoked by alias); 2 Jun 2000 14:25:09 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11728 Received: (qmail 14327 invoked from network); 2 Jun 2000 14:25:09 -0000 Date: Fri, 02 Jun 2000 15:24:41 +0100 From: Peter Stephenson Subject: Re: Use and abuse of dynamic loading RE: Getting dynamic loading to work on cygwin In-reply-to: "Your message of Fri, 02 Jun 2000 18:11:14 +0400." <000001bfcc9c$697939a0$21c9ca95@mow.siemens.ru> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0FVJ00HC06P518@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT > Consider Perl or Tcl where you compile and install modules > independently of main program. But this is exactly what Zsh lacks (just > think about autoloading - all information is compiled into main > executable, so if I want another module be autoloaded I need to > recompile zsh). I don't know what you mean by this. In perl, you use `use Module' to include a module, which may have compiled data, and may have autoload capability. In zsh, you use `zmodload -ab foo' and its friends to specify that foo is loadable from a module; you don't need to recompile to do that. What's the difference? Do you mean that zsh doesn't come with a separate kit to allow you to compile new modules without the original compilation environment? -- Peter Stephenson Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070