Requesting Assistance

You can do what you are talking about, have one application create a second console window, so you can have one for input and one for output.

That said, it is not a trivial thing to do. In fact it would be a fair bit of work. On windows for example, you could use the Console APIs to accomplish this, but trust me, such a task is not something you probably want to embark on.

Basically what happens in C++ is each application has something called stdin and stdout. These are simply buffers for text input and output. Where the actual text goes is somewhat irrelevant to C++. When you use cout or cin, you are actually writing to or reading from stdin and stdout, at least by default. Problem is, by default a new terminal window means a new process, which means a new cin and cout. You can easily redirect stdout and stdin, say... to a file. But redirecting the results to another running application is much more complicated involving cross-process communications of some form, such as a pipe.

Alright.... Going to look up how to do that, and implement it.... Man this drill has no idea what's coming for it! Thanks!

Well if you are a glutton for punishment, and working on Windows, start here. The trickiest part is, your console application is going to actually be a Windows application behind the scenes. The logististics of what that actually means can prove a bit confusing, beyond the fact one type of application has a main() and the other has a WinMain() entry point. It should prove an interesting learning experience, although I warn you Alice, this rabbit hole is deep, dark and kinda scary.

EDIT:

You can probably go the pure console app route using spawn and a pipe to control communications, that should be more cross platform but perhaps a bit more confusing at the end of the day. This example illustrates using a pipe to communicate between a parent and child process opened using spawnl().

Wouldn't it require working with a window API, like Win32?

I looked up here and I found this old thread. I think it is a good start.

Well, if you manage to do it don't forget to post here how you did it. This is something I had never thought about.

Serapth, I take your warning seriously, however know that Alice isn't afraid of the dark, does not easily scare, and likes long walks in a forest talking about the philosophical problems and solutions related to Chance as a manipulable force.

Kuramayoko10, I will indeed my good sir / ma'am.[sup] [/sup]

Apparently Serapth already answered your question, but to be honest, I don't get it... do you want to have the input requests in a different console than the output? That would, imho, not make it cleaner but totally confusing. Afterall, it's a question and answer game and I would think it's weird to give the answer to someone else than the one who asked me... I'd suggest to delay those pop-up windows until you start with GUI programming (which is not hard at all... take a look at wxwidgets or Qt, for example).

Until then I'd suggest to stick with the "ugliness" of the console and be happy (since you are coming from Java) that cin and cout is so much shorter than System.out.println and

BufferedReader bufferRead = new BufferedReader(new InputStreamReader(System.in));
String s = bufferRead.readLine();

(yeah, I know nowadays, there's the java.io.Console class, but even that is so much more than a simple "cin"...)
;)

P.S.: I really like Java, don't get me wrong, please!

brx, by ugliness, I meant it in a different way than you, I guess.

In the current form of the program, it takes all the inputs and outputs on the same screen, so when it asks you a question, you answer it in that same window, and then it responds, for instance, at the very end of the program, it asks you to say

Yours Sincerely,




However it ends up printing, because of the inputs being saved in the same window

Yours Sincerely,





If the inputs were accepted in a different window, then it would be a lot easier to read, it would make more sense and be overall nicer to the user.

Don't worry, when you reach Chapter 12 you're going to be introduced to graphical user interfaces (GUIs) & graphics :-) Chapter 16 further expands on GUIs.
// BTW, Chapter 12 is available freely: http://www.stroustrup.com/Programming/programming_ch12.pdf

I have the entire book on a PDF, 1285 pages or something like that. It's been great fun. I'm just starting Chapter 3. A lot of this stuff I already knew, from Java, and I just needed to learn how to properly translate my operations into C++. And as someone said previously, It feels a lot better to type cin or cout<< stuff << more stuff << more stuff << final stuff;

Rather than typing System.out.println


I was reading on the pipes, and spawns. And I'm going to keep reading the chapters in this PDF, and if it fails to teach me what I want (Which is simply a new window to take in he inputs and then accept those into the main window, as both in 1 window gets redundant and ugly) I shall (as I have already bookmarked the pages) find other materials to teach myself how to do said thing. I hope to have a working version within a week, that I can reply to this thread and say "Haha! I am pleased with myself! I did it by..."

Thanks to everyone for their replies. This is why I want to be a programmer, so far you are nothing but helpful, as though you want more professionals to communicate and work with.

In terms of the code maybe you could create a function that asks a question and then gets a valid answer. I don't know if that kind of thing is something that you could do yet but it would cut down on some of the clutter there a little. This one's not too bad, but long functions make me scared, lol.

Also, something that may make your life a little easier:

cout << "Have you seen" << " " << friend_name<< " " << "lately?\n";

could just as easily be:

cout << "Have you seen " << friend_name<< " lately?\n";

Unless you're after explicit spacing there, which is fine.

Finally, please enclose code on the forum in source braces. When you're making a post and you want to insert code just click the little red brackety button at the end of the second line of buttons above the text field. It makes it a lot easier to read and has syntax hilighting and stuff:

[source lang="cpp"]cout << "How many times a day do you cin?\n";
int times = 0;
cin >> times;
cout << "Really!? " << times << " times?\nRepeat after me: \"Forgive me console, for I have cin'ed.\"\n";[/source]