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/112199.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)Nick Coghlan ncoghlan at gmail.com
Mon Jul 4 05:44:59 CEST 2011
On Mon, Jul 4, 2011 at 12:54 PM, Benjamin Peterson <benjamin at python.org> wrote:
> 2011/7/3 Nick Coghlan <ncoghlan at gmail.com>:
>> 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?

I didn't check - was this change in a static function? For those, I
think they can figure it out. For functions exposed to the linker, I
think they demand an explicit check for a non-NULL pointer (which may
be in the form of an assertion).

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
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