On Tue, Feb 28, 2012 at 10:46 AM, Spencer Oliver <[email protected]> wrote: > In my original statement i was referring to the fact i am not familiar > with integrating TCL-C. I can work my around tcl enough for OpenOCD > usage. > > The other argument is how many people understand lua - probably the same as > tcl. > I do not have strong opinions for either jim or lua - the community > will have to decide.
I agree with Spen - what does Lua brings comparing to Jim TCL (except a lot of work on replacing it) ? Benefits are not so big comparing to the effort. I would be more convinced with Python. I see no reason why would anybody choose Lua ove Python : it is more mature, has bigger community, bunch of documentation... It can be made small, and even embedded on the chip (http://code.google.com/p/python-on-a-chip/). People are using it everyday in desktop app scripting and would be familiar to it. In any case, I like the way Jim TCL works now in OpenOCD - quite fine. So, if it should be replaced, I'd opt for the modular approach making OpenOCD a library. BR, Drasko ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
