Which is easy scripting language type in your opinion

[prazetto]

Hi All expert, newbie and lost person ,

Come here!     I want to ask something.

Which is easy scripting language type in your opinion.

#01:
      - case sensitive for type name
      - case sensitive for variable name
#02:
      - case sensitive for type name
      - case insensitive for variable name
#03:
      - no case sensitive (case insensitive)
        at all for type name and variable name
        and also function name.

Because currently the code I use for type name,  variable
name and function name using one list table.

So I need you opinion to consider change list table to have
one for each one.

Well for myself I'm more like number #03 than other but that
only my opinion and don't know the other people.

Aren't obviously if I wrote what i like when this not only for me.

Thanks.
 

[Melba23]

prazetto,

I have removed the link to your "official site" from your sig - it was firing AV alerts for myself and several other members. I realise this is probably not your fault - but if you want to add it to your sig again, please make sure it is clean before doing so.

M23

[James]

You're talking about languages features known as type systems. There a few of them around, so that link should clear things up for you.

Edited July 5, 2013 by James

[Richard Robertson]

Case sensitivity is very useful in my opinion. I dislike case insensitive languages and will capitalize things consistently on my own.

[BrewManNH]

Case sensitivity is very useful in my opinion. I dislike case insensitive languages and will capitalize things consistently on my own.

So, in other words, you don't really need case sensitivity? 

I find it to be an unnecessary burden with no real point in a language.

[guinness]

Case sensitivity is very useful in my opinion. I dislike case insensitive languages and will capitalize things consistently on my own.

I have zero opinion on this, but this is a good argument against.

[Mat]

Making use of case sensitivity is pretty common in some typed languages. You'll see declarations like "Foo foo;" all the time. Not necessarily a good idea, but pretty common.

Why would you change the case you name a variable? Surely it's much easier just to type the same thing?

[BrewManNH]

Making use of case sensitivity is pretty common in some typed languages. You'll see declarations like "Foo foo;" all the time. Not necessarily a good idea, but pretty common.

Why would you change the case you name a variable? Surely it's much easier just to type the same thing?

It's not that you'd want to change it, it's to prevent the half hour debugging a script because you typed foo instead of Foo.

[Mat]

It's not that you'd want to change it, it's to prevent the half hour debugging a script because you typed foo instead of Foo.

Well it should just be "Variable not declared". 

Programming doesn't account for typos anywhere else.

[BrewManNH]

And it's not a typo unless the variables are case sensitive, which means that having case sensitivity makes more work for zero gain. At least zero gain as far as anyone has been able to provide so far. Also, saying case sensitive is the way to go because some other language has it, is not a valid argument.

[MarkRobbins]

Wanting case-insensitivity so you don't have to worry about mistyping the wrong case for a character strikes me as saying 'give me the shotgun'.
In other words, if you are going that fast, you deserve your speeding ticket, who knows what else you mistyped that is going to hook up to the wrong thing and not give you a runtime error.
Case-sensitivity also gives you access to shorter names. I don't care what they say, local vars with 'descriptive' names make the code too noisy to read.
It is much better to use one-line comments on sections of code to describe what is happening, then the coder can look at it in one glance and see if it is 'well-formed' or not.
With big noisy names, this isn't possible.
Without CamelCase you have also to worry about collisions or switch to underbar separators.