From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Kleck <jim.kleck@NetergyNet.COM>
Cc: gdb@sources.redhat.com, insight@sources.redhat.com
Subject: Re: Register group proposal
Date: Tue, 27 Feb 2001 15:17:00 -0000 [thread overview]
Message-ID: <3A9C34ED.96F8D6E0@cygnus.com> (raw)
In-Reply-To: <3A9C201B.345097FA@netergynet.com>
Jim Kleck wrote:
> which preserves the type errors and simplifies the declaration of
> objects of the desired type:
>
> T_BLAH this_blah;
>
> vs.
>
> struct blah *this_blah;
To go full circle, I guess :-)
The thing about a typedef is that there can really only be one or each
name amonst all of your header files. The choices are rougly: don't
have the typedef and have each blah.h independant; use a typedef in
blah.h and have everything refering to blah.h suck it in; put the
typedef in defs.h; or have defs.h just suck in blah.h.
All the recent objects have used ``struct blah *'' giving fairly
independant header files. The older GDB code lived on a diet that
consisted on all of the above.
enjoy,
Andrew
next prev parent reply other threads:[~2001-02-27 15:17 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-28 1:59 Bernard Dautrevaux
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-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 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=3A9C34ED.96F8D6E0@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=jim.kleck@NetergyNet.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).