Sorry for that guys, but we didn't had the time to implement it on time for launch, this is one of our high priority for the next 1.5.1, that will be released ASAP.

Graynomad's description of interrupt capabilities is very accurate, but the current Arduino API (that we are going to implement) cannot be used to exploit all of them. An API update should be taken into account, but this is food for discussion on the developer's list on the coming weeks, for now we must stick to the current 1.0 API.

///////////////////////////////////////////////////////////////////////// Function name:PIOINTx_IRQHandler//// Description:Replacement for the default PORT0 interrupt handler.//// Parameters:none//// Returned value:none//// Errors raised:none//// Notes:The code has to determine the pin that caused the interrupt.//This is done by scanning the value in the MIS register//looking for a 1 bit. When found the corresponding user handler//is called if it exists.////Whether or not the user handler exists the interrupt is cleared.////Only a single interrupt at a time is called so an active pin//cannot hog the system. This is implemented by maintaining a//counter across invocations so for example if pin 4 is handled//this time the scan starts from pin 5 next time.////This method however has a side effect of increasing the latency//considerably in systems that only have 1 or 2 external interrupts,//for example after handling a pin 4 interrupt the next invocation//has to scan 31 bits before arriving back at pin 4.////This is largely reduced by writing 0 to the __force_interrupt_scan//variable. In this case the next scan starts from the pin the//last scan ended on.//// TODO:Implement a scan range to further reduce latency.//// Example://void PIOINT0_IRQHandler() {

Although I suspect that if I inserted the code from the function calls they would be similar. Note that this is a function that's part of my Arduino port, it maps the Arduino call to my LPC equivalent, that's really why there's no real work done here.

I work with a flat model of the pins, at this level I don't care what port they are on or anything. Also I'm implementing a system of "events" whereby everything that happens on the system is an event that can have a user function supplied if required. Pin interrupts are simply another 55 events.