Comments on: MEX ctrl-c interrupt

By: Pavel Holoborodko

Pavel Holoborodko — Sat, 02 Jul 2016 10:23:44 +0000

In reply to Ander Biguri. It depends on where you call it. If you call it in a loop with small code size - slowdown might be significant (extra conditional & far jump to non-inlined function call). Check the second section of the article for more details: Proper Handling of Ctrl-C in MEX Module

By: Yair Altman

Yair Altman — Mon, 20 Jun 2016 08:28:59 +0000

In reply to Ander Biguri. @Ander - I do not believe that you will detect any noticeable performance decrease when using this mechanism.

By: Ander Biguri

Ander Biguri — Mon, 20 Jun 2016 08:09:54 +0000

Thanks for the post, very useful!
Any insight on how does this function affect the global performance of the mex function?

By: Jeremy Johnson

Jeremy Johnson — Fri, 17 Jun 2016 16:49:44 +0000

I know you don’t usually discuss Simulink here, but would it be safe to assume that this applies to S-Functions as well since they are very similar to MEX functions?

By: Jon Chappelow

Jon Chappelow — Wed, 15 Jun 2016 22:56:12 +0000

I only knew of 2: utIsInterruptPending and utSetInterruptPending. The two classes, utInterruptMode and utInterruptState, are news to me. Very cool!

Since using them requires linking with libut, I include this library in the link list in my VS property sheets. See here for details: http://stackoverflow.com/a/27391300/2778484

Thanks for the post, Yair!