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

Showing content from https://mail.python.org/pipermail/python-dev/2002-September/028627.html below:

Two random and nearly unrelated ideas)

• Previous message: [Python-Dev] Re: Signal-resistant code (was: Two random and nearly unrelated ideas)
• Next message: [Python-Dev] Re: Signal-resistant code (was: Two random and nearly unrelated ideas)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Oren Tirosh wrote:
> If this macro is defined you will never get EINTR so there's no need to
> worry about this. If it isn't defined you need to restart system calls 
> yourself.

I don't think that is correct.  Only certain systems calls will be
restarted (for BSD 4.2 it's ioctl, read, readv, write, writev, wait, and
waitpid).  I think the system calls restarted varies depending on the
OS.

Signals are a gigantic mess.  I'm starting to doubt that you realize the
extent of the brain damage.  While I would be pleased if there was some
way Python could hide the mess, I'm not convinced it is possible.

  Neil

• Previous message: [Python-Dev] Re: Signal-resistant code (was: Two random and nearly unrelated ideas)
• Next message: [Python-Dev] Re: Signal-resistant code (was: Two random and nearly unrelated ideas)
• 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