@erisceleste @lproven @f4grx
We personally love a very verbose way of laying down instructions. But then again a lot of our work is basically functional with little to no objects in place. So perhaps not as abstracted as some people. so having your BEGIN FOR, END WHILE, IF, CASE, DO, etc etc, and other, almost SQL-isms are neat.
Your first example is easy to figure out what it might be doing. your last example is pretty much just soup to our eyes (also is that a return type declaration or the variable to return at the end of the function? etc etc).
A lot of people do rave about natural language programming but honestly, just having actual readable words for what you're doing even if you're doing verbose assembly would be good. ( but, again, it is not the same to stuff some values into some registers to have a little bunny move across a 32 tile playfield than it is, temperature monitoring for blood samples or what have you)