No, it's just some self-homework in my Operating Systems class I took in the spring. I didn't do as well as I had wanted to, so I'm trying to work on that now by working out the homeworks and trying...

OKay, this is in response to the same issues I've been dealing with in another thread.

In that one, someone gave me the documentation to the the POSIX calls, but they were vague and weren't too...

The UNIX equivalent to Win32 API is POSIX.

"With UNIX, there is almost a 1-to-1 relationship between the system calls (e.g., read) and the library procedures (e.g., read) used to invoke the system...

Thanks, I still don't have it figured out, but here's what I have thus far:

int main(int argc, char *argv[], char **envp)
{
type_prompt();
puts("Give me input numbers, each separated by...

How do I read up on exec? What, man exec in the terminal? I think I tried it with fork and it didn't work on my Debian Distro.

Oh, and by the way, I used unistd.h and it didn't change the warning at all.

I appreciate the help thus far, but what exactly is "unistd.h."? What does this library allow me to do?
And, what is the meaning of error " undefined reference to exec"?

Thanks Ancient Dragon. I think, however, that I'll keep my code the way it is until I'm sure that it works.

For right now, I'm wondering why I have the warnings for the following pieces of code:

Yes, you're right. I changed the code:
int main(int argc, char **argv)
{
int sum;
sum = atoi(*(++argv));
sum = atoi(*(++argv));
}

Take the following code:
#include <stdlib.h>


int main(int argc, char **argv, char **envp)
{
int sum;
atoi(&argv[1]);//statement with no effect. Passing argument 1 of ‘atoi’ from...