tags:

views:

1481

answers:

4

Is a string literal in c++ created in static memory and destroyed only when the program exits?

+8  A: 

Where it's created is an implementation decision by the compiler writer, really. Most likely, string literals will be stored in read-only segments of memory since they never change.

In the old compiler days, you used to have static data like these literals and global but changeable data. These were stored in the TEXT (code) segment and BSS (initialized data) segment.

Even when you have code like char *x = "hello";, the hello string is stored in read-only memory while the variable x is on the stack (or writable memory at global scope). x just gets set to the address of the hello string. This allows all sorts of tricky things like string folding, so that "invalid option" (0x1000) and "valid option" (0x1002) can use the same memory block as follows:

0x1000 invalid option\0

Keep in mind I don't mean read-only memory in terms of ROM, just memory that's dedicated to storing unchangeable stuff (which may be marked really read-only by the OS).

They're also never destroyed until main() exits.

paxdiablo
+5  A: 

Yes, string literals are valid for the entire duration of the program, even during the destruction of static objects.

2.13.4/1 in the Standard says

An ordinary string literal has type "array of n const char" and static storage duration.

The Standard says of 'static storage duration' in 3.7.1/1:

The storage for these objects shall last for the duration of the program.

James Hopkin
+1  A: 

Well ... Yes. They sort of have to be; the information that makes up the sequence of characters in each string has to be somewhere. If they were to be allocated dynamically and then initialized, where would the information used to to the initialization reside? Thus, it's more efficient to simply make the strings static, so that they are always available and valid once the program is done loading.

unwind
A: 

String literals are stored in read-only segments of memory

Samiksha