Re: [Rd] Capturing signals from within external libs

2012-05-23 Thread Jeffrey Ryan
Simon, Very likely butchered my initial problem explanation. The issue is that I make a call to a library, something like: SEXP my_fun() { ... CB = MyCallback("XYZ"); /* this contains callback functions that in turn use R */ externalLibCall(CB); /* infinite loop that won't return as it is ca

Re: [Rd] Capturing signals from within external libs

2012-05-23 Thread Simon Urbanek
On May 23, 2012, at 12:40 PM, Jeffrey Ryan wrote: > Simon, > > Thanks for the clarifying example. I fear my current set up fails the > test for 'no R calls', Well, but in that case you already have interrupt points so I'm not sure what is the problem? I thought the whole point is that you hav

Re: [Rd] Capturing signals from within external libs

2012-05-23 Thread Jeffrey Ryan
Simon, Thanks for the clarifying example. I fear my current set up fails the test for 'no R calls', so I think I am stuck on the ugly variant for my current challenge, but I will be able to use this in other places. Thanks again, Jeff On 5/22/12 4:45 PM, "Simon Urbanek" wrote: >Jeff, > >On Ma

Re: [Rd] Capturing signals from within external libs

2012-05-22 Thread Simon Urbanek
Jeff, On May 22, 2012, at 4:31 PM, Jeffrey Ryan wrote: > I have a continuous loop running in an external library that I am calling > from C (R API). This loop is processing events in real time with the > possibility of significant lag between events. > > When processing an event, I can make use

[Rd] Capturing signals from within external libs

2012-05-22 Thread Jeffrey Ryan
I have a continuous loop running in an external library that I am calling from C (R API). This loop is processing events in real time with the possibility of significant lag between events. When processing an event, I can make use of R_CheckUserInterrupt, but while the external library code is wa