Re: help

From:

James Kanze <james.kanze@gmail.com>

Newsgroups:

comp.lang.c++

Date:

Tue, 17 Mar 2009 15:50:17 -0700 (PDT)

Message-ID:

<2469cb6e-948f-4e48-b6ad-2af1afc28dfd@j39g2000yqn.googlegroups.com>

On Mar 17, 5:35 pm, Noah Roberts <n...@nowhere.com> wrote:

James Kanze wrote:

On Mar 16, 4:38 pm, "Christopher Dearlove"
<chris.dearl...@baesystems.com> wrote:

"James Kanze" <james.ka...@gmail.com> wrote in message

news:f8a99e67-f6aa-48c0-9301-6e4daa04d4bb@e38g2000yqa.googlegroups.com.=

...

It was part of the de facto C++ standard that predated the
ISO standard; in this sense, "deprecated" pretty much
describes its de facto situation, whether the term is
technically correct or not.

Except that if I use something still in the C++ standard but
deprecated, I expect it to still work. If I use <iostream.h> I
have no such expectation, and in at least some cases if I had
such an expectation, I'd be wrong. So it's quite unlike
deprecated in that practical regard.

Well, I'd expect it to work. And if it didn't, it's a pretty
strong sign from the compiler vendor that he doesn't care about
his customers.

1>------ Build started: Project: scratch, Configuration: Debug Win32 ----=

1>Compiling...
1>main.cpp
1>e:\dev_workspace\experimental\scratch\scratch\main.cpp(2) : fatal
error C1083: Cannot open include file: 'iostream.h': No such file or
directory
1>Build log was saved at
"file://e:\dev_workspace\experimental\scratch\scratch\Debug\BuildLog.htm"
1>scratch - 1 error(s), 0 warning(s)

Of course, you can always say, "Well obviously Microsoft
doesn't care about their customers." That's what makes your
philosophy here useless.

Apparently they don't. Which doesn't mean that you necessarily
have a choice. But it does mean that you may end up having to
rewrite parts of the project that you hadn't planned on. (Note
that I'm not recommending using <iostream.h> in new code. But
you shouldn't have to modify existing code if it wasn't broken.
And I'm sure that there was working code written for VC++ before
<iostream> existed.)

--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34