Re:Oberon (2009)
by 082349872349872 on Friday August 26, 2022 @09:06AM
(#32606947)
> ...all memory accesses are indirect ... module-data is position independent and may be moved in case memory should fail due to radiation damage.
I once used a debugger that shipped with a rather snarky easter egg command: "find my bug". One of its more useful suggestions was "Maybe a cosmic ray error? Use smaller chips!".
Wouldn't smaller chips make the problem worse?
Re:Oberon (2009)
by 082349872349872 on Friday August 26, 2022 @01:24PM
(#32610341)
I think it jocularly meant "use something with fewer gates and a smaller cross section", not "use a smaller feature size". Or I could easily have misremembered: this was all last century.
Re:Oberon (2009)
by AnimalMuppet on Friday August 26, 2022 @02:20PM
(#32610953)
> Or I could easily have misremembered: this was all last century.
Don't understate the difficulty of remembering. This was all last millennium.
Important not to also understate that some of us spent more time in the former than the current.
True! Smaller and closer the units, more probability that the particle would hit something useful.
Re:Oberon (2009)
by i_don_t_know on Friday August 26, 2022 @11:30AM
(#32608788)
Interestingly, one of the authors (Felix Winkelmann) created Chicken Scheme and their Oberon compiler appears to be written in it.
That's an interesting paper, thanks for the link. Though the resulting language is barely Oberon anymore, since even type extension is removed, not only dynamic memory management (and with it the GC). It seems to have less features than Oberon-0 described in Wirth's compiler book.
https://arxiv.org/abs/1709.03404v1