specification

A proc is a function with no return. A function is a function that returns something. Oberon+ keeps it's predecessors' idiotic distinction, but takes it one step further: both functions and procedures are decalred with `proc` or `procedure`, functions are `proc`s that have a return type. And yet: - procedure calls don't have to specify parameters apparently, but function calls must specify all parameters - functions cannot be used in Oberon+'s weird exception handling. [1] You do a call with `PCALL(res, P, args)` where res is a variable that will hold the result of the exception if it happened, and P is the procedure. You cannot pass functions (aka procedures which have a return type) As the spec so wonderfully says [2], --- start quote --- There are two kinds of procedures: proper procedures and function procedures. The latter are activa

Oberon and Oberon+ are very interesting and are certainly a step forward from Pascal. Wish Oberon+ had moved forward a few more steps, like making everything an expression, for example, or more lax variable declaration rules (which probably require scoping rules changes). If only the FPC compiler supported it and allowed combining units in Oberon with Pascal ones in one project! The language specs: https://github.com/oberon-lang/specification/blob/master/The...