“Life-time” of a string literal in C

by

Yes, lifetime of a local variable is within the scope({,}) in which it is created.

Local variables have automatic or local storage. Automatic because they are automatically destroyed once the scope within which they are created ends.

However, What you have here is an string literal, which is allocated in an implementation defined read-only memory. String literals are different from local variables and they remain alive throughout the program lifetime. They have static duration [Ref 1] lifetime.

A word of caution!

However, note that any attempt to modify the contents of an string literal is an undefined behavior (UB). User programs are not allowed to modify contents of a string literal.
Hence, it is always encouraged to use a const while declaring a string literal.

const char*p = "string";

instead of,

char*p = "string";

In fact, in C++ it is deprecated to declare a string literal without the const though not in C. However, declaring a string literal with a const gives you the advantage that compilers would usually give you a warning in case you attempt to modify the string literal in second case.

Sample program:

#include<string.h> 
int main() 
{ 
    char *str1 = "string Literal"; 
    const char *str2 = "string Literal"; 
    char source[]="Sample string"; 
 
    strcpy(str1,source);    // No warning or error just Uundefined Behavior 
    strcpy(str2,source);    // Compiler issues a warning 
 
    return 0; 
}

Output:

cc1: warnings being treated as errors
prog.c: In function ‘main’:
prog.c:9: error: passing argument 1 of ‘strcpy’ discards qualifiers from pointer target type

Notice the compiler warns for the second case, but not for the first.

To answer the question being asked by a couple of users here:

What is the deal with integral literals?

In other words, is the following code valid?

int *foo()
{
    return &(2);
}

The answer is, no this code is not valid. It is ill-formed and will give a compiler error.

Something like:

prog.c:3: error: lvalue required as unary ‘&’ operand

String literals are l-values, i.e: You can take the address of an string literal, but cannot change its contents.
However, any other literals (int,float,char, etc.) are r-values (the C standard uses the term the value of an expression for these) and their address cannot be taken at all.

[Ref 1]C99 standard 6.4.5/5 “String Literals – Semantics”:

In translation phase 7, a byte or code of value zero is appended to each multibyte character sequence that results from a string literal or literals. The multibyte character sequence is then used to initialize an array of static storage duration and length just sufficient to contain the sequence. For character string literals, the array elements have type char, and are initialized with the individual bytes of the multibyte character sequence; for wide string literals, the array elements have type wchar_t, and are initialized with the sequence of wide characters…

It is unspecified whether these arrays are distinct provided their elements have the appropriate values. If the program attempts to modify such an array, the behavior is undefined.

More Related Contents:

  1. Procedure to include own functions to ANSI C Standard library
  2. How do I modify a pointer that has been passed into a function in C?
  3. returning a local variable from function in C [duplicate]
  4. Default argument promotions in C function calls
  5. C Programming: malloc() inside another function
  6. Difference between passing array and array pointer into function in C
  7. Override a function call in C
  8. Function pointers and address of a function
  9. Alternative (K&R) C syntax for function declaration versus prototypes
  10. Allocate memory 2d array in function C
  11. Returning a pointer to an automatic variable
  12. What is this strange function definition syntax in C? [duplicate]
  13. C – allocating a matrix in a function
  14. Function Returning Itself
  15. Changing array inside function in C
  16. undefined reference when calling inline function
  17. Strange warning in a C function const multidimensional-array argument
  18. in c: func(void) vs. func() [duplicate]
  19. How to return matrix (2D array) from function? (C)
  20. What is the reason function names are prefixed with an underscore by the compiler?
  21. No defined type of a function parameter defaults to int? Am I insane?
  22. How to use the rand function to make numbers in a specific range?
  23. Avoiding the main (entry point) in a C program
  24. C -> sizeof string is always 8
  25. Function pointer as a member of a C struct
  26. Function declaration inside of function — why?
  27. Regex to pull out C function prototype declarations?
  28. C declaration from standard signal Library
  29. How can I malloc a struct array inside a function? Code works otherwise
  30. C pointer notation compared to array notation: When passing to function

Leave a Comment