Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: xingxing pan <forandom@gmail.com>
To: Robert Dewar <dewar@adacore.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	Jan Kratochvil <jan.kratochvil@redhat.com>,
	gdb@sourceware.org
Subject: Re: Why isn't GDB designed and implemented by using Object-Oriented 	methodology?
Date: Fri, 18 Jun 2010 02:08:00 -0000	[thread overview]
Message-ID: <AANLkTin8CYVMQMY9Ru6pkqbKICRWS2iz1neHO7Qwihbj@mail.gmail.com> (raw)
In-Reply-To: <4C19D22A.3090703@adacore.com>

Actually, what I want to say is that coding is different from design.

2010/6/17 Robert Dewar <dewar@adacore.com>:
> Joel Brobecker 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
>>
>> One can develop software using "Object Oriented *methodology*" without
>> using a language that implements classes. An object is, at its simplest,
>> data and methods.
>
> Interesting to see this definition take hold, very different from
> the classical (e.g. Simula) view of objects. To me data+methods =
> abstract data type.
>


  reply	other threads:[~2010-06-18  2:08 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 [this message]
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=AANLkTin8CYVMQMY9Ru6pkqbKICRWS2iz1neHO7Qwihbj@mail.gmail.com \
    --to=forandom@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=dewar@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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