Linux -Blue forest free software | Return to home page | Site Map | Search WWW | Contact Us |
Your current position : Homepage > Free Software > Technological exchanges >Application Programming


    

Blue Forest http://www.lslnet.com at 10:18 on June 6, 2006


The C + + header files

Standard C + + :

#include "Iostream.h>

Int main ()
{
}
Why not translated, and if it changed to the "can be translated through iostream>.

Since the provision of iostream.h, how to use?

Iostream.h this manner inconsistent with the standards.

Used
[code]#include "Iostream.h>[/code]

Equivalent

[code]#include "Iostream>
Using namespace std;
[/code]

More generally recommend the use of the latter

-->
Does not mean? ? ? ?

In the document Zhaobu to iostream.h, only iostream

-->


This is absolutely correct.

#include "Iostream.h>
C + + is a new version of the style.

#include "Iostream>
Using namespace std;
After the standardization of C + + style.

Many do not support the former compiler.

"C + + Programming Language" Appendix B.3
China is devoted to "deal with the old C + +."

Agree

Good, and I summarize :
1. I dev c++4.9.8.0 test passed.
2. The new compiler may contain "iostream.h> the first such document is compatible to the old code, and the" iostream.h> Std : : China is not a function of the content.

3. The standard C + +, using the format : "iostream>, this is not the first paper (header file)
Instead, the first (header), which is the standard name space.
4. "Iostream> totally dependent on the content of the" iostream.h> the content. Can be used alone.
5. Now the latest compiler only supports the "iostream> not support" iostream.h>.

I understand, right?



 Privacy Policy  Copyright © 1999-2000 LSLNET.COM. All rights reserved. Blue Forest website owners. E-mail : Webmaster@lslnet.com