The Oberon+ Programming Language
oberon-lang.github.io
The Oberon+ Programming Language
1–10 of 116 posts
Re: The Oberon+ Programming Language
#2Any relation to the Oberon operating system?
Re: The Oberon+ Programming Language
#3I don’t like how verbose Pascal-like languages are. I don’t want to have to type tons of keywords to get anything done. Curly brackets are a big improvement over pairs of “begin” and “end” all over. Makes it hard to see the forest for the trees when skimming some code to figure out what it does. That on its own makes something like this a complete nonstarter for me, leaving aside issues like support, quality of implementation, uptake, etc.
Re: The Oberon+ Programming Language
#4The funniest thing i see is programmers are getting prroblems to grok functional programing concepts.
Re: The Oberon+ Programming Language
#5I thought the background context by the author was interesting to read:
https://oberon-lang.github.io/2021/07/15/motivation-for-a-ne...
Re: The Oberon+ Programming Language
#6Any relation to the Oberon operating system? https://en.wikipedia.org/wiki/Oberon_(operating_system)
Only the language part of it
Re: The Oberon+ Programming Language
#7I don’t like how verbose Pascal-like languages are. I don’t want to have to type tons of keywords to get anything done. Curly brackets are a big improvement over pairs of “begin” and “end” all over. Makes it hard to see the forest for the trees when skimming some code to figure out what it does. That on its own makes something like this a complete nonstarter for me, leaving aside issues like support, quality of imple…
I think it's less about typing them and more about reading them. Curly braces reduce the number of keywords in the language (unless the alternative is indentation sensitivity like in Python or Haskell). This means that if I see a word, it is easier to infer if it is a variable name or if it does something structural.
How about a treesitter-based editor extension that converts between begin/end and {/}, as if they were ligatures? Actually this might not even need treesitter.
Re: The Oberon+ Programming Language
#8I was looking for coroutines. Modula had them, but I couldnt find them here. Just a note I mean coroutines, not preemptive threads.
Here is how it looks like in Modula-2.
https://www.modula2.org/reference/isomodules/isomodule.php?m...
Re: The Oberon+ Programming Language
#9I don’t like how verbose Pascal-like languages are. I don’t want to have to type tons of keywords to get anything done. Curly brackets are a big improvement over pairs of “begin” and “end” all over. Makes it hard to see the forest for the trees when skimming some code to figure out what it does. That on its own makes something like this a complete nonstarter for me, leaving aside issues like support, quality of imple…
Code is read much more times than written, and hieroglyphs don't help.
Re: The Oberon+ Programming Language
#10I don’t like how verbose Pascal-like languages are. I don’t want to have to type tons of keywords to get anything done. Curly brackets are a big improvement over pairs of “begin” and “end” all over. Makes it hard to see the forest for the trees when skimming some code to figure out what it does. That on its own makes something like this a complete nonstarter for me, leaving aside issues like support, quality of imple…
apart from that (which i agree with) is that in most pascal-like languages you have to define variables at the top of a function, and their scope is the whole function. both c (nowadays, define at top of a {} scope) and c++ (define anywhere inside a function) do much better which, together with irritating long names, may explain why c and c++ won out over the pascal-likes.
speaking as an ex professional delphi programmer here - i have written lots of object pascal code, and have no desire to write any more.