From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix python-interactive with Python 3.6
Date: Fri, 20 Jan 2017 16:51:00 -0000 [thread overview]
Message-ID: <323655f5-12bb-4245-0833-f38d94e63312@redhat.com> (raw)
In-Reply-To: <5989286b709d1361c8bc9062567ffedf@polymtl.ca>
On 01/20/2017 04:48 PM, Simon Marchi wrote:
> Yeah, I thought about that and concluded it would be a problem for my
> grandchildren ;).
>
;-)
> ... and this is cleaner anyway. But why not just
>
> #if python < 3.4
> #define PyMem_RawMalloc PyMem_Malloc
> #endif
>
> ?
Because I was just copy/pasting from python-internal.h
and didn't really think. :-) The other instances in
python-internal.h do it like that because they need to
redefine a symbol, not just define something missing.
Thanks,
Pedro Alves
prev parent reply other threads:[~2017-01-20 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 15:19 Simon Marchi
2017-01-20 15:38 ` Simon Marchi
2017-01-20 16:37 ` Pedro Alves
2017-01-20 16:49 ` Simon Marchi
2017-01-20 16:51 ` Pedro Alves [this message]
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=323655f5-12bb-4245-0833-f38d94e63312@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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