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/2006-March/062410.html below:

[Python-Dev] About "Coverity Study Ranks LAMP Code Quality"

[Python-Dev] About "Coverity Study Ranks LAMP Code Quality"Tim Peters tim.peters at gmail.com
Wed Mar 15 08:43:37 CET 2006
[Neal Norwitz]
> ...
> The public report says 15, but the current developer report shows 12.
> I'm not sure why there is a discrepancy.  All 12 are in ctypes which
> was recently imported.

I'm having a really hard time making sense of the UI on this.  When I
looked at the Python project just now (I can log in, so guess that's
what you called the "developer report" above), I see 13 "error" rows,
and none of them referencing ctypes.  OTOH, maybe you'd count this as
zero rows, since there are none left with BUG or UNINSPECTED status.

I dug into one of them, a claim by the tool that after marshal.c's:

    int one = 1;
    int is_little_endian = (int)*(char*)&one;

we have:

    Event const: After this line, the value of "is_little_endian" is equal to 1

but of course that's not so on a big-endian box, and it goes on to
claim that there's dead code because of this.

I'm not much inclined to look at more of these -- I probably waited so
long that all we have left are false positives?  If not, and somebody
wants me to look at one, point it out specifically ;-)
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