From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 281 invoked from network); 27 Mar 1997 18:18:40 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by coral.primenet.com.au with SMTP; 27 Mar 1997 18:18:40 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id NAA09792; Thu, 27 Mar 1997 13:12:44 -0500 (EST) Resent-Date: Thu, 27 Mar 1997 13:12:44 -0500 (EST) To: Zefram Cc: zsh-workers@math.gatech.edu Subject: Re: ksh autoloading References: <11717.199703261746@stone.dcs.warwick.ac.uk> From: Roderick Schertler Date: 27 Mar 1997 13:15:19 -0500 Message-ID: Resent-Message-ID: <"wnvES3.0.xO2.RYhEp"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3039 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu On Wed, 26 Mar 1997 17:46:21 GMT, Zefram said: > > The new scheme is that when a list has been read from the file and parsed, > it is examined to see if it is *in its entirety* a definition of the > function being loaded. If it is, then the contents of that definition > is used, rather than the complete list. This has much better defined > semantics than the old method. One of the nicest things about the ksh semantics are that you can define the function plus run some initialization code. It sounds like your patch will disallow that. -- Roderick Schertler roderick@argon.org