Re: Handling Strings

From:

=?ISO-8859-1?Q?=D6=F6_Tiib?= <ootiib@hot.ee>

Newsgroups:

comp.lang.c++

Date:

Mon, 28 Jun 2010 14:10:56 -0700 (PDT)

Message-ID:

<869603e7-c211-458e-b5bf-b2d134f350ee@k39g2000yqb.googlegroups.com>

On 28 juuni, 20:49, Sousuke <s0s...@gmail.com> wrote:

On Jun 28, 11:47 am, Brad <byte8b...@gmail.com> wrote:

On Jun 28, 11:18 am, "Francesco S. Carta" <entul...@gmail.com> wrote:

For converting std::string to C-style strings you use c_str(), for th=

reverse operation you build std::string from C-style strings - I have=

idea of what you mean with "byte arrays" since C++ has no "byte" type=

Yes, I use c_str(). Some libraries define byte (an unsigned char).

I don't see any need for casting, and about C style casts in particul=

ar,

you can (you should) always replace them with the equivalent C++
explicit casts - if casting is really needed.

You could take advantage of posting some example and of mentioning th=

libraries you're using, if this answer didn't satisfy your question.

Here is an example from Crypto++:

CryptoPP::Weak::MD4 hash;
byte digest[ 16 ];

// Here is one example where I cast to make the std::string I have
work
hash.Update((const byte*)generated_string.c_str(),
generated_string.length());
hash.Final( digest );

How about:

template<>
struct std::char_traits<byte>
{
// define the typedefs and static methods as appropriate

};

typedef std::basic_string<byte> ByteString;

When some library/framework/platform interface needs something as
input then best idea is provide that to it with conversion functions.
It is not so good idea to use the types of library in your internal
application data and logic.

Few years pass and you realize that you need to switch to different
library. Then it is hard because some "myte" of "cbangbang" library
has spread all over your code and now you depend on it. Whereas with
conversion/translation layers you may even support usage of multiple
competing libraries in parallel when need arises.