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/2001-August/017337.html below:

[Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Modules _sre.c,2.63,2.64

[Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Modules _sre.c,2.63,2.64Tim Peters tim@zope.com
Thu, 30 Aug 2001 14:50:15 -0400
>> _sre.c
>> Log Message:
>> Removed unreachable return to silence SGI compiler.
>>
>> !     /* shouldn't end up here */
>> !     return SRE_ERROR_ILLEGAL;
>>   }
>>
>> --- 1141,1145 ----
>>       }
>>
>> !     /* can't end up here */
>>   }

[Fredrik Lundh]
> I hate stuff like this: that line was there to make sure *I* don't
> mess up when developing SRE, not to deal with potentially broken
> compilers or misfired electrons.
>
> isn't there any way to tell the SGI compiler to stop whining about
> this?

I've had better luck x-platform with, e.g.,

    assert(!"can't get here"); /* !string is always false */

In non-debug builds, it vanishes so there's nothing for the compiler to
gripe about; while in debug builds most compilers don't do enough flow
analysis to realize there *is* something to gripe about.

Overall, it would be more useful if SGI compilers in particular produced:

    C00666: Warning: -O may produce buggy code.

after every executable line <wink>.




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