Hello,
I am writing an R interface for one of my C++ programs. The computations
in C++ are very time consuming (several hours), so the user needs to be
able to interrupt them. Currently, the only way I found to do so is
calling R_CheckUserInterrupt() frequently. Unfortunately, there are
On 24.04.2011 23:10, cstrato wrote:
Dear Uwe,
On 4/24/11 10:37 PM, Uwe Ligges wrote:
On 24.04.2011 20:59, cstrato wrote:
Dear Uwe,
Thank you for your reply.
ad 2, Yes, i know that xps-manual.pdf is the collection of help pages,
I have mentioned it only to show that creating pdf-files
Good afternoon,
As a clarification does it make sense to remove the second 'not' in the 'See
Also' documentation for file_test ?
Kind regards,
Sean O'Riordain
-
Index: src/library/utils/man/filetest.Rd
===
---
On Apr 25, 2011, at 11:09 AM, schattenpfla...@arcor.de wrote:
Thank you for your response, Simon.
1. Calling R_CheckUserInterrupt() interrupts immediately, so I have
no possibility to exit my code gracefully. In particular, I suppose
that objects created on the heap (e.g., STL containers)
Actually, it just came to me that there is a hack you could use. The problem
with it is that it will eat all errors, even if they were not yours (e.g. those
resulting from events triggered the event loop), so I would not recommend it
for general use. But here we go:
static void chkIntFn(void
On 2011-04-25 08:47, Sean O'Riordain wrote:
Good afternoon,
As a clarification does it make sense to remove the second 'not' in the 'See
Also' documentation for file_test ?
Both versions make sense to me; it's just a question of
whether we think of testing for x 'being a directory'
or for x
Dear Uwe,
Your suggestion to look at the Sweave manual helped me to solve the
problem. It seems that in R-2.13.0 every chunk can use the code from the
chunk before but not from an earlier chunk.
Concretely, the following does not work since chunk 5 needs the code
from chunk 3 and 4:
cstrato wrote:
Dear Uwe,
Your suggestion to look at the Sweave manual helped me to solve the
problem. It seems that in R-2.13.0 every chunk can use the code from the
chunk before but not from an earlier chunk.
I'm either misreading what you wrote, or it's wrong. If I have this in
a Sweave
On Monday 25 April 2011, Simon Urbanek wrote:
Actually, it just came to me that there is a hack you could use. The
problem with it is that it will eat all errors, even if they were not
yours (e.g. those resulting from events triggered the event loop), so I
would not recommend it for general
Dear Duncan,
Thank you for your example, however it is different since it does not
use x and y. What about print(x+y)?
Sorry, I do not believe that there is a bug in my code, since:
1, it worked in all versions from R starting with R-2.6.0 till R-2.12.2.
2, the identical code works in the
cstrato wrote:
Dear Duncan,
Thank you for your example, however it is different since it does not
use x and y. What about print(x+y)?
Try it.
Sorry, I do not believe that there is a bug in my code, since:
1, it worked in all versions from R starting with R-2.6.0 till R-2.12.2.
2, the
Thank you.
My problem seems to be that at the moment the problem can be seen only
on my Mac, since e.g. the Bioconductor servers have no problems creating
the vignettes.
Best regards
Christian
On 4/25/11 8:55 PM, Duncan Murdoch wrote:
cstrato wrote:
Dear Duncan,
Thank you for your
On 25/04/2011 3:16 PM, cstrato wrote:
Thank you.
My problem seems to be that at the moment the problem can be seen only
on my Mac, since e.g. the Bioconductor servers have no problems creating
the vignettes.
Then you are definitely the one in the best position to diagnose the
problem. Use
Thank you, I will try. Christian
On 4/25/11 9:31 PM, Duncan Murdoch wrote:
On 25/04/2011 3:16 PM, cstrato wrote:
Thank you.
My problem seems to be that at the moment the problem can be seen only
on my Mac, since e.g. the Bioconductor servers have no problems creating
the vignettes.
Then
Dear Simon,
thanks again for your explanations. Your previous e-mail clarified
several points for me.
Actually, it just came to me that there is a hack you could use. [...]
That actually looks quite nice. At least when compared to my currently
only alternative of not interrupting at all. I
15 matches
Mail list logo
