Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!batcomputer!riley
From: riley@batcomputer.tn.cornell.edu (Daniel S. Riley)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Execute strangeness
Message-ID: <6203@batcomputer.tn.cornell.edu>
Date: 4 Sep 88 15:12:16 GMT
References: <3823@polya.Stanford.EDU>
Reply-To: riley@tcgould.tn.cornell.edu (Daniel S. Riley)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 25

In article <3823@polya.Stanford.EDU> rokicki@polya.Stanford.EDU (Tomas G. Rokicki) writes:
>Can anyone explain why:
>
>The file asdf is:  delete asdf
>
>If you type `execute asdf', it bitches; file in use.  *But*, if
>The file testit is:  execute asdf
>and asdf is as above, the delete works?  

Nested executes are handled (for reasons beyond my ken) by creating a
temporary file, same as script files with .key's are.  Once the temp
file is created, the original file being executed is released, and can be
deleted.  If the file asdf contains

.key junk
delete asdf

it works.

>Can I count on this to continue to work?  Thanks!

dunno.  Seems like it should work at lesat until someone rewrites execute...

-dan riley (dsr@lns61.tn.cornell.edu, dsr@crnlns.bitnet)
-wilson lab, cornell u.