From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/DWARF] Set TYPE_FLAG_STUB for enum DIEs that are declarations only
Date: Tue, 08 Jan 2008 05:57:00 -0000 [thread overview]
Message-ID: <20080108055714.GB11831@adacore.com> (raw)
In-Reply-To: <20080105153709.GH5975@adacore.com>
Hi Eli,
> > That's not the kind of comment I was suggesting. I meant some summary
> > of the long explanation you posted as a preamble to the patch, which
> > explained why debugging Ada programs needed that.
>
> The preample was an introduction to an part of the Ada language, not
> a description of a problem. The "stub" DIE is a routine concept,
> that we see all the time with C opaque types. In fact, any type
> can be incomplete.
>
> But rather than arguing this ad vitam aeternam, here's a suggestion:
First of all, I have to apologize for writing this way to you.
I admit to being fustrated, but my fustration was not with you. it
was with myself, because I don't understand exactly what it is that
you'd like me to put in the comment.
I know this situation will happen again in the future because we
all have different conceptions of what necessary documentation is.
I will try to say it openly when I don't understand, so that you
can help me (please :).
Do you still think a comment should be added? If yes, is the comment
I suggested a step in the right direction?
> /* Enumeration DIEs descriptions can be imcomplete. In Ada, any
> type can be declared as private in the package spec, and then
> defined only inside the package body. Such types are known as
> Taft Amendment Types. When another package uses such a type,
> an incomplete DIE may be generated by the compiler. */
--
Joel
next prev parent reply other threads:[~2008-01-08 5:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 15:45 Joel Brobecker
2008-01-03 15:46 ` Joel Brobecker
2008-01-03 16:02 ` Daniel Jacobowitz
2008-01-03 17:38 ` Joel Brobecker
2008-01-05 12:33 ` Eli Zaretskii
2008-01-05 15:05 ` Joel Brobecker
2008-01-05 15:17 ` Eli Zaretskii
2008-01-05 15:37 ` Joel Brobecker
2008-01-08 5:57 ` Joel Brobecker [this message]
2008-01-08 20:25 ` Eli Zaretskii
2008-01-09 4:31 ` Joel Brobecker
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=20080108055714.GB11831@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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