a couple of my F.A.Q. (please read)

I have a couple of quetions that i always wondered about. You posters seem nice and I was wondering if you could answer them.

1)
My C++ book uses #include <iostream>
While others use #include <iostream.h>

what is the difference if the .h is or isn't there?

2)
Is there a website where I can read about all of the most common libraries and what they do and common functions they hold with examples?
Like, i would like to know the common <windows.h> functions that it has.

3)
Do i put the library files in the same file as my *.cpp source-code?



that's it. thanks for reading =))

#include <iostream> -->new style
#include <iostream.h>-->old style

nothing changes take one and use it
(.h means that it is a hearder file)

2-)most used functions are covered at this web site go for it

3-)do not touch the .h files they are maintaned by the compiler

2) check out MSDN, it is the begin all and end all

3) Do you mean where you include them? Or are you planning on making some?

Quote:

---

Originally posted by onurak
#include <iostream> -->new style
#include <iostream.h>-->old style

---

This is the way I understand it also, but the non-.h version uses the namespace std. I think I remember not having to do any std stuff when using <iostream.h>

Is that right people? I've been Windows coding for so long I don't remember my console stuff

Yep.

>I think I remember not having to do any std stuff when using <iostream.h>
Old C++ didn't support namespaces, they are a relatively new addition.

>what is the difference if the .h is or isn't there?
Another note should be that the old style is deprecated and support for it may be removed from the standard in the near future.

>Do i put the library files in the same file as my *.cpp source-code?
It depends on what you mean by library files.

-Prelude

By library do you mean a library of commonly used functions that me or someone i work with has put together? Or do you library like a library file (.lib)? I'll assume you mean the first one. I used to do that but found that is better practice not to. You should just make another include directory for your own stuff.