Monday, April 27, 2009

Interrupt

In our department there's a term that we focus on this year, so much in nearly all subjects it's called interrupt and what interrupt basically do is that if you're executing a certain sequence of code or executing in a certain order of processes .. if you recieve an Interrupt at any time and whatever you're doing, you simply leave all what you're doing and head to executing another process or another arrangement of code.

If i consider my life as a sequence of executable code .. the question lies here shall i be afraid of an interrupt or waiting for one.

No comments: