View Full Version : <iostream.h> not found?
Noxious020189
03-03-2006, 03:36 PM
Ok I just installed Visual Studio 2005, and I have never had a problem, but all of a sudden I am :(
http://img380.imageshack.us/img380/2392/ugh3kt.jpg
This is my exact build error^...
Win32 App
Consol App
.CPP file type
Do you have that file in directory where all other header files are stored? Also what is your code where you inlcude it?
Something Sexy
03-03-2006, 05:29 PM
Might want to try just <iostream> instead of <iostream.h>
Noxious020189
03-03-2006, 06:39 PM
I got it don't worry I renamed it to be a header file
Butcher_
03-10-2006, 07:25 PM
I got it don't worry I renamed it to be a header file
You shouldn't be renaming the standard headers!
<iostream> is correct - all the standard headers have no extension.
Something Sexy
03-11-2006, 12:09 AM
You shouldn't be renaming the standard headers!
<iostream> is correct - all the standard headers have no extension.
Depends what compiler you are using. If you are using an older verison or an older compiler, or a non microsoft based one then you might have STL headers that use their .h extension.
AgentGOD
03-29-2006, 12:54 PM
You guys seriously need to know how VS 2005 works.
What microsoft did was remove all the "old backwards compatible" header files. You'll need to use the Standard namespace now to do it, which is really gay.
Heres how it works:
#include <iostream>
using namespace std;
Don't ask me why they did this, but I believe they did it out of "convinience". What microsoft did not realize is that doing this will make the programmers' programs very bloated in file size.
For example, a program that ONLY needs iostream.h, it was about 80 KB, and after using the standard namespace, it became 200 KB. That is how bloated it is.
I would use Visual Studio .NET 2003, or download the SDK for VS 2005.
Something Sexy
03-29-2006, 02:25 PM
For example, a program that ONLY needs iostream.h, it was about 80 KB, and after using the standard namespace, it became 200 KB. That is how bloated it is.
I would use Visual Studio .NET 2003, or download the SDK for VS 2005.
And that is why you should NEVER use "using namespace std", poor programming.
AgentGOD
03-29-2006, 02:28 PM
And that is why you should NEVER use "using namespace std", poor programming.
I never do.
But I don't know why Microsoft made Visual Studio 2005 with all the "old" header files all stripped :p:
There are several ways to solve the problem:
1. Copy the includes, libs, etc from VS .NET 2003 to the 2005 folder.
2. Install Microsoft's VS 2005 SDK (includes "old" header files, and adds windows.h)
3. Stick with Visual Studio .NET 2003 or Visual Studio 6.0 SP6.
4. Screw MS, switch to a Linux Distro and use G++, or gcc.
Something Sexy
03-29-2006, 08:27 PM
Haha... gcc....I HATE gcc, using it right now for assembly and C++ to program my embedded systems robot....ugh, don't get me started
AgentGOD
03-29-2006, 08:44 PM
Nothings wrong with Linux :stick:
It's just Microsoft forcing us to use bloatware.
Something Sexy
03-30-2006, 09:17 AM
I never said there was anything wrong with Linux....I just don't like GCC....who does? It isnt the best written.
Asniper
04-09-2006, 04:20 PM
I never do.
But I don't know why Microsoft made Visual Studio 2005 with all the "old" header files all stripped :p:
There are several ways to solve the problem:
1. Copy the includes, libs, etc from VS .NET 2003 to the 2005 folder.
2. Install Microsoft's VS 2005 SDK (includes "old" header files, and adds windows.h)
3. Stick with Visual Studio .NET 2003 or Visual Studio 6.0 SP6.
4. Screw MS, switch to a Linux Distro and use G++, or gcc.
cause they're deprecated.
fyi iostream.h was deprecated in VC7 (VS.NET 2002) and removed in VC7.1 (VS.NET 2003)