Xref: utzoo comp.sys.amiga:22471 comp.sys.amiga.tech:1716
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!oliveb!amiga!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Execute strangeness
Message-ID: <4661@cbmvax.UUCP>
Date: 4 Sep 88 21:19:52 GMT
References: <3823@polya.Stanford.EDU>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 24

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?  Can I count on this to
>continue to work?  Thanks!

	Whenever you execute a file from within an execute script, it doesn't
actually run out of the file, but out of t:Command-xx-Tyy, where xx and yy
are numbers.

	If possible, I would avoid counting on the exact interactions of this.
It might work differently if someone replaces the resident CLI with a shell
that handles Execute internally, for example.

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup