[Rcpp-devel] Interrupts in compiled code.
Dirk Eddelbuettel
edd at debian.org
Thu Jan 27 02:33:52 CET 2011
On 26 January 2011 at 16:10, Davor Cubranic wrote:
| On 2011-01-24, at 6:53 PM, Dirk Eddelbuettel wrote:
|
| > On 24 January 2011 at 15:36, Davor Cubranic wrote:
| > | Actually, the interrupt seems to be caught only the first time I enter "foo". When I call it the second time from the prompt, no handler is activated -- I'm not sure why.
| >
| > Code such as the one shown below was only ever meant to catch one interrupt
| > signal such as Ctrl-C for abort. Upon catching the signal I usually wind the
| > program down. So I never tried what you are attempting here: to actually be
| > "reentrant" and catch the same signal multiple times. Let us know how it
| > goes and what you find :)
|
| Do you mean that this pattern only applies to stand-alone programs?
That was the context in which I used them.
I'd think one should be able to generalize this but I haven't done that
myself.
Dirk
--
Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com
More information about the Rcpp-devel
mailing list