Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@sebabeach.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: 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:11:00 -0000	[thread overview]
Message-ID: <m3ppqcbsdz.fsf@seba.sebabeach.org> (raw)
In-Reply-To: <527AB482.80600@earthlink.net> (Stan Shebs's message of "Wed, 06	Nov 2013 13:28:34 -0800")

Stan Shebs <stanshebs@earthlink.net> writes:

> On 11/6/13 9:00 AM, Doug Evans wrote:
>> Hi.
>> 
>> There's nothing python-specific about the bulk of this code so I've
>> moved it out of py-type.c.
>> 
>> Ok to check in?
>> 
>> 2013-11-06  Doug Evans  <dje@sebabeach.org>
>> 
>>         * gdbtypes.c: #include bcache.h, dwarf2loc.h.
>>         (type_equality_entry): Move here from python/py-type.c.
>>         (type_equality_entry_d): Ditto.
>>         (compare_maybe_null_strings, check_types_equal): Ditto.
>>         (check_types_worklist, types_deeply_equal): Ditto.
>>         * gdbtypes.h (types_deeply_equal): Declare.
>>         * python/py-type.c: Remove inclusion of bcache.h, dwarf2loc.h.
>>         (typy_richcompare): Update.
>> 
>
> +/* A helper function for tyscm_richcompare that checks two types for
> +   "deep" equality.  Returns non-zero if the types are considered the
> +   same, zero otherwise.  */
>
> "tyscm_richcompare"?  Should that be typy_... ?

Heh.

> The comments should be maybe be phrased to emphasize the
> quasi-librariness of the code, so that future generations aren't
> confused if it seems unused by core GDB (which could happen if python
> becomes plugin
> instead of subdir, for example).

Agreed.


  parent reply	other threads:[~2013-11-07  7:10 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
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 [this message]
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=m3ppqcbsdz.fsf@seba.sebabeach.org \
    --to=dje@sebabeach.org \
    --cc=gdb-patches@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /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