On Wed, Nov 11, 2009 at 10:47 PM, Zach Welch <z...@superlucidity.net> wrote: > On Wed, 2009-11-11 at 21:40 +0100, Øyvind Harboe wrote: >> On Wed, Nov 11, 2009 at 9:32 PM, Zachary T Welch <z...@superlucidity.net> >> wrote: >> > This series begins to improve the built-in command help: >> > >> > * provides a full list of all registered commands, not just those that >> > define a handler function). >> > * allows arbitrary command nesting >> >> What does this mean? >> >> Shouldn't we move *away* from command nesting and make >> e.g. target specific commands methods on the target object? > > This is a mechanism change, not policy. The code is cleaner; it happens > to give the option for more features, regardless of how (or if) we > decide use them. Also, there seems to be more for commands to do than > work on targets.
OK. I've posted a separate subject on the "method on targets" issue, not an urgent issue, but it will be good to have a sense of direction on that one... -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
