Re: C portability is a myth
From: Randy Howard (randyhoward_at_FOOverizonBAR.net)
Date: 02/26/05
- Next message: Keith Thompson: "Re: where does cc send the output by default"
- Previous message: Alan Connor: "Re: can I know how to write a html parser in C"
- In reply to: infobahn: "Re: C portability is a myth"
- Next in thread: infobahn: "Re: C portability is a myth"
- Reply: infobahn: "Re: C portability is a myth"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 26 Feb 2005 08:13:01 GMT
In article <422018FD.38FC99FF@btinternet.com>,
infobahn@btinternet.com says...
> RETURN VALUE
>
> The value returned is -1 on error (e.g. fork failed), and the return
> status of the command otherwise. This latter return status is in the
> format specified in wait(2). Thus, the exit code of the command will
> be WEXITSTATUS(status). In case /bin/sh could not be executed, the
> exit status will be that of a command that does exit(127).
>
> CONFORMING TO
> ANSI C, POSIX.2, BSD 4.3
> (etc)
>
> The implication of the man page is that /bin/sh -c, SIGCHLD, SIGQUIT,
> wait, WEXITSTATUS, and the semantics of the return status, are all
> defined by ANSI.
Not to mention fork(). I knew somebody would find a man page
showing the other side. What I am surprised by is the way the
role of the usual MS bashers and Linux bashers seem to be
reversed in this. :-)
-- Randy Howard (2reply remove FOOBAR) "Making it hard to do stupid things often makes it hard to do smart ones too." -- Andrew Koenig
- Next message: Keith Thompson: "Re: where does cc send the output by default"
- Previous message: Alan Connor: "Re: can I know how to write a html parser in C"
- In reply to: infobahn: "Re: C portability is a myth"
- Next in thread: infobahn: "Re: C portability is a myth"
- Reply: infobahn: "Re: C portability is a myth"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|