Checkbox to allow Case-(in)Sensitive source

[FloHimself]

what are the advantages of case-sensitivity?

[Psychophanta]

I don't get it, what has case sensitivity to do with the programs I'm writing and how does it affect the result???

Yes, it has to do, not for the results, but to make easy the control of the identifiers which belong to determinated stuff joints and subjoints inside programs or module-programs.

(because you are used to from other languages doesn't count btw )

The only languages i could be used are assemblers, not C/C++ (if you are refering to it). But you can be sure that's not the reason for this request. The real reason is what i say above, the real reason is: PRECISION in the names of identifiers.
I was born in Spain, so i am in use to talk spanish, but I prefer english; JUST BECAUSE it is a little bit more PRECISE than spanish one.

Moreover: As I've said, a CheckBox in the preferences will never affect you all who prefer not CaseSensitive identifiers. And i understand your positions and opinions, in fact i share it, but not for all kind of apps.

[Psychophanta]

what are the advantages of case-sensitivity?

Precision while checking and associating identifiers with determinated tasks and calculations.
A small task or calculation could have about 20 or 30 identifiers, and some of them must be grouped by parts which belongs to a stuff, those parts must be quickly and easy identified, with a shot of watch: I and i, J and j, K and k, IJK or IJk or IjK...
Interactions for physichs are always considered and analysed between 2 entities, not 3 or 4, etc, but 2. One of them is usually lower in electrical charge or in mass value. One is C and the lower is c, one is R, and the lower is r...
Sometimes, if for example i have a PermanentMagnet_A_RUB_Cause_Axis value (which could be variable due energy heat and/or electrical charges), there is needed a "dancing" value "hanging" from this, which is easy to manage: PermanentMagnet_A_Rub_Cause_Axis, PermanentMagnet_A_Rub_Cause_Axis1, PermanentMagnet_A_Rub_Cause_Axis2 ....

Anyway, for what i do, case sensitive identifiers are very very secondary in comparison to higher floats resolution and scientific notation expressions.

[Randy Walker]

There is no good reason to have variables with the same name but different cases. None.

This statement is in direct contradiction of common practices used in higher mathmatical fomulas. It's been a while since I studied physics but they very definitely use upper/lower case to distingguish various aspect of the same thing: time, distance, gravity, etc. so a big G and a little g would have entirely different values within the same equation. Blame Einstein

I liked having the ability to use double precision in my old launguage and I did use it, because it was there, but I have no preactical use for it and never really did. I think I recall seeing a post from Fred saying that PureBasic was never intended to be a platform for scientific applications and probably never will be. Case sensitivity will probably be assessed the same... too scientific and don't really need it in general programming.

[Kale]

What about a compiler directive:

Code: Select all

StrictCaseOn

X = 1
x = 2

Debug X
Debug x