On Thu, Jul 10, 2008 at 11:29 AM, Spen <[EMAIL PROTECTED]> wrote: >> >> > originally flash banks sent its output to command_print, >> can tcl not >> > have its own output handler and then parse the data there? >> >> I'm not sure what you are proposing. >> >> Parsing is painful and unecessary; I'm trying to avoid it. > > I am not really proposing anything. > > The point i am trying to make is that openocd now requires commands.tcl to > operate. > This is exactly the sort of thing i am not in favour of.
Can you explain a bit why/how? I'd like to avoid any pitfalls. > I am happy to go with the majority, i would just like to here other > opinion's on the subject. I guess there is a consensus for improved scripting support. The way the command handler & tcl integrates is to some extent an implementation issue. The tcl implementation of "flash banks" on top of "flash_banks" has the advantage of exercising the API using the standard OpenOCD commands(i.e. more testing). Similarly if we made tcl a compile time option, then we'd see less exercise of that code, which is bad from a testing point of view. -- Ø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
