On 14 Feb 2010, at 16:07, [email protected] wrote: > Ian, I don't want to be adversarial,
It's OK - I respect your input; I've seen plenty of stuff from you to know that you know your stuff, and value your opinions: Tell me I'm wrong and I'll believe you! > Use it or don't, but thinking that std::string isn't part of > the C++ language is akin to thinking that strcmp() isn't > part of the C language. OK - but just for the record, I don't think that strcmp() is part of the C language. I think of it is as part of the supporting libraries. I do most of my coding in embedded environments, generally on custom hardware (though it has been a *very* long time since we created our own CPU...) and in many of those the standard libraries are not available, unless you write your own implementations of them, or port newlib or etc... Experience using C++ in those environments? Let's just say that the C libraries are simpler to port/emulate... Things are better now, but for a very long time, the actual behaviour of C++ code and the STL could be very variable depending on which target we ran it on, and that's not a good thing for portability. Doesn't inspire confidence, shall we say... Cheers, -- Ian _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
