Why is “send” in Soar different from “send” in Tk, or What do I do if my Soar process comes up as soar2?
[This stuff will be subject to some change in Soar 7.1 and on, I suspect, -FER] Soar is and is not different from “send” in Tk. By default, Soar’s send is different from Tk. When Soar 7 is compiled with Tk, and -useIPC is specified on the command line at runtime, Soar’s send is the same as Tk. From: Karen J. Coulter (kcoulter@eecs.umich.edu), Date: Apr 11, 1997 Subject: Re: [Soar-Bugs #85] Why is “send” in Soar different from “send” in Tk? To support multiple agents, Soar 7 takes care of all the overhead of creating and maintaining multiple interpreters (which wasn’t supported by Tcl < 7.6). Soar 7 creates a flat space of interpreters -- no single interpreter is the supervisor or owner of another. To allow for communication among agents, Soar uses the "send" command. Tcl itself doesn't have a "send" command, it comes from Tk. But we didn't want to require Tk (i.e., X Windows) in order to run Soar. So Karl wrote an X-server-less version of "send" that could be used to support multiple a
Related Questions
- How can response messages be correlated with request messages? Can this be done if the process to send a reply is different than the process to receive the request?
- Why is "send" in Soar different from "send" in Tk, or What do I do if my Soar process comes up as soar2?
- If a referral comes from a defense firm is the life care planning process different?
