Question

For C, we use char[] to represent strings.

For C++, I see examples using both std::string and char arrays.

#include <iostream>
#include <string>
using namespace std;

int main () {
  string name;

  cout << "What's your name? ";
  getline(cin, name);
  cout << "Hello " << name << ".\n";

  return 0;
}

#include <iostream>
using namespace std;

int main () {
  char name[256];

  cout << "What's your name? ";
  cin.getline(name, 256);
  cout << "Hello " << name << ".\n";

  return 0;
}

(Both examples adapted from http://www.cplusplus.com.)

What is the difference between these two types in C++? (In terms of performance, API integration, pros/cons, …)

Answer 1

A char array is just that – an array of characters:

• If allocated on the stack (like in your example), it will always occupy eg. 256 bytes no matter how long the text it contains is
• If allocated on the heap (using malloc() or new char[]) you’re responsible for releasing the memory afterwards and you will always have the overhead of a heap allocation.
• If you copy a text of more than 256 chars into the array, it might crash, produce ugly assertion messages or cause unexplainable (mis-)behavior somewhere else in your program.
• To determine the text’s length, the array has to be scanned, character by character, for a \0 character.

A string is a class that contains a char array, but automatically manages it for you. Most string implementations have a built-in array of 16 characters (so short strings don’t fragment the heap) and use the heap for longer strings.

You can access a string’s char array like this:

std::string myString = "Hello World";
const char *myStringChars = myString.c_str();

C++ strings can contain embedded \0 characters, know their length without counting, are faster than heap-allocated char arrays for short texts and protect you from buffer overruns. Plus they’re more readable and easier to use.

---

However, C++ strings are not (very) suitable for usage across DLL boundaries, because this would require any user of such a DLL function to make sure he’s using the exact same compiler and C++ runtime implementation, lest he risk his string class behaving differently.

Normally, a string class would also release its heap memory on the calling heap, so it will only be able to free memory again if you’re using a shared (.dll or .so) version of the runtime.

In short: use C++ strings in all your internal functions and methods. If you ever write a .dll or .so, use C strings in your public (dll/so-exposed) functions.