3 ms·
Apart from wondering where this sprang from, if anyone wonders why AmigaDOS was such an ugly fit with the rest of exec and written in BCPL not C: They'd contra
by anexprogrammer 10y ago
Apart from wondering where this sprang from, if anyone wonders why AmigaDOS was such an ugly fit with the rest of exec and written in BCPL not C:
They'd contracted a SV company to produce CAOS, to a spec of Carl Sassenrath - the creator of exec (OO multi-tasking kernel). As deadline got closer and closer it was clear it wasn't happening, or even close. It was meant to get resource tracking and some other features to integrate with exec.
Edit: Found the spec and story of CAOS: http://www.thule.no/haynie/caos.html http://www.thule.no/haynie/caos.html
It got AmigaDOS - a port of Tripos from UK company Metacomco. It got that because no one else they asked believed they could deliver anything in the remaining time. That's why there was all the BCPL weirdness with DOS.
- a_thro_away 10y agoThanks for that; that was so difficult for then young, untrained me to get my head around, as well as reading the Amiga Reference Manuals - it was all so foreign.
- anexprogrammer 10y agoTripos started on PDP11, but had already been ported to 68k - just needed the exec glue code. Don't think the story ever properly came out but you get the impression it was the week or weekend before. :) The weird data thing was because of BCPL language - it only understood words, not bytes.