Would anyone mind terribly if I added Jim Tcl support(also hosted on BerliOS) to OpenOCD?
Motivation: - use Jim Tcl as a command line parser. The syntax will be largely unchanged, but the error handling will be better(exceptions), etc. - a large part of OpenOCD is code that will not suffer at all performance wise from being scripted. Writing some of this in C is tedious w.r.t. malloc(), etc. Tcl provides exception handling and resource tracking without introducing C/C++. - scripting *can* be useful for users as well. Plan: - leave current interpreter as-is - add option to OpenOCD to use tcl command line interpreter instead of OpenOCD interpreter - invoke existing OpenOCD commands from Tcl - invoke Tcl from existing command interpreter - commit - wait for feedback from community The next step would be to make some small evolutionary changes to OpenOCD. Perhaps switch from C to Tcl in some internal places. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
