From: Jan Kratochvil <jan.kratochvil@redhat.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 13:44:00 -0000 [thread overview]
Message-ID: <20100616134202.GA32490@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <AANLkTimffHXNNqQdr3QYa2xkL7dv33LuiCs1dtxuLBD4@mail.gmail.com>
On Wed, 16 Jun 2010 13:54:16 +0200, 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?
See the last discussion:
Move GDB to C++ ?
http://sourceware.org/ml/gdb/2008-07/msg00077.html
http://sourceware.org/ml/gdb/2008-08/msg00004.html
There is an ongoing work to make it at least possible:
http://sourceware.org/gdb/wiki/ArcherBranchManagement
-> archer-ratmice-compile-Wc++-compat
This idea is not new.
Thanks,
Jan
next prev parent reply other threads:[~2010-06-16 13:44 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 [this message]
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
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=20100616134202.GA32490@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.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