[Oberon] Portings Texts.Mod to Oberon-7, my Artemis project
Oleg N. Cher
allot at bk.ru
Thu Jun 17 04:39:30 CEST 2021
You may not have known this, but Ofront by Josef Templ has a successor -
this is the Ofront+ (https://github.com/Oleg-N-Cher/OfrontPlus). It
supports various UNIX-like (both 32-bit and 64-bit), as well as macOS
and Windows. Also I tested this under Linux Armbian on Orange Pi PC Plus
Also it has five input languages, including Oberon-07/16 and Component
Pascal. The support for Oberon-07 was done rather hastily, I can't call
it completed. But I'm interested in improving it. Therefore, I would be
very grateful if you take Ofront+ as one of the translators for build
It should probably be noted here that I am interested in the industrial
application of Oberon-07, and not in academic adherence to the canons of
extreme simplicity. So I will support both language extensions and also
things that seem reasonable to me.
Also, I just recently thought about the need to support UTF-8 as one of
input text format for Ofront+. I do not know what this might look like
in Oberon-07, where the CHAR type size is not fixed, which is likely to
cause a lot of problems. But I will probably have to develop something
like the Texts module, which should support at the input ANSI, UTF-8
encoded text, and I will definitely need support of the .odc format from
BlackBox Component Builder. The output will be a two-byte CHAR type.
even more than sure that you don't need support of .odc format, as
well as Component Pascal language. But I decided to inform you anyway.
Thank you for developing Artemis, I will follow your development.
Robert Doiel пишет:
> This list discussion around Oberon Texts has been inspiring. It is been so
> inspiring I've create a GitHub repository named Artemis:
> > Artemis is an Oberon-7 module collection. My hope is
> > to encourage continued use and development of the Oberon-7
> > language and encourage convergence towards compatibility
> > in implementations of Oberon-7 compilers.
> This ties back to the Texts discussion in one significant way. I am
> to port both S3 (Native Oberon) Texts.Mod and V4 (Linz) Texts (Texts.Mod,
> Elem.Mod, etc) to Oberon-7. That code will wind up in Artemis and be
> used to
> implement an "ocat" (like Joseph Templ's ocat from ofront) that will
> work for
> each of the type of Texts.
> I've looked at each implementation and I think unifying them is beyond my
> skill but porting each one would be extremely useful, especially from a
> preservation point of view.
> I am not promising fast (or successful) development. I am one of those
> dreaded hobbyist when it comes to Oberon. I think the collection will be
> useful as it evolves. It is likely to hold my interest for quite some
> I think it will be especially for useful for fellow novices exploring
> Oberon-7 on POSIX.
> Feed back welcome, criticism is helpful, pull request exciting. You can
> reach me on this email list and via GitHub issue
> All the best,
> Robert Doiel
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
More information about the Oberon