Case sensitive variable names?

[Econdoc]

Variable Names
I would really like to remove the requirement that variable names are case sensitive. I can see that the content (value) of a variable needs to be case sensitive, but do not understand why the name itself must be stringently applied.
I believe that Global_a and global_a are not the same variable. Ditto for Color="Red" and color="Red". This is very restrictive.

Function Calls
The same issues surrounds functions: IsChecked() is not accepted, but isChecked() is okay. Click(x,y) is not accepted, but click(x,y) is okay. The function call is the same, but one form creates a syntactic error.

Removing all these restrictions in an update will not affect any existing flows. Anyway these restrictions could be removed in an updated version?

[Martin]

Hi,

No sorry, removing this restriction affects existing flows since someone might have used upper and lower case variable names and expects the variables to be different.

Regards,
Martin

[fagci]

Yup. Most of programming languages are case sensitive.

Furthermore, they have own coding style guides.

Best regards, Mikhail.