From: Joel Brobecker <brobecker@gnat.com>
To: Paul Hilfinger <hilfingr@gnat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Extend some arithmetic operations to range types.
Date: Fri, 26 Mar 2004 19:03:00 -0000 [thread overview]
Message-ID: <20040326190334.GH1483@gnat.com> (raw)
In-Reply-To: <20040326180659.GA21603@nevyn.them.org>
> Is there something clearer you can call this? "base" to me means "as
> in inheritance", which is not really appropriate here.
How about using the dwarf-2 terminology: basis_type? That's how they
call the type on which the range type is based:
The subrange entry may have a DW_AT_type attribute to describe
the type of object, called the basis type, of whose values this
subrange is a subset.
(base type is the equivalent in Ada terminology)
--
Joel
next prev parent reply other threads:[~2004-03-26 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 10:59 Paul Hilfinger
2004-03-26 18:07 ` Daniel Jacobowitz
2004-03-26 19:03 ` Joel Brobecker [this message]
2004-03-26 20:32 ` Daniel Jacobowitz
2004-03-29 11:29 ` Paul Hilfinger
2004-03-31 19:05 ` Daniel Jacobowitz
2004-04-01 12:11 ` Paul Hilfinger
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=20040326190334.GH1483@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hilfingr@gnat.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