[Oberon] Re. "rock solid"/reliable software:

eas lab lab.eas at gmail.com
Fri Nov 7 03:07:43 CET 2014

]Ada had that declared aim. Is it still alive?
]Wirth advocated simplicity; if the whole-picture is small enoungh,
]   you can *see* the faults. But few tasks can be kept small enoungh.
]Eiffel introduced checking mechanisms beyond strict typing, but nobody
]  seemed interested.

It seems that WS's  "rock solid" does not refer to reliability, but RealTime.
In that case: ETHO [both S3 & V4] fails.
Can any system that needs Garbage Collection be trusted?
rPi can be quiet confusing to users who don't realise that it's not a light
that directly switches, but needs to read and schedule the instructions.

Was NW's helicopter-system interrupt driven?
I vaguely remember that the 'pic code', was nice and simple.
Isn't A2 about a more complex multiproc-system, than ETHO's simple loop?

== Chris Glur.

More information about the Oberon mailing list