The first example does not work when you go to delete the pointer. The program either hangs when I add the null terminator or without it I get:
Debug Assertion Fai
Do not forget to use
delete []
whenever you are allocating something with [].
In the first example, you have caused a memory leak.
Your variable at
is a pointer to a memory address, not the string itself. When you assign the address of "tw"
to the pointer, you have lost the original address that you got with new
. at
now points to an address that you did not allocate with new
, so you cannot delete
it.
If you think of pointers as integers, it will probably make more sense. I've assigned arbitrary numbers as addresses for the sake of discussion.
char *at = new char[3]; // 0x1000
at = "tw"; // 0x2000
at[2] = '\0'; // set char at 0x2002 to 0
delete at; // delete 0x2000 (whoops, didn't allocate that!)
Because a char*
isn't a string. It's just a pointer to some character, with the convention that there might be more characters to follow and that after the last one there is a '\0'
.
A string literal in C (and thus in C++) like "abc"
is just an array of characters, with the compiler silently adding a '\0'
. When you assign an array to a pointer, the array silently converts a pointer to the first element. The result is that
at = "tw";
means, the pointer at
is assigned the address of the first character in the string literal "tw"
. By this, it will lose its old value. Since this was the address of a dynamically allocated character array, you are leaking this array.
When you later assign to a character in the array at
now points to, you are assigning a new value to some character in the string literal. That's invoking undefined behavior and the program hanging or crashing immediately is probably the best that could happen to you when you do this. (On many platforms you're writing to read-only memory doing so.)
Later you pass at
to delete[]
(and not delete, since you called new[], not new). In doing so, you pass it the address of the string literal, instead of the allocated character array. This will, of course, mess up the heap manager. (VC's runtime library catches this in Debug mode.)
std::strcpy
, on the other hand, copies a string character by character from one array to another array. No pointers will be changed, only pieces of memory are copied. The pointer to the target array still points to the target array afterwards, only the data in that array has changed.
Let me add this: As a beginner in C++, you should use std::string
, rather than C strings. That does all the dirty work for you and has sane semantics.
In your first example you are allocating some memory and pointing to it with the "at" variable. When you do
at = "tw"
you are effectively re-pointing the char * to a constant character string. This causes you to leak memory. When you go on to delete "at" you are attempting to delete stack memory.
strcpy goes through each character and copies their values to the new memory you allocate. This is also known as a deep copy.
When you do
char *at = ...;
at = "hello";
You're basically overwriting the pointer value (i.e., the address of the memory allocated for you by new[]
) with the address of a static constant string. This means that when you later delete that memory, you're passing delete
a pointer not previously returned by new
.
That is a bad thing to be doing.
In C and C++, assignments to pointers typically don't do anything to the memory being pointed at, they change the pointer itself. This might be confusing if you're used to a language where strings are more of "first class citizens".
Also, you should use delete[]
if you used new[]
.
In the first example you are chaning the value at, in the second you are changing the value of what at points to. Assigning a char * to a double quoted string assigns it to a static const pointer.
In particular, in the first example at now points a different location in memory.