Re: Using boost::thread under Visual C++ now OT

From: terekhov (terekhov_at_[hidden])
Date: 2002-01-09 18:20:27

--- In Boost-Users_at_y..., "bill_kempf" <williamkempf_at_h...> wrote:
> --- In Boost-Users_at_y..., "terekhov" <terekhov_at_d...> wrote:
> > --- In Boost-Users_at_y..., "bill_kempf" <williamkempf_at_h...> wrote:
> > > --- In Boost-Users_at_y..., Jon Kalb <kalb_at_L...> wrote:
> > > > At 7:57 PM +0000 1/5/02, bill_kempf wrote:
> > > > ><string.h> is neither deprecated,
> > > > 
> > > > Appendix D.5 Standard C library headers [depr.c.headers] 
leads 
> me 
> > > to 
> > > > believe otherwise.
> > > 
> > > Splitting hairs.  ...
> > 
> > No. Consider:
> > 
> > "These are deprecated features, where deprecated is defined as:
> >  Normative for the current edition of the Standard, but not
> >  guaranteed to be part of the Standard in future revisions."
> 
> But the features aren't deprecated, only the header is.  In other 
> words all the features of the deprecated <string.h> will live on in 
> the non-deprecated <cstring>.

But the code might "suddenly" stop compile (1st: missing 
header; 2nd: global->std name space change) in X years 
from now and our build/packaging folks just have no idea 
what <string.h>/<cstring> is and even if they would know 
how to fix this "small" problem, they are not supposed/
allowed to modify my sources... so, do I want to get a 
call/fix it later? No! ;-)

regards,
alexander.