Re: Is GILD broken?

On 11/10/2001 1:07 AM Rick VanNorman wrote:

> Yes, there is a problem with the sequence. It is one that I haven't been
> able to resolve. Here is the issue:
>
> When the file is included, the GILD inside a file performs the
> closure of the wordlists. Then, after this closure, the INCLUDE completes
> and returns to the command interpreter. At that point, the include
> mechanism writes the filename to a specialized wordlist so that
> the LOCATE mechanism works. Notice that this happes *after* the
> GILD. Now, back in the command interpreter, you execute EMPTY,
> the filename goes away, and things get funny with the interpreter.
> It may seem simple to fix, but I haven't figured out how.
>
> Hope the explanation helps. Sorry there's not a better answer.

Thanks for the clear explanation. I've simply changed my
4nt script to:

   sf=c:\util\SwiftForth\bin\sf requires stuff gild

and I can now 'edit' my own definitions even after 'empty'.

Thanks,

Bill

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe sftalk" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/sftalk -- check them out!
Search the archives! Visit http://www.forth.com/search for details.
Received on Fri Nov 09 2001 - 22:23:40 PST