Boost logo

Boost :

From: Peter Dimov (pdimov_at_[hidden])
Date: 2004-10-22 12:11:53

Rob Stewart wrote:
> It is easy to build a safe interface atop a fast one, but you
> can't do the reverse.

Yes. The question is, why should the fast interface not consist of a set of
algorithms operating on sequences of char*_t. The argument against was that
creating a string incurs an allocation penalty, and the users will not do
it. But my experience does not suggest that this would be the case. I
frequently use vector<char> for C APIs that need a char[] and std::string
for C++ APIs, and haven't found the necessary conversions a performance

Boost list run by bdawes at, gregod at, cpdaniel at, john at