Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Revised C++ ABI abstraction patches
Date: Thu, 15 Mar 2001 13:38:00 -0000	[thread overview]
Message-ID: <3AB13647.7B5E4B5@cygnus.com> (raw)
In-Reply-To: <npr8zy3men.fsf@zwingli.cygnus.com>

Jim Blandy wrote:
> 
> Eli Zaretskii <eliz@is.elta.co.il> writes:
> > >     * cp-abi-gnu-v2.c (gnu_v2_destructor_prefix_p,
> > [...]
> > >     (gnu-v3-abi.o): Add.
> > >     (gnu-v2-abi.o): Add.
> >
> > So what is it: cp-abi-gnu-v2 or gnu-v2-abi?  I prefer the latter, and I
> > thought that was the conclusion of the earlier discussions about that.
> 
> gnu-v[23]-abi were the names originally used in Daniel's patch.  I
> changed them to cp-abi-gnu-v[23], for the reasons explained in the
> ChangeLog entry provided with the patch:
> 
>         * cp-abi-gnu-v2.c, cp-abi-gnu-v3.c: Renamed from gnu-v2-abi.c
>         and gnu-v3-abi.c, to show more clearly that they are
>         implementations of cp-abi.h.
>         * Makefile.in: Adjusted accordingly.
> 
> The names `gnu-v[23]-abi' just indicate that they're implementations
> of some ABI, but the files are actually specifically dealing with C++
> ABI's.  It's not meaningful to talk about an ABI without knowing the
> source language, since an ABI is a binding between a particular source
> language and a particular machine language.

Jim, I think it is a compromize between that and the need to keep 8.3
support simple. Longer names can be introduced when GDB's directory
structure is changed.  For the moment I'd stick to something that works
on both DOS and UNIX.

This is exactly the same as what happened to:

	ui-out / mi-out, cli-out
	ui-file / mi-file, tui-file

enjoy,
	Andrew


  reply	other threads:[~2001-03-15 13:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  1:50 Jim Blandy
2001-03-15  3:15 ` Eli Zaretskii
2001-03-15  6:21   ` Fernando Nasser
2001-03-15  6:46     ` Daniel Berlin
2001-03-15 10:40   ` Jim Blandy
2001-03-15 13:38     ` Andrew Cagney [this message]
2001-03-15 14:05       ` Jim Blandy
2001-03-16 23:28     ` Eli Zaretskii
2001-03-19  9:38       ` Jim Blandy
2001-03-19 11:58         ` Eli Zaretskii
2001-03-15 14:57 ` Andrew Cagney
2001-03-15 17:57   ` Jim Blandy
2001-03-15 18:10     ` Andrew Cagney
2001-03-15 19:12     ` Daniel Berlin
2001-03-15 19:56       ` Jim Blandy
2001-03-15 18:58   ` Daniel Berlin
2001-03-15 10:50 Michael Elizabeth Chastain
2001-03-15 11:04 ` Jim Blandy
2001-03-15 11:32   ` Michael Snyder
2001-03-15 11:35   ` J.T. Conklin
2001-03-15 12:36     ` Jim Blandy
2001-03-15 15:21       ` Stan Shebs
2001-03-15 17:54         ` Jim Blandy
2001-03-15 20:11           ` Andrew Cagney
2001-03-15 13:46   ` Andrew Cagney
2001-03-15 15:01     ` Daniel Berlin

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=3AB13647.7B5E4B5@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@cygnus.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