Case sensitive variables question [SOLVED]

[jchd]

And the true purpose was?

What you say solves the "problem" boils down to giving variables completely distinct names.

That's the same as:

Assign("UpperVal", 123)
Assign("LowerVal", 456)
Assign("ProperVal", 789)

[czardas]

What you say solves the "problem" boils down to giving variables completely distinct names.

That's the same as:

Assign("UpperVal", 123)
Assign("LowerVal", 456)
Assign("ProperVal", 789)

My thoughts exactly, which is why I had to giggle. A big round of applause to Azijo for thinking out of the box though. Edited March 22, 2013 by czardas

[Shanheavel]

And the true purpose was?

What you say solves the "problem" boils down to giving variables completely distinct names.

That's the same as:

Assign("UpperVal", 123)
Assign("LowerVal", 456)
Assign("ProperVal", 789)

No, they're different. I can be the same only if will add U (upper) and L (lower) before every character in the variable name, like that:

Assign("UmLeLsLsLaLgLeUbLoLxUa", 123)
Assign("UmUeUsUsUaUgUeUbUoUxUa", 456)

Because UmLeLsLsLaLgLeUbLoLxUa isn't equal to UmUeUsUsUaUgUeUbUoUxUa. But AZJIO's idea is much better.

[Melba23]

Shanheavel,

I am delighted that you feel that you have solved your problem, but if you ever produce a valid code example in which this trickery is necessary I would still be interested in seeing it. Like jchd and czardas, to me it looks as if you are using distinct names after all.

M23

[Shanheavel]

Shanheavel,

I am delighted that you feel that you have solved your problem, but if you ever produce a valid code example in which this trickery is necessary I would still be interested in seeing it. Like jchd and czardas, to me it looks as if you are using distinct names after all.

M23

Good to know. I'll remember about this.

If everything is clear then I think we can just end this.

[kylomas]

What is clear is that you can't/won't answer the question that everyone is asking...

[BrewManNH]

Interesting reads for anyone interested

http://www.codinghorror.com/blog/2005/12/the-case-for-case-insensitivity.html

http://www.somethinkodd.com/oddthinking/2005/10/27/the-case-for-case-preserving-case-insensitivity/

[Shanheavel]

What is clear is that you can't/won't answer the question that everyone is asking...

If you mean where I want to use case sensitive variable names - I said that I was making some tool which converts scripts to FASM.

[Melba23]

Shanheavel,

We know that as you mentioned it before - but we are all eager to see some working AutoIt code that requires these case-sensitive variables.

M23

[guinness]

I'm happy AutoIt doesn't have case-sensitive variables, imagine the support tickets that would come flooding in as a result of someone inadvertently using a single upper-case character.

[BrewManNH]

I just read the documentation for FASM and it doesn't use case sensitivity either.

[Shanheavel]

Shanheavel,

We know that as you mentioned it before - but we are all eager to see some working AutoIt code that requires these case-sensitive variables.

M23

The project is named Excalibur. Take a look here. Give me a few months and I'll finish and maybe public it here.

I just read the documentation for FASM and it doesn't use case sensitivity either.

Just do a simple test. Create empty *.asm file and try this:

VAL dd 1
val dd 2
VaL dd 3

And it works (or at least it should), so the variable names are different.

Now try something like that:

val dd 7
val dd 3

The compiler should throw the error.

Error: symbol already defined

What do you think about this?

[BrewManNH]

Ok, so it's case sensitive, write the variables with different names then. Using the same word but with different case should probably be avoided in every language, I can't imagine the nightmare of trying to troubleshoot code where you've used the same variable name, but with different case. Imagine a typo in your code where you used dog instead of Dog, where dog means kill the dog, and Dog means feed the dog, and you typed in dog by accident.

[Shanheavel]

@BrewManNH

In FASM and many other programming languages dog isn't the same as Dog or dOG. So now you know why I needed this, right?

[guinness]

Imagine a typo in your code where you used dog instead of Dog, where dog means kill the dog, and Dog means feed the dog, and you typed in dog by accident.

Wow, try explaining that to the family.

[Shanheavel]

Wow, try explaining that to the family.

Haha, I fell off the chair. >_< Guys, but what are we talking about?

[trancexx]

Using the same word but with different case should probably be avoided in every language, I can't imagine the nightmare of trying to troubleshoot code where you've used the same variable name, but with different case. Imagine a typo in your code where you used dog instead of Dog, where dog means kill the dog, and Dog means feed the dog, and you typed in dog by accident.

I don't agree. That's matter of perspective and from my perspective case sensitive is more natural solution. Besides, argument that all serious programming languages are case sensitive is pretty strong.

[JohnOne]

Would it not just be easier to run some regexp to convert all variables in a script to either upper or lower case.

[czardas]

Would it not just be easier to run some regexp to convert all variables in a script to either upper or lower case.

But JohnOne isn't RegExp case sensitive by default?

[bogQ]

and then we will have a script with 8 types of identical dog where user asking why dog won't bark correctly

if you ask me better to put one more letter to define different variable name instead to search all variables to see what type of dOg is available to type in next