On Wed, Jun 25, 2008 at 11:51 AM, Sergey Lapin <[EMAIL PROTECTED]> wrote: > On Wed, Jun 25, 2008 at 1:42 PM, Øyvind Harboe <[EMAIL PROTECTED]> wrote: >> Jim Tcl is embedded friendly, which for me is a killer feature + >> it is used by VHDL developers via e.g. ModelSim. >> >> Lua is nice as well. I'm surprised to see it rated that high. Never seen >> in real life usage. Could be who I hang with :-) >> >> The other killer feature of Jim Tcl is that *I* can put it together >> real quickly(being a Jim Tcl maintainer). >> >> I first ran across Jim Tcl in athttpd from eCos. > > I really like TCL support, but is it possible to add it a modular way, > at least from > user perspective? I mean, to be possible to write scripts both in TCL, > OpenOCD scripting and Lua? > So, to implement some interface to hook-up extra scripting language, whatever > user might want in future? OpenOCD might use TCL or whatever internally.
I intend to use Tcl internally in OpenOCD, i.e. switch parts of OpenOCD from C to Tcl. This would be tedious parts where there is a lot of malloc()/free() and not a lot of performance requirements. Good examples to follow. Sticking to *one* scripting language for the implementation of OpenOCD makes sense. openocd.c would then contain an example of how to hook up an interpreter. I don't want to impose any scripting preference on the user, but the work I plan to do would, for now, only expose Tcl. Lua would be my second choice. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
