Re: [jamboost] Use of _exit() in execunix.c?

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-07-29 04:32:21

Hi Craig,
>
> Maybe this was there before and I just never paid attention to it.
> I recently did a cvs update and compiled bjam
> on MacOS X 10.4 and saw this compiler warning:
>
> execunix.c: In function 'execcmd':
> execunix.c:153: warning: incompatible implicit declaration of built-in
> function '_exit'
>
>
> _exit() is defined in <unistd.h>.
> Can we unconditionally include <unistd.h> in this file? <unistd.h>
> is a fairly standard Unix header file.

Thanks, applied!

BTW, anybody has any idea why the code in question:

if ((pid = vfork()) == 0) 
{
execvp( argv[0], argv );
_exit(127);
}

uses "_exit" and not "exit"? The only difference is that _exit does not invoke
"atexit" functions. Everywhere else, "exit" is used.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2