From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17863 invoked from network); 2 May 1999 16:35:01 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 May 1999 16:35:01 -0000 Received: (qmail 27414 invoked by alias); 2 May 1999 16:34:52 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6183 Received: (qmail 27407 invoked from network); 2 May 1999 16:34:50 -0000 From: "Bart Schaefer" Message-Id: <990502093405.ZM7542@candle.brasslantern.com> Date: Sun, 2 May 1999 09:34:05 -0700 X-Mailer: Z-Mail (4.0b.820 20aug96) To: zsh-workers@sunsite.auc.dk Subject: zmodload -C ?? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In making up the patch for the zmodload changes I suggested a few days ago, I ran across code that appears to accept a -C option ... but it's not listed in the builtin.c definition of the zmodload call signature, so AFAIK it can't ever actually be passed to bin_zmodload(). I've forgotten what it was for (if it ever was for anything) and the only effect it seems to have is to behave almost-but-not-quite the same as -c. Should I just delete it? -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com