Martin Oberzalek wrote:
> What I wan't to point out is that in gnulib on WIN32 API pid_t is not a
> process id
> like it is on linux. Functions in gnulib that are using pid_t eg waitpid()
> accepting
> a process handle instead.
Correct.
When an OS offers process handles, instead of pids, we be
Hi Bruno,
> Your email is hardly readable, because
I'm sorry for that. I hope it is fixed now.
> > _spawnvp(), or _wspawnvp() are not returning a pid. It is a process handle.
>
> No one claimed that _spawnvp() is returning a pid.
What I wan't to point out is that in gnulib on WIN32 API pid_t i
Hi Martin,
Your email is hardly readable, because
1. it is a HTML email,
2. when viewing it as plain text - which is the only secure way to read mail
[1] - the cited text is not indented.
Please configure your mailer for plain-text mail [2], if you want to continue
to write to mailing lis
Hi,
Am Montag, den 24.08.2020, 01:30 +0200 schrieb Bruno Haible:
On 64-bit Windows, pid_t needs to be 64-bit large, i.e. intptr_t or 'long
long'or
'__int64'.
This is because the return type of _spawnv* (when invoked with _P_NOWAIT) and
the argument of the _cwait function are 'intptr_t' (se
Hi,
Am Montag, den 24.08.2020, 01:30 +0200 schrieb Bruno Haible:
On 64-bit Windows, pid_t needs to be 64-bit large, i.e. intptr_t or 'long
long'or
'__int64'.
This is because the return type of _spawnv* (when invoked with _P_NOWAIT) and
the argument of the _cwait function are 'intptr_t' (se
On 64-bit Windows, pid_t needs to be 64-bit large, i.e. intptr_t or 'long long'
or '__int64'.
This is because the return type of _spawnv* (when invoked with _P_NOWAIT) and
the argument of the _cwait function are 'intptr_t' (see [1][2]: "The return
value from an asynchronous _spawnvp or _wspawnvp (
