This is the mail archive of the
xconq7@sources.redhat.com
mailing list for the Xconq project.
RE: New Interpreter (was RE: Marketing Xconq?)
- From: Eric McDonald <mcdonald at phy dot cmich dot edu>
- To: Erik Jessen <ejessen at adelphia dot net>
- Cc: 'xconq' <xconq7 at sources dot redhat dot com>
- Date: Mon, 17 Nov 2003 23:01:25 -0500 (EST)
- Subject: RE: New Interpreter (was RE: Marketing Xconq?)
On Mon, 17 Nov 2003, Erik Jessen wrote:
> My thought was this:
> - add an interpreter, using a standard language (like Perl) that can
> simply access existing data-structures.
>
> The hard part (at least to me) is: how do you decide when to execute the
> new programs? It's easy to load data-structures at initialization time
> & then have canned code execute it (what we do today). It's harder to
> say "execute this subroutine any time combat occurs".
Well, with the Tcl/Tk interface we access a Tcl interpreter
from C code all the time. As long as whatever language you have
in mind can expose its interpreter to C in some for or another,
you can call back into the interpreter and ask it to do things on
your behalf. And vice versa, if the interpreter can call C
functions. Then it is simply a matter of putting hooks into the
relevant code sections. But my experience with Tcl and Xconq is
that this sort of arrangement is harder to debug.
Also, with a full blown interpreter being used, one must consider
the security aspect. Especially since Xconq has the setgid bit set
on Unix/Linux systems....
> Alas, I've not been able to locate my examples (I hope they weren't on
> my system that had the HDD crash), but I'm hopeful of backups.
Good luck finding them (and anything else you lost).
Eric