Re: [boost] [iostreams][vc8]deprecetedstandardlibrarymemberfunctions; fatal linker error [OT]

From: Bronek Kozicki (brok_at_[hidden])
Date: 2005-07-02 14:29:35

Jonathan Turkanis wrote:

>>It would probably be a good idea if someone would volunteer to give
>>Microsoft's headers a once over and see if there are any other API's
>>that are needlessly deprecated. Certainly there plenty of room for
>>frustration here - I've seen deprecated warning from std::copy and
>>other std lib algorithms (and no *not* using pointers), as well as
>>the C API's.
> 
> Maybe they should just deprecate everything, to be on the safe side.

starting with cash cows ... errr ... Windows and Office?

Sorry for harsh tone, but I started getting unpleasant feeling that my 
favourite compiler will soon completly "deprecate" well established and 
very portable C++ library "just to be on the safe side", while real bugs 
are hiding somewhere else. Maybe Microsoft programmers do need some 
special, crippled library to help them write secure code, but forcing it 
down the throat of all their customers is bit too far, IMO. MSVC8 is 
"deprecating" std::copy !? Maybe all std algorithms, eh? And BTW, I 
thought that term "deprecated library features" is actually used by the 
C++ standard, has clear meaning, and using it to describe some other 
kind of "depreciation" in the context of the C++ library implementation 
is little misleading.

B.