This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Will therefore GDB utilize C++ or not?
- From: <Paul_Koning at Dell dot com>
- To: <tromey at redhat dot com>
- Cc: <gdb at sourceware dot org>
- Date: Fri, 18 May 2012 18:46:58 +0000
- Subject: Re: Will therefore GDB utilize C++ or not?
- References: <20120330161403.GA17891@host2.jankratochvil.net> <87aa2rjkb8.fsf@fleche.redhat.com> <4F832D5B.9030308@redhat.com> <20120409190519.GA524@host2.jankratochvil.net> <4F833D29.4050102@redhat.com> <20120416065456.GA30097@host2.jankratochvil.net> <4F8ECB72.70708@redhat.com> <20120418151553.GA16768@host2.jankratochvil.net> <4F8EDD7B.2010602@redhat.com> <20120418155354.GA17912@host2.jankratochvil.net> <201204181748.q3IHm1cF002815@new.toad.com> <87pqb4q2on.fsf@fleche.redhat.com> <201204182309.q3IN9FcF019607@new.toad.com> <87k409gwv0.fsf@fleche.redhat.com>
On May 18, 2012, at 2:36 PM, Tom Tromey wrote:
> ...
> For example, look at the Python layer. Despite patch review and our
> knowledge of the issues, we still have error-checking and
> reference-counting bugs in the code. You can go through the list
> archives and find them.
How would C++ help with reference counting bugs? I could see how it might (or might not) help with the subset related to error handling that can be made clearer with exceptions. But the reference counting errors I remember were straight algorithmic mistakes that, as far as I can see, would have existed in the exact same form if the algorithm had been expressed in C++.
paul