How to Handle GCC's Deprecated Conversion Warnings from String Constant to `char*`?

How to Work Around Warnings About Deprecated Conversion from String Constant to 'char*'

In GCC versions prior to 4.3, one could declare a variable with a char * type and then assign it a string literal. However, GCC 4.3 and later deprecate this practice with a warning. The correct way to do this is to declare the variable as const char *, but if you have a large codebase and do not want to fix all the instances at once, there is a way to stifle the warnings.

To suppress these warnings, change the type of any functions that you pass string literals to from char * to const char *. This is the correct way to do it anyway, so if you're going to fix something, fix it right.

The reason for this deprecation is that string literals are of type const char *, and casting away the const to modify them is undefined behavior. To modify a string, you need to copy the const char * string character by character into a dynamically allocated char * string.

Here is an example of how to do this correctly:

#include <iostream>

void print(char* ch);

void print(const char* ch) {
    std::cout << ch;
}

int main() {
    print("Hello");
    return 0;
}

The above is the detailed content of How to Handle GCC's Deprecated Conversion Warnings from String Constant to `char*`?. For more information, please follow other related articles on the PHP Chinese website!