You need the first two because they give you access to the core C++ IO manipulation functions (cin, cout, etc).

that's just simple math and making sure you point the correct question to the correct equation.. math is the same in every language.. there's no fancy way to do math, that's why if aliens landed on our planet you show them the fucking pythagorean theorem and they'll be like oh fuck these monkeys aren't that fucking stupid afterall

Then they show you the math behind quantum mechanics and they be like "wtf these apes are dumb."

OMG. Hahahaha I was just thinking to myself as I read his code. "Hmm. No comments, no && operators, no knowledge of float, int, double, long, etc. Oh man..."



Oh man. You should be in a basic course bud. Not sure who taught you but they didn't give you any fundamentals it seems.
Read this:
STARTING OUT WITH C++ From Control Structures through Objects SEVENTH EDITION

http://www.amazon.com/s/?ie=UTF8&keywords=starting+out&tag=googhydr-20&index=stripbooks&hvadid=19931788157&hvpos=1t2&hvexid=&hvnetw=s&hvrand=13867330391977755615&hvpone=&hvptwo=&hvqmt=b&hvdev=c&ref=pd%5Fsl%5F92zzw19zud%5Fb

It goes through all the basics very well. To answer your original questiom: int is short for integer, float for floating precision point, double for double floating precision point, char is character. IIRC it is 8 bits or 1 byte of data. I think it is the smallest unit in C++ but I could be wrong.**



Also:

• Integers are at least as big as short integers.
• Long integers are at least as big as integers.
• Unsigned short integers are the same size as short integers.
• Unsigned integers are the same size as integers.
• Unsigned long integers are the same size as long integers.

In stead of const you can use #define for keep a variable from being modified.



The #include <iostream> is a preprocessor directive. It goes before the compiler and inputs all the data from the directive. It's much like calling a library in Java. It instead of writing the crap load of code it takes to do a cout//cin, etc. (By the way cout stands for console back when people typed on terminals to access consoles.) Same with <stings>, etc.; they are called header files. Hence they go at the head of the file.
iostream, string, etc. is also the name of the file being called forth into the source code.

Well I am tired and that is enough of that today.

Edit:: Left a sentence half written.**

This post was edited by NinjaSushi2 on Feb 14 2014 11:08pm

He's learning.




He is in a basic course.



This one made my head hurt. Don't do this. The only benefit to doing this over declaring constants is you save a bit of memory not having to allocate memory for each variable stored on the names table. The preprocessor just replaces the define with the literal. You sacrifice scope capabilities though. If you don't need global scope for a variable, you should not be using #define. In fact, saying you should replace const with #define as a rule of thumb is just a bad idea.



It is nothing like calling a library in Java. The preprocessor literally just replaces the #include with the contents of the file. This happens before compilation, so the compiler just sees 1 source file after the preprocessor does its parsing. The java import statement just tells the compiler where to look for external classes. They are 2 different operations.


cout represents the standard output stream. It stands for C OUTput stream. And it doesn't just print to a console. It prints to the designated default output stream, which by default is the console. But it can be set to log, err, a file, etc.



They aren't called headers because they go in the beginning (hint: they dont have to go at the top of the file). They are called headers because they precede the actual implementation. Headers are things typically "describe" how to read/operate something. In the case for C++ they typically contain function declarations. The actual implementations of these functions will be in the main cpp file, which will then #include the header to grab the declarations.It allows for multiple implementations of the same interface to exist. Again, all the preprocessor does is take the contents of one file and paste it where the #include was. There is no rule that says this must go at the "head" of the file.


Don't bag on the kid because he is learning, especially when you have a lot to learn as well..

+1 Minkomonster

It's simple, our space ship turns into light and goes light speed * 500

thus it is fast

mad?

Hey now. Who you callin' Tachyons ?

Hmm interesting read.

I never said use the #define as a replacement for const, I said you can use it in placement of const. He should know that as some older programs written still use #define.

The java reference was a poor comparison, you are correct.

Regarding cout:



That is how I learned cout at least. Console OUTput as a learning tool because it makes more sense that way.

Obviously there is no rule that says it has to go at the top of the file. Nor did I said you couldn't place it anywhere else as a preprocessor super-ceeds any other code written. It's written at the top of the file because that is good programing. Same with putting comment lines through your program and having your program open with a comment. Such as the name of the programer who wrote it, last date modified, what the file/program does, etc.

You are right though. It was wrong to laugh, my bad.

Thanks for correcting me on anything.

This post was edited by NinjaSushi2 on Feb 15 2014 06:02am