RetroBASIC
Retrogamecoding(.org) => Other Languages => Topic started by: Tomaaz on October 21, 2018, 08:10:03 PM
-
Has anyone tried Icon? It's been around for a while (41 years), but it doesn't look dated. Last stable release is 5 years old but it's being maintained by people from The University of Arizona. Just a month ago Icon has been re-validated for new version of Ubuntu and MacOS. There is also a Windows version of Icon. It's extremely well documented, comes with a set of libraries and is simple to use. No OOP, just old-school procedural stuff. Website - https://www2.cs.arizona.edu/icon/ .
-
I did try it 20 or so years ago, it was interesting. It was also expanded by Unicon: https://unicon.sourceforge.io/ (https://unicon.sourceforge.io/) which I played with off and on for a while and even bought the book for although the book was sold during a move. I always was a sucker for odd languages.
-
It looks like they don't have else if...
-
Yeah, I see if-then-else but no elseif.
-
Excuse my ignorance, but what's special about Else If?
-
It's a part of majority of languages?
-
In this instance probably not much since I do see a case statement, but to me either is cleaner looking than a list of if-then's.
-
Well as I understand it - and correct me if I'm wrong - but BASIC is generally built (for IF) with IF <condition> THEN <statement> ELSE <statement> and since IF itself constitutes a statement, then IF x THEN y ELSE IF z THEN a etc etc is perfectly fine?
-
In this instance probably not much since I do see a case statement, but to me either is cleaner looking than a list of if-then's.
Case statement can't replace every else if scenario.
Well as I understand it - and correct me if I'm wrong - but BASIC is generally built (for IF) with IF <condition> THEN <statement> ELSE <statement> and since IF itself constitutes a statement, then IF x THEN y ELSE IF z THEN a etc etc is perfectly fine?
Unless y and a are complex multi-statement blocks.