From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Register group proposal
Date: Tue, 27 Feb 2001 08:53:00 -0000 [thread overview]
Message-ID: <20010227115222.A11298@redhat.com> (raw)
In-Reply-To: <3A9AFC19.9673A100@cygnus.com>
On Mon, Feb 26, 2001 at 08:00:09PM -0500, Andrew Cagney wrote:
>Christopher Faylor wrote:
>>
>> On Mon, Feb 26, 2001 at 01:54:19PM -0500, Andrew Cagney wrote:
>> >>That works fine if xxx is a struct. If, at some point, you have an
>> >>amazing idea that allows you to change all xxx's to "unsigned short"
>> >>you're stuck with a lot of editing.
>> >
>> >Um, are you being serious here?
>>
>> Do you have some kind of problem with this simple concept? Been programming
>> long?
>
>GDB is made up of several objects. Some have been identified - a
>frame, an architecture, the cli output device (ui-file / ui-out), and
>even a proposal for reggroup .... Others are still lurking beneath the
>surface.
>
>I don't think you are seriously suggesting that one of these
>``fundamental'' objects - ex ``struct gdbarch *'' - be replaced by
>``unsigned short''.
I believe that someone did suggest using an "fd style" interface where
you are passing around a "handle" or a "cookie" rather than a pointer
to a struct/union/whatever.
However, I was just responding to the general point of typedefs being
useless, and the argument that struct could be used everywhere in place
of a typedef. I was not advocating a particular implementation, just
noting, as others have, that there were advantages to their use.
I have never heard of another project that bans the use of typedefs
but I guess there aren't many projects like gdb.
cgf
next prev parent reply other threads:[~2001-02-27 8:53 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 5:29 Bernard Dautrevaux
2001-02-26 9:28 ` Christopher Faylor
2001-02-26 10:56 ` Andrew Cagney
2001-02-26 11:28 ` Christopher Faylor
2001-02-26 17:02 ` Andrew Cagney
2001-02-27 8:53 ` Christopher Faylor [this message]
2001-02-27 9:57 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2001-02-28 1:59 Bernard Dautrevaux
2001-02-23 2:52 Bernard Dautrevaux
2001-02-24 15:43 ` Nick Duffek
2001-02-26 18:21 ` Andrew Cagney
2001-02-27 10:30 ` Jim Kleck
2001-02-27 11:24 ` Per Bothner
2001-02-27 13:44 ` Jim Kleck
2001-02-27 15:17 ` Andrew Cagney
2001-02-22 9:19 Michael Elizabeth Chastain
2001-02-21 3:00 Stephane Carrez
2001-02-21 7:00 ` Nick Duffek
2001-02-21 9:34 ` Andrew Cagney
2001-02-20 20:56 Nick Duffek
2001-02-21 6:44 ` Fernando Nasser
2001-02-21 7:10 ` Nick Duffek
2001-02-21 7:36 ` Fernando Nasser
2001-02-21 7:58 ` Keith Seitz
2001-02-21 8:50 ` Andrew Cagney
2001-02-21 11:43 ` Andrew Cagney
2001-02-25 15:36 ` Nick Duffek
2001-02-21 11:43 ` Andrew Cagney
2001-02-21 12:28 ` Andrew Cagney
2001-02-21 12:18 ` Andrew Cagney
2001-02-22 0:59 ` Eli Zaretskii
2001-02-22 4:29 ` Nick Duffek
2001-02-22 8:46 ` Andrew Cagney
2001-02-22 8:56 ` Keith Seitz
2001-02-22 9:20 ` Andrew Cagney
2001-02-22 5:17 ` Nick Duffek
2001-02-22 6:36 ` Fernando Nasser
2001-02-22 8:23 ` Andrew Cagney
2001-02-22 7:58 ` Andrew Cagney
2001-02-22 8:37 ` Nick Duffek
2001-02-22 9:12 ` Andrew Cagney
2001-02-22 10:15 ` Nick Duffek
2001-02-22 10:25 ` Andrew Cagney
2001-02-22 11:40 ` Eli Zaretskii
2001-02-22 11:02 ` Kevin Buettner
2001-02-22 12:08 ` Andrew Cagney
2001-02-22 8:16 ` Andrew Cagney
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=20010227115222.A11298@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).