I agree the "English feel" side of the BASIC language is something which attracted me a lot when I was young and decided which language to pick. But lately, it seems the OOP model as a such gives similar service in almost any language.
I think that is one of the reasons I feel strong BASIC "spirit" from C# language for example.
Little illustration:
sText = File.ReadAllText("c:\temp\myCharacters.txt");
sText = sText.ToLower();
If there would not be that semicolon on the end, it very much resembles some of the BASICs - no ugly characters, the stream of "commands" flows similar to english language as in BASIC.
I think the transition to higher level languages, increased performance of PCs, bigger hard drives and code completion mechanics smoothed the borders between languages a lot. Obscure strcpy and similar few characters "magic words" commands (not speaking of assembly) are now substitued by more english like function/method names in many languages.
Sometimes, BASIC takes it too far with being English like. For example, I was never big fan of:
syntax, because I think the:
... is still "human language compatible" and much shorter (similar to "things I should buy" list of items I use when I go to shop).
ThinBASIC and many other newer BASICs offer this alternative syntax. Often being criticised by "BASIC hardcore guys", but I think these people forgot the purpose and focus too much on form they are used to.
Petr
Bookmarks