No subject

h sensitive to case and insensitive to case has got to be unexpected.  The =
proposal is to make it consistent - which probably means matching the docum=
entation on wiki.asterisk.org and making it case sensitive.  If done in 1.8=
, this needs to be noted in the UPGRADE file.

At the minimum, the would entail making the code in ast_str_retrieve_variab=
le should be made to be case sensitive:

{noformat}
=09/* if not found, look into chanvars or global vars */
=09for (i =3D 0; s =3D=3D &not_found && i < ARRAY_LEN(places); i++) {
=09=09struct ast_var_t *variables;
=09=09if (!places[i])
=09=09=09continue;
=09=09if (places[i] =3D=3D &globals)
=09=09=09ast_rwlock_rdlock(&globalslock);
=09=09AST_LIST_TRAVERSE(places[i], variables, entries) {
=09=09=09if (!strcasecmp(ast_var_name(variables), var)) {
=09=09=09=09s =3D ast_var_value(variables);
=09=09=09=09break;
=09=09=09}
=09=09}
=09=09if (places[i] =3D=3D &globals)
=09=09=09ast_rwlock_unlock(&globalslock);
=09}
{noformat}

There are potentially other areas where variables are evaluated however, an=
d all of those should be checked.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira