From: Nathan Sidwell <nathan@codesourcery.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
gdb-patches@sourceware.org,
Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: add vector container type
Date: Tue, 11 Jul 2006 18:19:00 -0000 [thread overview]
Message-ID: <44B3EBAA.4010300@codesourcery.com> (raw)
In-Reply-To: <vt24pxoknuu.fsf@theseus.home.>
Jim Blandy wrote:
> "Mark Kettenis" <mark.kettenis@xs4all.nl> writes:
>> If this interface is better, are we going to convert other bits of
>> GDB to use these interfaces?
>
> It's a type-safe form of the common idiom for dynamically resized
> arrays. For me, at least, type safety is a big deal. I definitely
> think we should convert other pieces of GDB to use it.
>
> Is this file modified much from the GCC version? Could GDB and GCC
> share this from libiberty?
IMO it is impractical to share this. GCC requires too much GC-specific
additional bits. That's not to say putting this in libiberty would be a bad
thing, just that GCC couldn't really use that copy.
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
next prev parent reply other threads:[~2006-07-11 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 10:09 Nathan Sidwell
2006-07-10 11:54 ` Mark Kettenis
2006-07-10 12:54 ` Daniel Jacobowitz
2006-07-10 19:59 ` Eli Zaretskii
2006-07-13 18:29 ` Nathan Sidwell
2006-07-13 19:25 ` Eli Zaretskii
2006-07-14 16:23 ` Nathan Sidwell
2006-07-14 19:31 ` Eli Zaretskii
2006-07-17 15:09 ` Nathan Sidwell
2006-07-17 18:07 ` Mark Kettenis
2006-07-17 18:15 ` Daniel Jacobowitz
2006-07-11 18:17 ` Jim Blandy
2006-07-11 18:19 ` Nathan Sidwell [this message]
2006-08-15 19:42 ` Daniel Jacobowitz
2006-09-21 13:48 ` Daniel Jacobowitz
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=44B3EBAA.4010300@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=mark.kettenis@xs4all.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