I know there was a previous thread, but there was no clear conclusion to the debate as to if and how it was possible to make MinGW2003 and Dev-C++ work together correctly. There were problems with iostream etc. that prevented simple cin/cout from working.
Anyone have any ideas ?
Thanks,
Greg.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tried a few ways to do just that; and they all worked , the way iam doing it now works fine. ( everything compiles if coded right).
Now as for iostream , i found that gcc 3.2 has a problem with ' iostream.h ', not ' iostream '. Something to do with a renew of the header in 3.2-( Standard C++) ( the .h is not needed, and the compiler i get, kicks it back with a message if you put the .h ).
Second as cout and cin go, if you use them you must do one of two things: ' using namespace std; ' will allow you to write them as just ' cout ' and ' cin '....otherwise !, you will need to write them as: ' std::cout ' and ' std::cin ' ect... in order for them to compile without errors.
Just my personal use of the gcc 3.2 and what i have done, and found from using it.
j@ck_
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
you never use ".h" in your c++ work. This can not be considered as a problem with "iostream.h". ".h" files are for c. You can always use them in your c work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi All,
I know there was a previous thread, but there was no clear conclusion to the debate as to if and how it was possible to make MinGW2003 and Dev-C++ work together correctly. There were problems with iostream etc. that prevented simple cin/cout from working.
Anyone have any ideas ?
Thanks,
Greg.
I have tried a few ways to do just that; and they all worked , the way iam doing it now works fine. ( everything compiles if coded right).
Now as for iostream , i found that gcc 3.2 has a problem with ' iostream.h ', not ' iostream '. Something to do with a renew of the header in 3.2-( Standard C++) ( the .h is not needed, and the compiler i get, kicks it back with a message if you put the .h ).
Second as cout and cin go, if you use them you must do one of two things: ' using namespace std; ' will allow you to write them as just ' cout ' and ' cin '....otherwise !, you will need to write them as: ' std::cout ' and ' std::cin ' ect... in order for them to compile without errors.
Just my personal use of the gcc 3.2 and what i have done, and found from using it.
j@ck_
Jack !
Thx man, I will try it and let you know how it goes.
Regards,
Greg.
you never use ".h" in your c++ work. This can not be considered as a problem with "iostream.h". ".h" files are for c. You can always use them in your c work.