I'm going with Jim Tcl for now, for two reasons: - Jim Tcl does not add a dependency on other packages. For those that don't need or want scripting this should be a killer feature :-) - "full" Tcl/Tk is a PC hosted scripting language(can't be run in embedded mode) and I therefore place it on par with any other scripting language out there. I'd like to see OpenOCD easy to bind to any scripting language out there hosted on a PC. I don't know what this hosting interface would look like yet. Perhaps modeled on SQL :-) Any app can send Tcl to OpenOCD and receive a result. This is a different problem than what I'm currently working on. - fait accompli & I've got experience with Jim Tcl.
-- Ø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
