From: Bernard Dautrevaux <Dautrevaux@microprocess.com>
To: 'Jim Kleck' <jim.kleck@NetergyNet.COM>,
Andrew Cagney <ac131313@cygnus.com>
Cc: Nick Duffek <nsd@redhat.com>,
Bernard Dautrevaux <Dautrevaux@microprocess.com>,
gdb@sources.redhat.com, insight@sources.redhat.com
Subject: RE: Register group proposal
Date: Wed, 28 Feb 2001 01:59:00 -0000 [thread overview]
Message-ID: <17B78BDF120BD411B70100500422FC6309E21B@IIS000> (raw)
> -----Original Message-----
> From: Jim Kleck [ mailto:jim.kleck@NetergyNet.COM ]
> Sent: Tuesday, February 27, 2001 7:32 PM
> To: Andrew Cagney
> Cc: Nick Duffek; Dautrevaux@microprocess.com; gdb@sources.redhat.com;
> insight@sources.redhat.com
> Subject: Re: Register group proposal
>
>
> A consistent interface is *one* reason to have a particular interface.
> However, it is not the only thing to consider, nor have the "style
> advantages and disadvantages" been fully explored... at least not
> in this forum.
>
> I would note that "struct blah *" is NOT fully opaque. Its
> very use implies
> a control structure of some sort, and it is quite different
> from the standard
> types provided by the language. Thus it is not using the full
> "extensability"
> of the language.
>
> An alternative I have not seen discussed is to have "typedef
> void * blah"
> as the public interface (then the implementation would need to cast
> the object to the internal representation before operating on it).
>
> Finally, in the "LONGEST" example, why replace "a = b + c;" with
> "a = add(b, c);". My inclination would be to overload the "+" so that
> no change to the users of the type are necessary.
>
I'm afraid GDB is written in C isn't it? so overloading '+' is not really an
option.
Regards,
Bernard
--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel: +33 (0) 1 47 68 80 80
Fax: +33 (0) 1 47 88 97 85
e-mail: dautrevaux@microprocess.com
b.dautrevaux@usa.net
--------------------------------------------
next reply other threads:[~2001-02-28 1:59 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 1:59 Bernard Dautrevaux [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2001-02-27 9:57 ` Andrew Cagney
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
[not found] ` <200102221237.f1MCbtX02766@rtl.cygnus.com>
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=17B78BDF120BD411B70100500422FC6309E21B@IIS000 \
--to=dautrevaux@microprocess.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=jim.kleck@NetergyNet.COM \
--cc=nsd@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