A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-March/034010.html below:

[Python-Dev] PyObject_New vs PyObject_NEW

[Python-Dev] PyObject_New vs PyObject_NEW [Python-Dev] PyObject_New vs PyObject_NEWDavid Abrahams dave@boost-consulting.com
Thu, 13 Mar 2003 08:00:24 -0500
Thomas Heller <theller@python.net> writes:

> David Abrahams <dave@boost-consulting.com> writes:
>
>> Thomas Heller <theller@python.net> writes:
>>=20
>> >> I don't think the macro versions should ever be used outside the core.
>> >> Inside the core, it's safe.  So I think the "doc bug" is that the docs
>> >> mention PyObject_NEW at all.
>> >>=20
>> >
>> > Better to expl=EDcitely warn about them with a wording similar to that
>> > from the section 9.2 Memory Interface:
>>=20
>> I'm not in a position to decide which one of these is better.  Thomas,
>> maybe you should be submitting the patch?
>
> Nor am I. You can submit a patch as well, and the discussion will show.
>
> Sorry, no time.

Fair enough; Tim's patch was much easier ;-)

--=20
Dave Abrahams
Boost Consulting
www.boost-consulting.com




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4