From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Strings and arrays without malloc
Date: Thu, 13 Mar 2008 16:22:00 -0000 [thread overview]
Message-ID: <1205425296.6643.93.camel@localhost.localdomain> (raw)
In-Reply-To: <m3tzja4tc7.fsf@fleche.redhat.com>
On Thu, 2008-03-13 at 08:00 -0600, Tom Tromey wrote:
> But, the problem with object mappings like this is that managing the
> lifetime of the objects in the scripting language can be a pain. I'm
> not really a gdb expert so I don't know how difficult this will be in
> practice.
Well, at least Python seems to have well documented and established
conventions on reference counting and ownership, so hopefuly we won't
make too much of a mess out of it.
> Thiago> I think there are lots of eyes on this Python support thing,
> Thiago> including mine. :-)
>
> Thiago> I'm starting to put some hands on it too, FWIW.
>
> Let's set up a branch or make a git repository or something like that.
> What works for you?
A git repo would work. I personally prefer mercurial or bazaar,
but git is fine by me.
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
next prev parent reply other threads:[~2008-03-13 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 16:14 Daniel Jacobowitz
2008-03-09 22:20 ` Eli Zaretskii
2008-03-11 6:58 ` Tom Tromey
2008-03-13 6:12 ` Tom Tromey
2008-03-13 14:16 ` Thiago Jung Bauermann
2008-03-13 14:54 ` Tom Tromey
2008-03-13 16:22 ` Thiago Jung Bauermann [this message]
2008-03-13 16:59 ` Tom Tromey
2008-03-13 20:47 ` Tom Tromey
2008-03-13 19:22 ` Joel Brobecker
2008-03-21 15:03 ` 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=1205425296.6643.93.camel@localhost.localdomain \
--to=bauerman@br.ibm.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