Nick Ing-Simmons wrote: > As one of those well able to do the plugging, parsing and lexing what > scared me off was the black magic of the op "tree" - which is neither > a parse tree in traditional sense, nor threaded code as in FORTH but > a weird hybrid. My cache friendly data structures idea might result > in having a tree (for parse, symbols introspection) and threaded code > for execution. Forget the cache for the moment - seperation of the read-only and read/write parts of the parse tree would be a major step in that it would remove a lot of the the COWs (Copy On Writes) that happen whenever a perl script forks another copy of itself. It would probably help threading quite a bit as well. -- Alan Burlison