Hi there.  Why does emx/gcc disallow the modification of string constants? 
Or more to the point - why does ANSI/ISO C disallow this?  Tnx.

Note that the following code when compiled with emx/gcc will cause an
exception error when executed, due to this ANSI/ISO C rule.  When compiled
with Borland C++ for DOS 3.1, Microsoft QuickC 2.5 or Borland C++ for OS/2
1.0, the following code executes without error.  CLint 1.41 also passed the
following code with flying colors.


#include 

int main(void)
{
    char *str = "Hello world";
    *(str + 5) = '\0';
    printf("str: `%s'\n", str);
    return 0;
}


The following code is a simple work-around for the rule:

#include 
#include 
#include 

int main(void)
{
    char *str = strdup("Hello world");
    *(str + 5) = '\0';
    printf("str: `%s'\n", str);
    free(str);
    return 0;
}


andrew

--- Msgedsq/2 3.20