7 replies to this topic

[pathtotake]

I'm learning about event driven programming at college but the teacher, and wikipedia... and everywhere else seems to give really general information on:

callback routines
interrupts
interrupt handlers
embedded systems
software layers


I need to write two pages on this, and general information is not enough for me to write two pages...
for example... in hardware interrupts... where are they generated, how are they generated in the hardware? what does a software interrupt code even look like? Where is an interupt handler code (if there is code) held?

also, this is from wikipedia :
"An interrupt handler is a low-level counterpart of event handlers."
what's the difference between the two, and what do they mean by low-level?

[Steve.L]

pathtotake said:

I'm learning about event driven programming at college but the teacher, and wikipedia... and everywhere else seems to give really general information on:

callback routines
interrupts
interrupt handlers
embedded systems
software layers


I need to write two pages on this, and general information is not enough for me to write two pages...
for example... in hardware interrupts... where are they generated, how are they generated in the hardware? what does a software interrupt code even look like? Where is an interupt handler code (if there is code) held?

also, this is from wikipedia :
"An interrupt handler is a low-level counterpart of event handlers."
what's the difference between the two, and what do they mean by low-level?

Cool. I don't see how this is relevant to this forum. Looks like you have a lot of reading to do bud. We don't do homework for you.

[dcs]

pathtotake said:

I'm learning about event driven programming at college but the teacher, and wikipedia... and everywhere else seems to give really general information on

I think your following approach is the correct one -- to list specific things you would like clarified.

pathtotake said:

for example... in hardware interrupts... where are they generated, how are they generated in the hardware?

As it shows here, there are many ways in which an interrupt might be generated. Some event happens, such as the change of state on a pin, and when the CPU detects it (skipping other details for the moment), it generates an interrupt. This interrupt tells the CPU to finish its instruction, push some registers, and vector off elsewhere -- to an interrupt service routine.

pathtotake said:

what does a software interrupt code even look like?

A special machine instruction that does the same thing as an external hardware interrupt: causes the CPU to vector to an ISR.

pathtotake said:

Where is an interupt handler code (if there is code) held?

That depends on the architecture.

pathtotake said:

also, this is from wikipedia :
"An interrupt handler is a low-level counterpart of event handlers."
what's the difference between the two, and what do they mean by low-level?

In interrupt handler (or ISR) is code that will be executed when some hardware event occurs. An event handler is code that will be executed when software detects an event and executes code associated with the event -- possibly a callback.

[marwex89]

Steve.L said:

We don't do homework for you.

YES, we do :) Check out MeTh0Dz' "Homework for lulz" thread :P

[MeTh0Dz]

Lol yeah, but that's just me liking to lul at easy code and taking a break from hard ****.

[marwex89]

So programming-history assignments are not done?

[MeTh0Dz]

**** no. I'm only coding.

[marwex89]

Ok, seems like pathtotake has to do it himself, then ;)