Sorry to jump in late here, but OpenOCD is already written in C.  Why would
we rewrite in C++?  I can appreciate that the refactoring Tomek is
proposing is a large effort, but what benefit does doing it in C++ provide?

I mean, I'd love to replace the JimTcl components with Lua too, but until I
can formulate real benefits to this, I wouldn't think of proposing it.


On Mon, Jan 14, 2013 at 2:34 PM, David Riley <[email protected]> wrote:

> On Jan 14, 2013, at 2:11 PM, Laurent Gauch wrote:
>
> > Le 14.01.2013 19:42, CeDeROM a écrit :
> >> Hello Laurent :-)
> >>
> >> Thank you for your input and good words :-) Glad we agree here, also
> >> that this is a lot of work to be done, this is why I prefer to ask and
> >> plan first :-)
> > great point.
> >> We can use simple name "Core" no problem :-)
> >>
> >> Regarding the C++ there should be a bigger discussion and maybe some
> >> analysis of what are the advantages of C over C++ and vice versa and
> >> we can choose better solution... C is simple and fast, and the work
> >> can be done with C, there are some people that want it done in C, so
> >> we would have to present very strong arguments to use C++ I guess...
> >> what are the real code size and speed differences?
> > If we want an elegant solution and more robust the way is C++ !
> >
> > Code size differences between C or C++ ? ... The C++ will give us a bit
> > larger binary but the gap will be really small. But why this question in
> > 2013 ?
> > Speed differences between C or C++ ? ... The real speed gain will be in
> > the concept and not the language used, except if you use a script
> langage !
>
> True, but if OpenOCD is to be used in embedded devices, there are
> things you can do to make the speed and memory footprint more
> palatable.  You almost certainly want to disable RTTI (unless there
> is a very good reason to keep it), and you may want to think about
> eliminating or at least heavily restricting the use of exceptions,
> because they can have a real (>1%) performance impact, especially
> within a try/catch block because of the stack unwinding semantics.
>
> Otherwise, C++ is fine these days on embedded devices; even the
> STL tends to perform fairly well, though that does depend on the
> C++ library.
>
>
> - Dave
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> OpenOCD-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openocd-devel
>
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to