Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] handle VLA in a struct or union
Date: Wed, 21 May 2014 18:24:00 -0000	[thread overview]
Message-ID: <20140521182411.GM22822@adacore.com> (raw)
In-Reply-To: <87fvk3kpng.fsf@fleche.redhat.com>

Hey Tom,

> Joel> Perhaps we might think of having a new value_from_contents_and_address
> Joel> that produces the value without resolving the type? If Ada is the only
> Joel> user, as it would be, we could possibly put implement that in ada-lang,
> Joel> I think. Kind of ugly, but this would be medium-term only, since we are
> Joel> slowly trying to get rid of the GNAT encodings.
> 
> I put it in value.c, since I generally like to keep the whole module
> together, having been bitten before by code living in the wrong spot.
> I don't really care much though, in case you do.

Great minds think alike. I was offering alternatives in case people
don't want to keep stuff that is not necessarily specific to Ada
but only used by Ada in the common area. But that would usually be
nonsense to me, since that encourages proliferation of the same code
at multiple locations. But sometimes it's only a bandaid and we don't
want to encourage the use of that code, so keeping it close the few
spots where it is still necessary might make better sense.

I can't remember. Is there a dash in "overthinking"? :-)

> Here's the updated patch, which I think addresses all review comments.

I'll try to review the patch again, but you should feel free to
push it anytime you're ready. I am fairly busy at the moment :-(.

Thanks, Tom!
-- 
Joel


  reply	other threads:[~2014-05-21 18:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 18:47 [PATCH 0/2] " Tom Tromey
2014-05-08 18:47 ` [PATCH 1/2] minor cleanups in is_dynamic_type Tom Tromey
2014-05-08 18:47 ` [PATCH 2/2] handle VLA in a struct or union Tom Tromey
2014-05-08 19:01   ` pinskia
2014-05-08 19:07     ` Tom Tromey
2014-05-08 20:30     ` Philippe Waroquiers
2014-05-08 21:32       ` Tom Tromey
2014-05-08 21:09   ` Joel Brobecker
2014-05-08 21:33     ` Tom Tromey
2014-05-08 22:38       ` Joel Brobecker
2014-05-09 15:57         ` Joel Brobecker
2014-05-21 17:28           ` Tom Tromey
2014-05-21 18:24             ` Joel Brobecker [this message]
2014-05-21 22:02             ` Joel Brobecker
2014-05-21 22:28               ` Tom Tromey
2014-06-04 20:27               ` Tom Tromey
2014-05-09  8:05   ` Agovic, Sanimir
2014-05-09 21:08     ` Tom Tromey
2014-05-12 15:37       ` Agovic, Sanimir
2014-05-12 17:00         ` Tom Tromey
2014-05-13  7:53           ` Agovic, Sanimir

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=20140521182411.GM22822@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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