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-December/041292.html below:

[Python-Dev] Re: python/dist/src/Objectsunicodeobject.c, 2.204, 2.205

[Python-Dev] Re: python/dist/src/Objectsunicodeobject.c, 2.204, 2.205Tim Peters tim.one at comcast.net
Sat Dec 20 21:52:03 EST 2003
[Skip Montanaro]
> Isn't that supposed to always be defined in limits.h or is UCHAR_MAX
> not a standard macro?

Yes, it's supposed to be there.  OTOH, so is limits.h, i.e. the
HAVE_LIMITS_H test shouldn't be necessary either.  So they're just sanity
checks.  But you're right, if UCHAR_MAX isn' defined, I was thinking the
preprocessor would expand

#if UCHAR_MAX != 255

to

#if != 255

and then the error message would be incomprehensible.  But unknown names in
preprocessor conditionals actually get replaced by 0, and

#if 0 != 255

does just as well.

> Sounds like a plan.  I modify my local source and see if it affects
> anything.

It should work fine.


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