Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@sebabeach.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Stan Shebs <stanshebs@earthlink.net>,
	gdb-patches@sourceware.org, xdje42@gmail.com
Subject: Re: [PATCH] Move "types deeply equal" code from py-type.c to gdbtypes.c
Date: Sat, 09 Nov 2013 19:50:00 -0000	[thread overview]
Message-ID: <CAA8o+=RBU=AkLmW=Q+J16jZgJZ-Fpp8nPajK-FDH-AyrEJgQyQ@mail.gmail.com> (raw)
In-Reply-To: <CAA8o+=T2a8WLE8zi1NO=u8B460KmwOvA2m2pzVJCkAsXw6vHBw@mail.gmail.com>

On Thu, Nov 7, 2013 at 8:40 AM, Doug Evans <dje@sebabeach.org> wrote:
> On Thu, Nov 7, 2013 at 6:36 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>>> "Doug" == Doug Evans <dje@sebabeach.org> writes:
>>
>> Doug> 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.
>>
>> Doug> I don't understand.
>> Doug> Which changes?  While useful beyond its present state, this is in
>> Doug> essence just a cleanup.
>>
>> I had thought this patch was more or less a straight move of the code.
>> But Stan's note revealed a change from what is currently in the tree.
>> So the question is, can you say what else changed?
>> That would be handy so I don't have to go over it line-by-line myself.
>
> Ah.  Except for the comment (*1) the only substantive change is in the result:
> Py_{NE,EQ} -> 0.1.
>
> (*1): Early on I made a copy because I wasn't sure how things would end up,
> and left in a FIXME to remind myself to revisit.
> I revisited and realized there's no need for the copy, but missed the
> comment.  Blech.
> "diff -b before after" shows nothing of note to me.

Here's v2 of the patch.

I fixed the comment and added an assert to check type1,type2 != NULL.

I changed the email address in the ChangeLog entry 'cus I'm having
problems with this domain.
After this email hopefully the switchover is complete.


  parent reply	other threads:[~2013-11-09 19:48 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 [this message]
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='CAA8o+=RBU=AkLmW=Q+J16jZgJZ-Fpp8nPajK-FDH-AyrEJgQyQ@mail.gmail.com' \
    --to=dje@sebabeach.org \
    --cc=gdb-patches@sourceware.org \
    --cc=stanshebs@earthlink.net \
    --cc=tromey@redhat.com \
    --cc=xdje42@gmail.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