use restrict everywhere it's required by c99 and/or posix 2008

to deal with the fact that the public headers may be used with pre-c99
compilers, __restrict is used in place of restrict, and defined
appropriately for any supported compiler. we also avoid the form
[restrict] since older versions of gcc rejected it due to a bug in the
original c99 standard, and instead use the form *restrict.
This commit is contained in:
Rich Felker
2012-09-06 22:44:55 -04:00
parent bac03cdde1
commit 400c5e5c83
192 changed files with 552 additions and 382 deletions

View File

@ -1,15 +1,15 @@
#include <spawn.h>
#include <unistd.h>
int __posix_spawnx(pid_t *, const char *,
int __posix_spawnx(pid_t *restrict, const char *restrict,
int (*)(const char *, char *const *),
const posix_spawn_file_actions_t *,
const posix_spawnattr_t *, char *const [], char *const []);
const posix_spawnattr_t *restrict, char *const *restrict, char *const *restrict);
int posix_spawnp(pid_t *res, const char *file,
int posix_spawnp(pid_t *restrict res, const char *restrict file,
const posix_spawn_file_actions_t *fa,
const posix_spawnattr_t *attr,
char *const argv[], char *const envp[])
const posix_spawnattr_t *restrict attr,
char *const argv[restrict], char *const envp[restrict])
{
return __posix_spawnx(res, file, execvp, fa, attr, argv, envp);
}