Why does getpid() return pid

What's the logic behind calls like getpid() returning a value of type pid_t instead of an unsigned int? Or int? How does this help?

I'm guessing this has to do with portability? Guaranteeing that pid_t is the same size across different platforms that may have different sizes of ints etc.?

Is pid_t the same as int?

The pid_t data type is a signed integer type which is capable of representing a process ID. In the GNU library, this is an int .

What is the return value of getpid () when called from a parent process?

The getpid() function returns the process ID of the calling process. The getpgrp() function returns the process group ID of the calling process.

Can I use int for PID?

Using int is probably not a good idea since it would not support hypothetical future implementations with 64-bit pids.

I think it's the opposite: making the program portable across platforms, regardless of whether, e.g., a PID is 16 or 32 bits (or even longer).

Why does getpid() return pid_t instead of int?

Tags:

c

pid

type-equivalence

ntl0ve

People also ask

1 Answers

zvrba

Recent Activity

Donate For Us