[Oberon] ETH Oberon source and module SYSTEM

[eas lab]

]Please don't reply using the subject RISC5 and then talk about ETH Oberon,
]it's confusing.

Since the glorious revolution, many people who can read & write have emigrated,
& ISPs have collapsed & TexMail.* doesn't work with gmail & I just must take
<any buss that passes>.

]> in all cases the path is concealed at: IMPORT SYSTEM.
]> Some of us resent that. Oberon may have had a better following if
]> it had been open. OTOH perhaps that was not possible?

]Sorry, but that's complete rubbish.

]......It's documented in the Oberon language report (any
]version).

Thanks!! That enabled me to RE-locate it.

]By the way, the only "concealed" sections of the original Oberon system,
]ie not included in the Project Oberon book, were the Kernel and Display
]driver, which were written in machine-code, and thought to be arcane and
]of little general interest at the time.  (As stated in the preface to the
]new edition, this is no longer the case, Kernel and Display for the RISC
]are written in Oberon.)

So then, if the SYSTEM calls are implemented in <native machine-bytes>,
what's to stop simple-direct-porting to ARM, other than the real-time
constraints of the VGA drivers - perhaps?

== Chris Glur.

On 4/18/14, Paul Reed <paulreed at paddedcell.com> wrote:
> Chris,
>
>> Today I tried to trace the M.P route of how eg. ET.* gets to the
>> VGA-port.
>> [Like you CAN trace how http* arrives via a serial-port-modem ...etc.]
>> For ETH Oberon (2.4.3) for Linux x86   and
>> V4/oberon-1.7.02/Source  and my
>>  source1, 2, 3.arc  which I guess comes from Native;
>
> Please don't reply using the subject RISC5 and then talk about ETH Oberon,
> it's confusing.
>
>
>> in all cases the path is concealed at: IMPORT SYSTEM.
>> Some of us resent that. Oberon may have had a better following if
>> it had been open. OTOH perhaps that was not possible?
>
> Sorry, but that's complete rubbish.
>
> SYSTEM is a pseudo-module intended to enable non-portable features of the
> Oberon language.  It's documented in the Oberon language report (any
> version).
>
> By the way, the only "concealed" sections of the original Oberon system,
> ie not included in the Project Oberon book, were the Kernel and Display
> driver, which were written in machine-code, and thought to be arcane and
> of little general interest at the time.  (As stated in the preface to the
> new edition, this is no longer the case, Kernel and Display for the RISC
> are written in Oberon.)
>
> Thanks,
> Paul
>
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>