Thanks for following up on this. The style guide needs updating w.r.t. embedded considerations(I was going to work on the style guide the other day, but docs didn't build at the time and then I forgot about it...)
> However, alloc_vprintf() seems to have a rather cumbersome > implementation. Is there a reason why it is looping, trying with > increasingly larger allocations? It was optimized for maximum exercise of code paths at the time rather than performance. -- Ø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
