From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8507 invoked from network); 25 Feb 2000 09:44:32 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 25 Feb 2000 09:44:32 -0000 Received: (qmail 4843 invoked by alias); 25 Feb 2000 09:44:24 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9872 Received: (qmail 4827 invoked from network); 25 Feb 2000 09:44:17 -0000 From: "Bart Schaefer" Message-Id: <1000225094411.ZM22302@candle.brasslantern.com> Date: Fri, 25 Feb 2000 09:44:11 +0000 In-Reply-To: <200002250841.JAA25219@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: PATCH: parser (was: Re: PATCH: Improved _mailboxes)" (Feb 25, 9:41am) References: <200002250841.JAA25219@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Precompiled wordcode zsh functions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Feb 25, 9:41am, Sven Wischnowsky wrote: } Subject: Re: PATCH: parser (was: Re: PATCH: Improved _mailboxes) } } > Let's stick with autoload and have a file suffix convention, like } > emacs' .el and .elc, or something. Heck, there could even be } > separate fpath and compiled_fpath or ... } } I was wondering what to do when the directory isn't writable... but a } $COMPILED_FPATH containing one directory would be enough. There need to be at least two directories, one for the users' personal functions and one for the .../share/zsh/$ZSH_VERSION/functions/... set. You can't expect everyone to keep their own compiled copies of the base function library, surely? } Hm. Do you want to say that you actually like the idea? Me? I don't really care one way or the other, except that I want to see it done right if it's going to be done. } [...] we would need to have a wordcode-verifier [...] How does emacs assure the integrity of .elc files? Or does it? } That's yet another reason for having only a scalar containing } only one directory name (so $COMPILED_FDIR might be a better name) -- } save compiled functions only if that is set and names an existing, } writable directory. Users would set it to a directory in their account } so that others can't trick them into using evil code. Zsh should probably already be more paranoid than it is about loading modules or functions from widely-writable directories or files. But that has nothing to do with how many such directories or files are involved. Where does "save compiled functions" come in? I'd think we'd want an explicit "zcompile" builtin so functions can selectively be compiled or not. I don't want it just automatically writing out wordcode for every function it ever loads. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com