typedef unsigned short _Elem;
template <class _Elem>
class Data {
public:
void fn() {
...
_Elem* tmp = new _Elem[size];
if( sizeof(*content) == 1 ) { //char
strncpy(tmp, content, size);
}
else { //wchar_t
wcsncpy(tmp, content, size);
}
}
private:
_Elem* content;
}Different functions based on template arg
Author
strcpy has no place in C++. Doubly so when dealing with strings.
If you find yourself in need to copying sequences of iterable containers, use std::copy.
Functions can be specialized using templates:
To extend that, you can use template specialization, to handle other types differently:
There's also a few gotchas using partial specialization, but the link eludes me right now.
If you find yourself in need to copying sequences of iterable containers, use std::copy.
Functions can be specialized using templates:
template < class CharType >void foo( std::basic_string< CharType > &s ){ //}To extend that, you can use template specialization, to handle other types differently:
template < class CharType >class operation{ void copy( std::basic_string< CharType > &s );};template <>class operation<char>{ void copy( std::string &s );}template <>class operation<wchar_t>{ void copy( std::wstring &s );}...template < class CharType >void foo( std::basic_string< CharType > &s ){ operation< CharType > op; op.copy( s );}There's also a few gotchas using partial specialization, but the link eludes me right now.
Author
Thanks, I didn't know you could use std::copy on a char array. The only reason I was using strcpy was because I need to use an actual char* instead of std::string because I'm working with binary data since std::string changed the data when I tried copying the data into it.
Quote:Original post by SfpianoCan you elaborate on this? What do you mean by std::string 'changing the data'?
The only reason I was using strcpy was because I need to use an actual char* instead of std::string because I'm working with binary data since std::string changed the data when I tried copying the data into it.
In case you're talking about dealing with different character types, std::string and std::wstring are just typedefs for std::basic_string<...>, so you should be able to use SC++L strings while still parameterizing by element type (or so I assume - I've never actually had occasion to do this myself). [Edit: See Antheus' post above for an example of this.]
[Edited by - jyk on August 11, 2007 6:41:50 PM]
Author
Hmm, the way I originally had it, I was doing:
char* buff;
std::string str;
...
str += std::string(buff);
which was turning all of the non-standard characters into some other character.
But if I do:
str.append(buff, len);
then it works.
char* buff;
std::string str;
...
str += std::string(buff);
which was turning all of the non-standard characters into some other character.
But if I do:
str.append(buff, len);
then it works.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
