macOS fgets() from command line

gets might be what you're looking for.

Use the predefined variable stdin instead of fp.

toddburch said:

Use the predefined variable stdin instead of fp.

Click to expand...

You need to include stdio.h for stdin and stdout to be available, but otherwise this is the right way to do it.

-Lee

So fgets with stdin is preferred over gets? Just curious, but what's the reasoning?

Edit: nevermind. Found this which explains it.

Yea? And why not use std::cin << mystring;

EDIT: Ah, nvm.

kainjow said:

So fgets with stdin is preferred over gets? Just curious, but what's the reasoning?

Edit: nevermind. Found this which explains it.

Click to expand...

And another link on why gets() is bad: http://faq.cprogramming.com/cgi-bin/smartfaq.cgi?answer=1049157810&id=1043284351

toddburch said:

And another link on why gets() is bad: http://faq.cprogramming.com/cgi-bin/smartfaq.cgi?answer=1049157810&id=1043284351

Click to expand...

I obviously agree that fgets is the right answer here, and the link provided has good information, but:

Termination of another, unrelated program

Click to expand...

This is not really a risk on most modern OSs. Most processes have their own protected memory space now, so one program going crazy should not affect the memory space of others. If a program attaches to a shared memory segment it could easily corrupt that, and that could cause issues for other processes, but in the general case you shouldn't be able to do worse than killing the particular program in which the problem exists. This isn't to downplay the risk, but I think understanding things like this can be important for beginners.

-Lee

Yep, looks like a hold-over from DOS days.