Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2000-August/008514.html below:

typedef ??? pthread_t and hacky return statements

• Previous message: [Python-Dev] pthreads question: typedef ??? pthread_t and hacky return statements
• Next message: [Python-Dev] pthreads question: typedef ??? pthread_t and hacky return statements
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[/F]
> from what I can tell, it's compatible with a long on all sane plat-
> forms (Win64 doesn't support pthreads anyway ;-), so I guess the
> right thing here is to remove volatile and simply use:
>
>     return (long) threadid;

That's what the code originally did, and the casting was introduced in
version 2.5.  As for the "volatile", Vladimir reported that he needed that.

This isn't worth the brain cell it's getting.  Put in the hack and move on
already!

• Previous message: [Python-Dev] pthreads question: typedef ??? pthread_t and hacky return statements
• Next message: [Python-Dev] pthreads question: typedef ??? pthread_t and hacky return statements
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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