We don't have a way to measure consensus but I belive the current consensus can be summarized as:
- OpenOCD stays C for now. There has to be a good plan and major upside to budge the status quo. - OpenOCD has a number of quaint constructs that mimick features in other languages(virtual function tables, exception handling, resource trackinig, etc.). This is implemented through very loose conventions, macros and such. A sensible use of e.g. C++ could get rid of those "strange" constructs. - We've got Tcl to handle a lot of the tedium that benefits from resource tracking and exception handling. There is even talk of moving more stuff into the scripting domain, making OpenOCD more of a library/kernel than anything else. I believe the primary concern is to use a programming convention that is best suited for community development, i.e. not so much concern for the person who writes the code, but the person who is going to write patches. -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
