From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb@sources.redhat.com
Subject: Re: [PATCH] Naming dwarves
Date: Tue, 20 May 2003 21:01:00 -0000 [thread overview]
Message-ID: <vt2vfw5uxzo.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <20030518043519.GA11124@nevyn.them.org>
What Elena and Andrew said about the current naming convention
(dwarf2) is my understanding, too.
But it's a bit confusing to talk about the modern Dwarf reader this
way. If I say "the Dwarf reader", it's not clear that I don't mean
Dwarf 1. (Which I never do.) If I say "the Dwarf 2 reader", then it
sounds like I want to exclude the extensions in Dwarf 3. (Which I
almost never do.) And I end up saying odd-sounding things like "the
modern Dwarf reader".
The major distinction between Dwarf 1 and Dwarf 2 was the introduction
of the abbreviation table, introduced because Dwarf 1 was even more
enormous than Dwarf 2 is. But since that change, Dwarf has been able
to grow pretty well, and incorporate major improvements like duplicate
suppression, without breaking compatibility again. So I wonder if we
won't eventually have a reader named dwarf2 that handles Dwarf 2, 3,
and 4.
Would it make sense to, at some point (not today) adopt "dwarf1" as
the prefix for the dwarf1 reader, and simply "dwarf" for the modern
Dwarf reader?
For what it's worth, the latest Dwarf spec usually just calls it
"DWARF".
next prev parent reply other threads:[~2003-05-20 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 12:53 Mark Kettenis
2003-05-18 4:35 ` Daniel Jacobowitz
2003-05-20 21:01 ` Jim Blandy [this message]
2003-05-19 13:07 ` James Cownie
2003-05-19 14:03 ` Elena Zannoni
2003-05-20 18:54 ` 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=vt2vfw5uxzo.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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).