Quote:
Originally Posted by Thomas Richter
but the facts should be correct - and this is not the case here.
|
This has been a consistent pattern for litwr. And he tends to not actually change his mind all that much when the facts disagree with his opinions. Just look at this thread for some examples. The 'discussion' about the OS 'interfering' with the hardware timers is a pretty good example here (to recap: the issue was that litwr blamed the Amiga/OS for a problem, rather than admitting the real problem was his ignorance of how to properly code with the OS running).
Quote:
|
This is not much different from TOS, but since TOS is a single-tasking system, it can re-initiate the complete machine after the "bombs". On a multi-tasking system, one cannot do that without affecting other programs.
|
Well, this is partially true. But as an ex-ST user, I can tell you that the reality is that "bombs" tend to mean "system crash".
I mean, just consider the case presented by litwr here: far from TOS informing you a 68020 only instruction was encountered and continuing to work without problem*, in reality TOS displays 4 bombs when it encounters any illegal instruction (including 68020 instructions on a 68000) and then ignores the instruction.
It certainly doesn't continue without issue. After all, the real world result of randomly ignoring instructions can be guessed, but just in case other people reading the thread might wonder: ignoring random instructions almost always means your code will crash the system sooner rather than later. And if not, it certainly won't work as expected regardless.
*) litrw literally wrote "The Atari ST OS works much better, in such cases it just informs you about the problem and continues working!". This is 100% false information, TOS does not contain a 68020 emulator and doesn't handle illegal instructions any better than Amiga OS.