process creation in c++

lemon09 · 01-17-2014, 08:17 AM

Well, in C we have functions like fork() and exec() to create a separate process from within a program. The header files that they use is

Code:

#include <unistd.h>

Now, the question is - what is the C++ equivalent of this code. Do we have separate functions for these or they are just the same in C++. Also that C++ uses its own style headers, like:

Code:

#include <iostream>

followed by the namespace to use. For process creation in C++ do we have such header files and namespaces??

Any tutorial with proper examples would be appreciated. Thanks!!!!

rtmistler · 01-17-2014, 09:38 AM

You can do that exact same things in C++ that you can do with C in invoking fork() and exec(). I do this all the time. I also however do include <unistd.h> in that form in a C++ program.

lemon09 · 01-17-2014, 01:55 PM

Yes, I know that I can do it in the same way we do in C. But my question was - is there any specific way of doing this in C++ which is a bit different from C?

dwhitney67 · 01-17-2014, 04:38 PM

Quote:

Originally Posted by lemon09

Yes, I know that I can do it in the same way we do in C. But my question was - is there any specific way of doing this in C++ which is a bit different from C?

No. (which makes you wonder why anyone would every bother developing in C, unless they are relegated to using a puny compiler for a specific microprocessor).

rtmistler · 01-17-2014, 09:46 PM

Quote:

Originally Posted by lemon09

Yes, I know that I can do it in the same way we do in C. But my question was - is there any specific way of doing this in C++ which is a bit different from C?

Possibly, but none that I in know of. I'm thinking that pretty much most Linux library functions are written in C, as is the kernel; hence to me it's best to stick with the C implementation. And further, wouldn't a C++ implementation risk being not better but instead worse because it would be a rewrite of an already existing proven function? What particular aspect of C++ would you think could improve fork() as it stands today? Granted one could create a higher order fork() function with overloads, but what would you suggest?

bigearsbilly · 01-19-2014, 01:54 PM

C++ could improve fork best if it uses it to disappear up it's own backside

rtmistler · 01-20-2014, 07:14 AM

Quote:

Originally Posted by bigearsbilly

C++ could improve fork best if it uses it to disappear up it's own backside

Joking? Or did you mean something like automatically monitoring for signals from the child so that it would avoid zombies, or give distinct API's so that people would use signals they might otherwise ignore?