Path: utzoo!utgpu!watserv1!watmath!att!rutgers!usc!elroy.jpl.nasa.gov!decwrl!infopiz!lupine!rfg From: rfg@NCD.COM (Ron Guilmette) Newsgroups: comp.bugs.sys5 Subject: Re: Annoying prototypes for execv* functions in V.4 Message-ID: <3656@lupine.NCD.COM> Date: 2 Feb 91 23:09:20 GMT References: <3598@lupine.NCD.COM> <1991Jan31.174039.17973@cbnewsl.att.com> Organization: Network Computing Devices, Inc., Mt. View, CA Lines: 28 In article <1991Jan31.174039.17973@cbnewsl.att.com> sethr@cbnewsl.att.com (seth.r.rosenthal) writes: +In article <3598@lupine.NCD.COM>, rfg@lupine.ncd.com (Ron Guilmette) writes: +> If you use and/or sell System V Release 4 you may want to fix up your +> file. +> +> It probably contains: +> +> extern int execv(const char *, char *const *); +> extern int execve(const char *, char *const *, char *const *); +> extern int execvp(const char *, char *const *); +> + +These prototypes come right out of 1003.1-1990. That +is why they are in SVR4. I stand corrected. Apparently there *is* some POSIX document that says that those prototypes are correct. Now if somebody would just tell me where I can get a copy of this mythical document... Is it a draft or an approved document? What's its ISBN #? -- // Ron Guilmette - C++ Entomologist // Internet: rfg@ncd.com uucp: ...uunet!lupine!rfg // Motto: If it sticks, force it. If it breaks, it needed replacing anyway.