Øyvind Harboe wrote: > How about this approach to the problem of scripting? > > - make OpenOCD a library > - make that library usable from Python & Lua.
Lua works the other way around. It was, again, designed and implemented from ground up to be embedded into a host software. > - Leave Jim Tcl in there for now. No. The whole point of the suggestion is to replace Tcl. > - Eventually make the scripting choice for OpenOCD compile time > configurable. It's not a choice. There's only one set of cfg files, and they will only be in one language. Of course it's interesting to consider completely replacing the cfg files being scripts for another approach, but I think that's an orthogonal idea. > The above route seems pretty doable via incremental patches... Not a holy grail. One logical change one patch. Some changes are larger than others, but as I said, I don't believe JimTcl->Lua would be such a large change. Anyway, I did not ask for buy-in. I asked if someone was strongly against replacing Tcl. Not many, if any, were. I think this is good! :) //Peter ------------------------------------------------------------------------------ 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
