[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Checking executability for asynchronous commands
From: |
Markus Elfring |
Subject: |
Re: Checking executability for asynchronous commands |
Date: |
Tue, 29 Dec 2020 14:28:15 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 |
>…, is not a winning argument.
I got further development ideas according to the usage of wait function calls
and better error reporting for asynchronous commands.
>The OP seems to think that "people will occasionally forget to run `wait`",
This happens for various reasons.
> and wants to know if we "care" that people will forget …
The attention varies for this implementation aspect.
> Why should we care?
Would you like to care for proper management of system resources
(including process identifications)?
>The official advice is to run `wait`
How do you think about any additional guidance for such a programming interface?
Regards,
Markus
- Re: Checking executability for asynchronous commands, (continued)
- Re: Checking executability for asynchronous commands, Eli Schwartz, 2020/12/28
- Re: Checking executability for asynchronous commands, Léa Gris, 2020/12/28
- Re: Checking executability for asynchronous commands, Eli Schwartz, 2020/12/28
- Re: Checking executability for asynchronous commands, Chet Ramey, 2020/12/29
- Re: Checking executability for asynchronous commands, Eli Schwartz, 2020/12/29
- Re: Checking executability for asynchronous commands, Chet Ramey, 2020/12/27
- Re: Checking executability for asynchronous commands, Markus Elfring, 2020/12/28
- Re: Checking executability for asynchronous commands, Chet Ramey, 2020/12/29
- Re: Checking executability for asynchronous commands, Robert Elz, 2020/12/29
Re: Checking executability for asynchronous commands, Dale R. Worley, 2020/12/28
Re: Checking executability for asynchronous commands,
Markus Elfring <=