(), but might be a problem in interrupt handlers (I am not an
expert though).
Thanks,
Vadim
> -Original Message-
> From: Luke Tierney [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 14, 2004 7:46 PM
> To: Vadim Ogranovich
> Cc: R-Help
> Subject: RE: [R] mkChar can be interrupt
5:43 PM
> > To: Vadim Ogranovich
> > Cc: R-Help
> > Subject: RE: [R] mkChar can be interrupted
> >
> > On Mon, 14 Jun 2004, Vadim Ogranovich wrote:
> >
> > > I am confused. Here is an excerpt from R-exts:
> > >
> > > "As from R 1
() and R_alloc() stand
up against long jumps?
Thanks,
Vadim
> -Original Message-
> From: Luke Tierney [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 14, 2004 5:43 PM
> To: Vadim Ogranovich
> Cc: R-Help
> Subject: RE: [R] mkChar can be interrupted
>
> On Mon, 14 Ju
On Mon, 14 Jun 2004, Vadim Ogranovich wrote:
> I am confused. Here is an excerpt from R-exts:
>
> "As from R 1.8.0 no port of R can be interrupted whilst running long
> computations in
> compiled code,..."
>
> Doesn't it imply that the primitive functions like allocVector, mkChar,
> etc., which
I am confused. Here is an excerpt from R-exts:
"As from R 1.8.0 no port of R can be interrupted whilst running long
computations in
compiled code,..."
Doesn't it imply that the primitive functions like allocVector, mkChar,
etc., which are likely to occur in any compiled code called via .Call,
are
On Mon, 14 Jun 2004, Vadim Ogranovich wrote:
> > -Original Message-
> > From: Luke Tierney [mailto:[EMAIL PROTECTED]
> > Sent: Monday, June 14, 2004 1:30 PM
> > To: Vadim Ogranovich
> > Cc: R-Help
> > Subject: Re: [R] mkChar can be interrupted
> >
> -Original Message-
> From: Luke Tierney [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 14, 2004 1:30 PM
> To: Vadim Ogranovich
> Cc: R-Help
> Subject: Re: [R] mkChar can be interrupted
>
> Not sure why you think this suggest mkChar can be interrupted.
>
Not sure why you think this suggest mkChar can be interrupted.
If you want to figure out how interrupt handling works on unix, run
under gdb and single step from the signal to the next point where
R_CheckUserInterrupt is called. You should find that the signal
handler sets a flag and that flag is
Hi,
As was discussed earlier in another thread and as documented in R-exts
.Call() should not be interruptible by Ctrl-C. However the following
code, which spends most of its time inside mkChar, turned out to be
interruptible on RH-7.3 R-1.8.1 gcc-2.96:
#include
#include
SEXP foo0(const SE
