On 26 May 2012 20:39, Peter Stuge <pe...@stuge.se> wrote: > Akos Vandra wrote: >> > a protocol is also *not* the same thing as a programming language. >> >> Please explain what is the problem with TCL? It does the job, it >> seems quite easy to learn, and it's extensible... > > I'd really like to get rid of the jimtcl dependency, and much rather > sooner than later. > > Not because jimtcl is a bad implementation or TCL is a bad language, > but again because I think remote control should use a protocol rather > than a programming language.
I understand your point of view, however there is no real alternative to it at the moment, right? I mean is there another working way to "remote control" openocd, that would be favored over TCL? Regards, Ákos Vandra > > > //Peter > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > OpenOCD-devel mailing list > OpenOCD-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openocd-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
