From: Doug Evans <dje@sebabeach.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Stan Shebs <stanshebs@earthlink.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Move "types deeply equal" code from py-type.c to gdbtypes.c
Date: Thu, 07 Nov 2013 07:17:00 -0000 [thread overview]
Message-ID: <m3li10bsbj.fsf@seba.sebabeach.org> (raw)
In-Reply-To: <87ppqd1a0t.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 06 Nov 2013 14:43:30 -0700")
Tom Tromey <tromey@redhat.com> writes:
> Stan> +/* A helper function for tyscm_richcompare that checks two types for
> Stan> + "deep" equality. Returns non-zero if the types are considered the
> Stan> + same, zero otherwise. */
>
> Stan> "tyscm_richcompare"? Should that be typy_... ?
>
> It would be helpful if Doug could list all the change he made when
> moving the code.
I don't understand.
Which changes? While useful beyond its present state, this is in
essence just a cleanup.
next prev parent reply other threads:[~2013-11-07 7:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 17:10 Doug Evans
2013-11-06 21:35 ` Stan Shebs
2013-11-06 21:50 ` Tom Tromey
2013-11-07 7:17 ` Doug Evans [this message]
2013-11-07 14:53 ` Tom Tromey
[not found] ` <CAA8o+=T2a8WLE8zi1NO=u8B460KmwOvA2m2pzVJCkAsXw6vHBw@mail.gmail.com>
2013-11-09 19:50 ` Doug Evans
2013-11-09 19:55 ` Doug Evans
2013-11-09 20:33 ` Doug Evans
[not found] ` <CAP9bCMQa7g0vupyHKwmZKum1QJDToDL7bCj92Sc6xbV9R71KGg@mail.gmail.com>
2013-11-17 19:34 ` Doug Evans
2013-11-22 7:40 ` Doug Evans
2013-11-07 7:11 ` Doug Evans
2013-11-07 10:19 ` Publishing binary interfaces [was Re: [PATCH] Move "types deeply equal" code from py-type.c to gdbtypes.c] Doug Evans
2013-11-11 18:59 ` Tom Tromey
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=m3li10bsbj.fsf@seba.sebabeach.org \
--to=dje@sebabeach.org \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
--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