On Fri, Jun 27, 2008 at 1:13 AM, Tim Hudson <[EMAIL PROTECTED]> wrote:
> Øyvind Harboe wrote:
>>> for {set i 0} {$i < 10} {incr i} {openocd "mww [expr $i*4] 0"}
>
> Hooking the command interpreter on a per-line basis isn't a good approach IMHOThe reason for hooking it up to the command line interpreter is that I'd then replace the command line interpreter w/tcl. The OpenOCD commands actually follow Tcl syntax: OpenOCD: flash write_image x y Tcl: flash write_image x y see? same syntax :-) > I think something more along the lines of embedded script usage in web pages > would make more sense: > > e.g. > > <?lua > ... lua code here > ?> > > or with tcl: > > <?tcl > ... tcl code here > ?> > > Scripts really should be allowed to be multi-line and include whatever syntax > the scripting language wants to use - be it lua, tcl, php, perl, whatever is > embedded. I'm not crazy about this inversion approach for OpenOCD. Since the command line interpreter and tcl would(eventually) be the same thing, there is no need for inversion. Multiline is currently supported by: ocd> source myscript.tcl or by using the OpenOCD search path: ocd> source [find myscript.tcl] -- Ø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
