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/2011-July/112198.html below:

no one passes NULL here (or should anyway)

[Python-Dev] [Python-checkins] cpython: no one passes NULL here (or should anyway) [Python-Dev] [Python-checkins] cpython: no one passes NULL here (or should anyway)Benjamin Peterson benjamin at python.org
Mon Jul 4 04:54:23 CEST 2011
2011/7/3 Nick Coghlan <ncoghlan at gmail.com>:
> On Mon, Jul 4, 2011 at 8:02 AM, benjamin.peterson
> <python-checkins at python.org> wrote:
>> http://hg.python.org/cpython/rev/bbbeddafeec0
>> changeset:   71160:bbbeddafeec0
>> user:        Benjamin Peterson <benjamin at python.org>
>> date:        Sun Jul 03 17:06:32 2011 -0500
>> summary:
>>  no one passes NULL here (or should anyway)
>>
>> files:
>>  Python/ceval.c |  3 ---
>>  1 files changed, 0 insertions(+), 3 deletions(-)
>>
>>
>> diff --git a/Python/ceval.c b/Python/ceval.c
>> --- a/Python/ceval.c
>> +++ b/Python/ceval.c
>> @@ -1115,9 +1115,6 @@
>>
>>  /* Start of code */
>>
>> -    if (f == NULL)
>> -        return NULL;
>> -
>
> May need to replace that with an assert(f != NULL) to keep static
> analysers happy.

Surely static analyzers don't assume every argument passed in is NULL?


-- 
Regards,
Benjamin
More information about the Python-Dev mailing list

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