0 Members and 1 Guest are viewing this topic.
I'm not using a register, although refresh is a good idea.
Hmm, is there a way to detect if a BSoD byte is sent? If it is, maybe KOS could cancel it as soon as it's detected...
So, an entirely different subject. How do you manage multi-threading? I really have been wrecking my brain over it...I assume you use time-division multiplexing? But then again where do you leave/store all the 'shadow' Program Counters?Also, how many threads will KOS support eventually or is it basically unlimited (despite significant slowdown)
I also have crash alerts, where it will apologize to the user for crashing and try to recover the previous state.
*BLOD
*jaw drops* Awesome!!! "Sorry, your calculator just crashed. Trying to recover..." That would be nice. Does it ask to recover? How does it recover?
BSOD on the 83+SE. Instead of a few blue lines, the entire screen turns blue in test mode.
*BLODI also have crash alerts, where it will apologize to the user for crashing and try to recover the previous state.Quote from: matthias1992 on November 17, 2010, 06:41:51 amSo, an entirely different subject. How do you manage multi-threading? I really have been wrecking my brain over it...I assume you use time-division multiplexing? But then again where do you leave/store all the 'shadow' Program Counters?Also, how many threads will KOS support eventually or is it basically unlimited (despite significant slowdown)20 threads max. As for multithreading, I use interrupts to switch threads, and push all the registers to the stack during the interrupt. Then, I change the value of SP to point to a different thread's stack, pop all the registers, and RET. That's the small and simple explanation.
Brings up another question. Can a program consume more then one thread? or will threads only be initiaded when a other task comes in?