wip(n) | Word Interpreter | wip(n) |
wip - Word Interpreter
package require Tcl 8.4
package require wip ?2.2?
package require snit ?1.3?
package require struct::set
::wip wipName engine arg...
def name
def name method_prefix
wipName option ?arg arg ...?
wip::dsl ?suffix?
wipName def name ?method_prefix?
wipName defl names
wipName defd dict
wipName deflva name...
wipName defdva (name method_prefix)...
wipName undefl names
wipName undefva name...
wipName unknown cmdprefix
wipName runl wordlist
wipName run word...
wipName run_next
wipName run_next_while acceptable
wipName run_next_until rejected
wipName run_next_if acceptable
wipName run_next_ifnot rejected
wipName next
wipName peek
wipName peekall
wipName insertl at wordlist
wipName replacel wordlist
wipName pushl wordlist
wipName addl wordlist
wipName insert at word...
wipName replace word...
wipName push word...
wipName add word...
This package provides a micro interpreter for lists of words. Domain specific languages based on this will have a bit of a Forth feel, with the input stream segmented into words and any other structuring left to whatever the language desired. Note that we have here in essence only the core dispatch loop, and no actual commands whatsoever, making this definitely only a Forth feel and not an actual Forth.
The idea is derived from Colin McCormack's treeql processor, modified to require less boiler plate within the command implementations, at the expense of, likely, execution speed. In addition the interface between processor core and commands is more complex too.
Word interpreters have a mappping from the names of the language commands they shall recognize to the methods in the engine to invoke for them, and possibly fixed arguments for these methods. This mapping is largely static, however it is possible to change it during the execution of a word list (= program).
At the time a language command is defined the word interpreter will use snit's introspection capabilities to determine the number of arguments expected by the method of the egnine, and together with the number of fixed arguments supplied in the method prefix of the mapping it then knows how many arguments the language command is expecting. This is the command's arity. Variable-argument methods (i.e. with the last argument named args) are not allowed and will cause the word interpreter to throw an error at definition time.
Note that while I said snit's abilities the engine object can be written in any way, as long as it understands the method info args, which takes a method name and returns the list of arguments for that method.
When executing a list of words (aka program) the first word is always taken as the name of a language command, and the next words as its arguments, per the arity of the command. Command and argument words are removed from the list and then associated method of the engine is executed with the argument words. The process then repeats using the then-first word of the list.
Note that the methods implementing the language commands may have full access to the list of words and are allowed to manipulate as they see fit.
The main command of the package is:
The engine is the object the word interpreter will dispatch all recognized commands to, and the arguments are a word list which defines an initial mapping from language words to engine methods.
The recognized language of this word list is
The returned command may be used to invoke various operations on the object. It has the following general form:
The package additionally exports the command:
It installs a component named wip, and a method wip_setup for initializing it. This method has to be called from within the constructor of the type using the word interpreter. If further installs a series of procedures which make the object API of the word interpreter directly available to the type's methods, without having to specify the component.
Note that this does and cannot install the language to interpret, i.e. the mapping from words to engine methods.
It is possible to instantiate multiple word interpreter components within a type by using different suffices as arguments to the command. In that case the name of the component changes to ´wip_$suffix', the setup command becomes ´wip_$suffix_setup' and all the procedures also get the suffix ´_$suffix'.
The following commands are possible for word interpreter objects:
The wordlist is stored in the object for access by the other run-methods, and the general program accessor methods (see below). A previously stored wordlist is saved during the execution of this method and restored before it returns. This enables the recursive execution of word lists within word lists.
Exposed for use within command implementations. The methods run and runl use it to execute words until their word list is exhausted.
Exposed for use within command implementations to change the order of execution.
Exposed for use within command implementations to change the order of execution.
Exposed for use within command implementations to change the order of execution.
Exposed for use within command implementations to change the order of execution.
$wip insertl 0 $wordlist
$wip insertl end $wordlist
No examples yet.
This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category wip of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation.
interpreter, list, word
Programming tools
Copyright (c) 2007-2010 Andreas Kupries <andreas_kupries@users.sourceforge.net>
2.2 | wip |