Archives
D Programming
DD.gnu digitalmars.D digitalmars.D.bugs digitalmars.D.dtl digitalmars.D.dwt digitalmars.D.announce digitalmars.D.learn digitalmars.D.debugger C/C++ Programming
c++c++.announce c++.atl c++.beta c++.chat c++.command-line c++.dos c++.dos.16-bits c++.dos.32-bits c++.idde c++.mfc c++.rtl c++.stl c++.stl.hp c++.stl.port c++.stl.sgi c++.stlsoft c++.windows c++.windows.16-bits c++.windows.32-bits c++.wxwindows digitalmars.empire digitalmars.DMDScript |
c++ - #include behavior
I've used C (albeit on unix) for a very long time. I've decided to do a rather silly thing, which is learn win32 and C++ at the same time.... Anyway, I've picked up a C++ book and it talks about a new way of using #include with the standard libraries. #include <iostream> instead of #include <iostream.h> This leads to two questions: Is this behavior supported? Is this the style most folks use or do you slip back to the .h format? Jan 04 2002
"Jon R. Nials" <jnials nials.org> wrote in message news:a160bp$7dh$1 digitaldaemon.com...I've used C (albeit on unix) for a very long time. I've decided to do a rather silly thing, which is learn win32 and C++ at the same time.... Anyway, I've picked up a C++ book and it talks about a new way of using #include with the standard libraries. #include <iostream> instead of #include <iostream.h> This leads to two questions: Is this behavior supported? Is this the style most folks use or do you slip back to the .h format? Jan 05 2002
|