Thread: Tell me about C/C++

Code::Blocks automatically pauses the execution at the end for you, you don't need that unless compiling or running outside of the IDE

How to I package together my code into an exe or something both windows and macs can open?

Originally Posted by slayer

How to I package together my code into an exe or something both windows and macs can open?

A dos console and unix consoles are completely different. Macs can run windows console programs, you need to compile seperately for mac and windows

Originally Posted by ninja9578

A dos console and unix consoles are completely different. Macs can run windows console programs, you need to compile seperately for mac and windows

Then how do I do it just for windows?

Originally Posted by slayer

Then how do I do it just for windows?

It does that for you

Go to the folder with your Code::Blocks file, then go to bin/Debug. A .exe file should be in there

If you use standard C++, it will compile on any platform with no change in code Firefox compiles on every major platform, using the same code, with very little preprocessor.

"C++ will let you shoot your foot without warning you. In fact, it will even load the gun for you."

~ Allegro User

Ynot. I'll give you an example. If the program asks you to input something, you would put it in. You would get an instant response, and then the terminal window would instantly shut the moment after the new text is displayed. This is not what you want.

It's not that I need it at this level, I don't need any fancy way of closing the program at this level. It is just purely for having it there.

Originally Posted by ninja9578

If you use standard C++, it will compile on any platform with no change in code Firefox compiles on every major platform, using the same code, with very little preprocessor.

There are a lot of things you need system calls for, though, like GUI and scanning directories and such. So Firefox must be using preprocessor directives, or libraries which uses them.

Originally Posted by slash112

Ynot. I'll give you an example. If the program asks you to input something, you would put it in. You would get an instant response, and then the terminal window would instantly shut the moment after the new text is displayed. This is not what you want.

Console programs are normally opened from the terminal, though. And if you do that, then the terminal doesn't close and you'll see the output. It's just if you open it by double clicking on the executable that you won't see the text, but then that's no how the programs are supposed to work. If you want those kinds of programs you need GUI.

Funny thing, I've got C++ as a university subject this year. Of the things we'll learn this year, there was only one thing I haven't done before.

Originally Posted by khh

There are a lot of things you need system calls for, though, like GUI and scanning directories and such. So Firefox must be using preprocessor directives, or libraries which uses them.

I said little preprocessor. I've looked at the Firefox code because I reverse engineered a chunk of it. All of this stuff uses a NPWindow object, almost all of the preprocessor is in there.

Console programs are normally opened from the terminal, though. And if you do that, then the terminal doesn't close and you'll see the output. It's just if you open it by double clicking on the executable that you won't see the text, but then that's no how the programs are supposed to work. If you want those kinds of programs you need GUI.

But stick with the terminal while learning, GUIs can be a pain.

Funny thing, I've got C++ as a university subject this year. Of the things we'll learn this year, there was only one thing I haven't done before.

But I'm sure that you'll learn better technique and optimization techniques that you currently don't know. Assuming the professor is competent, I had a professor in college who was a good C++ programmer in 1995, but he stuck to those techniques, so we were taught no modern designs. C++ coding changes very quickly, if you don't stay on top of it, you can fall behind quickly.

Originally Posted by slash112

system("PAUSE") means that when I run the program, it doesn't close as soon as it finishes. But it lets you close it by pressing any key.

Don't do that
I'm not sure exactly what you mean by "closing" (you mean the terminal window?)
but good programs finish as soon as they're done, and do not hang for user input unnecessarily

Say you release a program that takes input from stdin does something and outputs to stdout, exiting 0 on success and any other value on error, errors get sent to stderr

I would like to be able to say something like

Code:

slash112_program || echo "Error $?"

or

Code:

cat some_file | slash112_program | less

hanging the program for input at the end breaks program flow
anyway....

Originally Posted by slayer

How to I package together my code into an exe or something both windows and macs can open?

You can't (well, you can, but it's way more trouble than it's worth)
Either make the various platform & architecture packages yourself
or the easy route - just release the code
If the program's useful, people will package it up for their platform / architecture of choice

Originally Posted by ninja9578

Code::Blocks automatically pauses the execution at the end for you, you don't need that unless compiling or running outside of the IDE

Yea, which is why I like to add the system ("PAUSE") at the end all the time. Not that it is important when I am just making stupid little things, but I just like to do it anyway.