I think Lee would probably like to avoid adding reference types, etc. to the language. A much simpler change could be to allow things like this:



It only introduces one keyword ("in <array>") which translates directly into "= 0 to <length of array>" and doesn't require changes to the AppGameKit player.

The next thing that is definitely needed is the "continue" and "redo" commands to complement the "exit" command. "continue" should jump to the next iteration of a loop. "redo" should jump to the start of the current iteration.

"continue" allows you to skip a loop without having loads of nested if statements:


"redo" allows you to easily delete from an array while looping through it:

I agree with Diggsey and understand the issue Airslide raises. IMO the foreach should return the index of the array it is iterating as oppose to a reference or copy of the actual element. So Airslides example would become:



Save the confusion of passing by reference.

Dynamic arrays should be high on the list (With Push/Pop/size functions) to....I would say associative arrays would be nice but maybe thats just a personal love of mine

I can do without associative arrays, but dynamics arrays is a must. It's hard to write my xml parser without them.