OSDev.org

is it possible for a program in C to execute an exe file. ??? ???

system() can be an awfully dangerous call to make, as shell variables can be induced to alter the call... fork() and something from the exec() family (execl() or execv()) are easy and tend to be a wee bit safer

-Erik

Yes, but that's POSIX API, not C. How do you know he's running on a machine with POSIX API, and that he's not interested in portability across platforms?

How is system("notepad.exe"); more portable?

Grrrr.... >:(

For all we know, he might be doing system("MyOtherApp").

Starting a new process can be done with Process.Start(), OpenExec(), StartExecutable(), or execl(), depending on your operating system / support libraries.

But it can be done with system() on any compliant C compiler in any environment.

Candy wrote: How is system("notepad.exe"); more portable?

It isn't. Replacing the string with a header-defined constant (think EDITOR in this case) on the other hand would greatly aid portability...

Being the cross-platform and portability geek, I'll have to side with Solar on this one (surprise, surprise).

since when you two don't agree, eh? *rofl* sometimes it occurs to me to think you are kinda twins or so.

Thanks for the compliment. ;D

I was just thinkin that i could create somthing like multi-threading programs in 'C' usin this system(). but then it would'nt work in DOS if not for the windows start.exe btw in my college they teach us to program using 16-bit compilers..TURBO C.. . How do I use vc++ ?(i've got .NET2003)

rich_m wrote: I was just thinkin that i could create somthing like multi-threading programs in 'C' usin this system(). but then it would'nt work in DOS if not for the windows start.exe

That isn't multithreading, that is batch parallelism.

Multithreading is when several threads cooperate. Your example can't give music.exe any input data beyond command line parameters, and the only output data is the return code. Anything beyond that would have to work with temporary files, and that defeats the whole purpose of multithreading - increased efficiency.

The POSIX function you want to look at is fork()... dunno what it's equivalent is in WinAPI.

Using fork() doesn't qualify as multithreading either. IMO, "multithreading" implies multiple threads in the same process, sharing the same address space.

The Win32 equivalent of fork() is CreateProcess(), more or less. To create threads, the Win32 call is CreateThread(), but if you're using C or C++ you should use _beginthreadex() instead. It's a wrapper for CreateThread() that cleans up C/C++ run-time library bookkeeping structures when the thread terminates.

Solar wrote: That isn't multithreading, that is batch parallelism.

Guess i had the wrong impression of what multithreading meant(i thought it was just running a couple of programs simultaneously), thanks . btw i would like to know of 'a' good tutorial for c,c++ using 32bit compilers, i'm not sure if my request sounds weird, if it does my apologies.

Colonel Kernel is correct, of course - fork() does create a new process, not a new thread - however, that process starts with all the data of the forking process, so you're a big step further than with system().

And I have to admit that I haven't written anything multithreading yet.

Running several programs in parallel, BTW, is called "multitasking" (as opposed to what DOS did).