From: Andrew Cagney <cagney@gnu.org>
To: gdb@sources.redhat.com
Subject: Remaining builtin_types (potential flag day)
Date: Wed, 28 Jul 2004 20:00:00 -0000 [thread overview]
Message-ID: <4107CCED.3040900@gnu.org> (raw)
Hello,
There are currently ~1400 occurances of /builtin_type_/ in GDB's source.
While some are ok (builtin_type_ieee...*) many are not (typically
needing a conversion to builtin_type()).
For the moment we can let these remaining uses be migrated incrementally
(chance has it someone will find an interface change (1)). However,
eventually, well have to change all remaining references. Given their
magnitude, this suggests a "Flag Day".
Andrew
(1) I wonder if the way languages create their primitive type vector can
be simplified - I implemented a mindless vector->vector conversion.
next reply other threads:[~2004-07-28 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 20:00 Andrew Cagney [this message]
2004-07-28 23:09 ` Jim Blandy
2004-07-29 23:27 ` 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=4107CCED.3040900@gnu.org \
--to=cagney@gnu.org \
--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).