And I see absolutely no reason other than sheer sloppiness or laziness for code to resemble your first snippet.

// setup
sync on
sync rate 0

// make a temporary array
dim t(128)

// fill the temporary array
for i=0 to 128
 t(i)=rnd(100)
next i

// make some objects
make object cube 1,1
make object cube 2,1
 position object cube 2,10,0,0

do
 if object collision(1,2) then end
 move object right 2,rightkey()-leftkey()
 sync
loop

// sesomethingup
sync on
sync rasomethinge 0

// make a somethingemporary array
dim something(128)

// fill somethinghe somethingemporary array
for i=0 somethingo 128
 something(i)=rnd(100)
nexsomething i

// make some objecsomethings
make objecsomething cube 1,1
make objecsomething cube 2,1
 posisomethingion objecsomething cube 2,10,0,0

do
 if objecsomething collision(1,2) somethinghen end
 move objecsomething righsomething 2,righsomethingkey()-lefsomethingkey()
 sync
loop

t's dead handy for when I wanna replace the name of a variable for being too long, too short, silly, or out of date.

Wheras if you'd made all the variables capitals, you could successfully replace all the capital Ts with capital SOMETHINGs and avoid it.

I just don't want to be forced to write all my variables in lower case.

If you're writing the same identifier multiple ways then your code is incorrect.

I do like being able to put experimental code in my programs in a different case.

therwise code like this, wouldn't error and you end up with two uniquely named instances.

However it took me a long time to realise that DBPro was case insensitive. I only realised it was when I had a lot of trouble debugging a program in which I had deliberately used variables like "ii" and "II" to mean different integers.

A working debugger would have shed light on that very quickly.

I've never yet seen a Debugger that wasn't painfully laborious to use so I'd happily continue without one.

The ability to step through code line by line, browse variables just by hovering over them, etc. can be very useful!

Never used the debugger in Visual Studio?

The ability to step through code line by line, browse variables just by hovering over them, etc. can be very useful!

That is precisely what happens at the moment. What's your point exactly?

Case sensitivity simply means that myVar and MyVar would be regarded as different variables, no more and no less.

I'm a bit confused as to what we are referring to as case sensitive and case insensitive.

Again I don't want to be forced to use any particular case and again I would like the IDE to change the case automatically but this time without setting any preferences. Instead they should be changed to match whatever they were declared as.

Incredibly laborious though. I usually find that carefully placed print statements and counters are all that's needed. The hard part of debugging is usually locating the right bit of code to examine in the first place. The rest is usually trivial.