Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: xingxing pan <forandom@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Why isn't GDB designed and implemented by using Object-Oriented 	methodology?
Date: Wed, 16 Jun 2010 17:10:00 -0000	[thread overview]
Message-ID: <4C19057D.8090607@codesourcery.com> (raw)
In-Reply-To: <AANLkTimffHXNNqQdr3QYa2xkL7dv33LuiCs1dtxuLBD4@mail.gmail.com>

xingxing pan wrote:
> When meeting so many structs and function pointer in the source codes,
> dose anyone have the thought to redesign and implement GDB using
> Object-Oriented  methodology?
>   

Well, the target vector abstraction dates from 1990, so that means we've 
been redesigning GDB to use object-oriented methodology for the past 
twenty years or so.

In practice, the hard part for us is deciding what the objects *should* 
be.  If someone posted a mega-patch tomorrow that converted GDB to C++ 
written in good style, that wouldn't do a thing to help me figure out 
how to support changing properties of tracepoints while a trace is 
running, or how to speed up symbol reading for really large executables, 
or how to reliably install software breakpoints with the inferior 
running in a non-stop mode.

So yes, more OOM "would be nice" and we encourage the submission of 
patches going in that direction, but it's not the magic bullet that will 
magically make GDB easy to work on.

Stan


      parent reply	other threads:[~2010-06-16 17:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 11:54 xingxing pan
2010-06-16 13:44 ` Jan Kratochvil
2010-06-16 16:37   ` Joel Brobecker
2010-06-17  7:43     ` Robert Dewar
2010-06-18  2:08       ` xingxing pan
2010-06-21 19:59         ` Tom Tromey
2010-06-16 17:10 ` Stan Shebs [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C19057D.8090607@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=forandom@gmail.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox