SoylentNews is people
SoylentNews
On one of those Simtel CDs I found Jorf. (Josephine's Recipe Filer). It was a OO language, with an interpreter for DOS or Windows, and it supported stuff that was really advanced for the time, and it made my coding a lot simpler.
Out of nostalgy, I downloaded a copy (yes, it is still there), and ran it in DosBOX (yes, it still works), to check if it was as good as I remembered.
You know what? It is.
In fact, if it had come out 2 or three years later, and as free software instead of shareware... I think it would have been big.
Here are some highlights og the language:
OOP
Has integrated windowing toolkit (for DOS and Windows)
It had an interactive hypertext/windowing tutorial written in itself. In 1993.
It looks like a cousin of Python. A freaky cousin, though.
-Comments start with |
-Strings limited with single or double quotes
-Automatic type conversions
-Intentation controls flow :-)
-No declared data types
-Integrated editor and debugger
The article author's native language seems to not be English, but it's a fun little piece on a language that might have been.
(Score: 2) by bzipitidoo on Tuesday October 20 2015, @12:54AM
I agree that C's switch statement is poor syntax. It's one of the gotchas that the execution path continues into the next case statement if there is no break statement. Ranks up near the newbie gotcha of using = when == was meant, and not getting any compiler error about the mistake because it is valid C to say "if (a=b)".
How about C's for statement? It doesn't look so bad at first, but there are some tricky details there too. A statement like "for (int i=0; i100; i++)" is an exception to the simple scoping rule that a variable is valid from the line where it is declared to the end of the block. "i" should only be valid within the body of the for statement. It was a bug in gcc up through version 2.7.2 that "i" was considered still in scope after the for block ended.