On Sun, Jan 18, 2009 at 10:53 PM, Dick Hollenbeck <[email protected]> wrote: > With that assumption in mind, I again feel it bolsters my belief that C > is NOT the correct language for any part of this project except for the > cable drivers, and even they could be done in C++. I am fluent in C, > C++, Java and Python and have seen wide variation in maintainability and > ease of adding new features that want to jiggle the status quo of > thought on this issue a little here.
The currently chosen approach is to do things in c and tcl and I don't see why some would need yet an other language. it's complicated enough like that. besides putting things outside of the core puts them in a place less people will look. The SVF format is not going to change any time soon and the code would have gotten more workout from then the xsvf . I think it is the right place to put this support The language used in openocd is "c" and I guess it makes sense as most OS related things are still written in c and therefore chances are that developer will know c better. Myself I prefer Ruby, LUA and C# over Python TCL and c++ but who cares :p Greetings _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
