NOTE: DCTEdit v0.04 [9]
 GW> I'll try. It's generally similar across all compilers that provide
 GW> interrupt support, and is not the same in C as C++.
Yeah? What are the differences, I've noticed you need '...' as the parameters 
to the function in c++ but nothing in c, is there anything else?
 VK>instruction. I would really like to be able to wait for an
 VK>interrupt to occur from within the interrupt function, but
 VK>waiting for it just makes it sit there forever.
 GW> You emphatically do not call an "interrupt" function and wait for the
 GW> interrupt to occur, rather the "interrupt" function should do the
I think I've written that message a bit sloppily, what I meant is wait in one 
interrupt's function for a different one to occur which will have it's own 
function. But Just today I found that using that onmask/offmask stuff with 
the PIC, seems to fix the problem(After I'd already written a workaround :( 

... I have no idea what I'm doing out of bed.
--- Maximus 3.01
---------------