• Jon R. Nials (10/10) Jan 04 2002 I've used C (albeit on unix) for a very long time. I've decided to do a
• Walter (4/14) Jan 05 2002 The modern way is the .h-less way. DMC++ isn't there yet with

"Jon R. Nials" <jnials nials.org> writes:

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?

"Walter" <walter digitalmars.com> writes:

"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?

The modern way is the .h-less way. DMC++ isn't there yet with
iostream. -Walter