[Oberon] A new dialect? Oberon+ (OBX)

[Charles Perkins]

I found the strategy for generics interesting and approachable with the
specialization occurring over a module as a whole and the selection
occurring on module import.

If generic modules are not compiled on their own but are only compiled
(with an .rsc file generated just for that concrete type) when the module
that imports it is compiled, then the combinatorial explosion of generated
code can be limited to just those types actually used. If the generic
module was already coerced to be compiled for that type by a different
importing module (or the same one previously,) and the .smb files are
compatible then it doesn't have to be compiled again.

It seems to me to be in the spirit of Oberon -- as simple as possible but
no simpler.

Chuck

On Fri, Jul 16, 2021 at 9:03 AM Liam Proven <lproven at gmail.com> wrote:

> https://oberon-lang.github.io/
>
> --
> Sent from my smartphone. Please pardon brevity & typos.
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20210716/658cfc7a/attachment.html>