similar to: Catching warning and error output

Dear R developers, this mail is basically a summary / clarification of some previous mails I sent to this list last week (subject "Catching warning and error output"). Duncan Murdoch pointed out that these were badly organized, and suggested I repost, collecting the main points previously spread out between several mails. Problem statement: In an application embedding R, I would

Hi I try to develop a R interface to a set of C routines, in order to produce a R-package on Geostatistics. My C-code uses interaction with the user as I use printf and gets statements. I develop the code in a LINUX environment and do not face any problem having the questions and answers routed on my current Terminal. When I tried to port the package on Windows, the problems began. No message

In R-2-4-branch r39548, Rcons_vprintf is called from stdout_vfprintf when R_Outputfile is NULL. When called and output is greater than R_BUFSIZE, output is truncated to R_BUFSIZE. Here's a one-line fix: Index: src/main/printutils.c =================================================================== --- src/main/printutils.c (revision 39548) +++ src/main/printutils.c (working

Hi all, I have been trying to add the line: h = n - p0 + 1; just after h = n / 2 + 1; (line 131) in the source code (the original paper mention this is possible for p0<n). with p0 declared as an int (actually i used the same declaration protocol as n everywhere in the code). The "new" source compiles, but when i give it reasonable values of p0, it runs unto

I have the following contrived code in package format. On Solaris and Mac OS X, code runs just fine. On Windows, it crashes the R environment with the "Send Bug Report" dialog. I tried R 1.8.1 (Win2K) and R 1.9 (WinXP) binaries with the same result. PCs otherwise appear properly configured for creating R packages. Anything blatantly wrong? Suggestions? TIA Relevant files from package

Hi, I'm currently trying to use R as a back-end from an interface (you may have seen me on the help list), and I'm running into something that is rather confusing. The following lines in main/errors.c of R 1.5.1: 439: if ( !R_Interactive && !haveHandler && inError ) { 440: REprintf("Execution halted\n"); 441: R_CleanUp(SA_NOSAVE, 1, 0); /*

On Sun, 15 Sep 2019, Jan Gorecki wrote: > Dear R-devel community, > > There appears to be an inconsistency in R C API about the exceptions > that can be raised from C code. > Mapping of R C funs to corresponding R functions is as follows. > > error -> stop > warning -> warning > REprintf -> message This is wrong: REpintf is like cat with file = stderr().

You can file it as a wishlist item in the bug trackign system. Without a compelling case or a complete and well tested patch or both I doubt it will rise to the top of anyone's priority list. Best, luke On Sun, 15 Sep 2019, Jan Gorecki wrote: > Thank you Luke for prompt reply. > Is it possible then to request a new function to R C API "message" > that would equivalent to

Dear R-devel community, There appears to be an inconsistency in R C API about the exceptions that can be raised from C code. Mapping of R C funs to corresponding R functions is as follows. error -> stop warning -> warning REprintf -> message Rprintf -> cat Rprint/cat is of course not an exception, I listed it just for completeness. The inconsistency I would like to report is

Full_Name: Russell Senior Version: 0.64.0 OS: linux-2.2.x Submission from: (NULL) (198.107.133.11) It appears that the GNU readline history size is limited to 50 entries. This is apparently occurring because R is not bothering to override the readline default value (from readline-4.0): ./history.c:59:#define DEFAULT_HISTORY_GROW_SIZE 50 It appears that it ought to be possible to override

I would like to redefine some R print functions (Rprintf for example) so that they don't print to stdout, but save the output in a global string array. I can compile and link my definition of Rprintf into a library and load it with dyn.load. I don't get an error message, but afterwards the original function is still valid, my new version isn't executed. Is there a way to change R

Thanks - I'll find another way to send messages to the main thread for printing. -Winston On Tue, Nov 21, 2017 at 12:42 PM, <luke-tierney at uiowa.edu> wrote: > On Tue, 21 Nov 2017, Winston Chang wrote: > >> Is it safe to call Rprintf and REprintf from a background thread? I'm >> working on a package that makes calls to fprintf(stderr, ...) on a >>

Thank you Luke for prompt reply. Is it possible then to request a new function to R C API "message" that would equivalent to R "message" function? Similarly as we now have C "warning" and C "error" functions. Best, Jan On Sun, Sep 15, 2019 at 5:25 PM Tierney, Luke <luke-tierney at uiowa.edu> wrote: > > On Sun, 15 Sep 2019, Jan Gorecki wrote:

When large calls cause errors R may stall for extended periods.? This is particularly likely to happen with `do.call`, as in this example with a 24 second stall: ??? x <- runif(1e7) ??? system.time(do.call(paste0, list(abs, x)))? # intentional error ??? ## Error in (function (..., collapse = NULL)? : ??? ##?? cannot coerce type 'builtin' to vector of type 'character' ??? ##

Is it safe to call Rprintf and REprintf from a background thread? I'm working on a package that makes calls to fprintf(stderr, ...) on a background thread when errors happen, but when I run R CMD check, it says: Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor the system RNG. Is it safe to replace these calls

In some code that I have written, use of url() is generating the output line: "cannot open: HTTP status was `404 Not Found`" The problem is that I do not want R to be outputting any error messages - I have 'internet.info' set to 3, show.error.messages set to FALSE and the url() wrapped in a try(). When the URL is not found I am already handling it in a manner consistent with

Luke, thanks for considering the issue.? I would like to try to separate the problem into two parts, as I _think_ your comments address primarily part 2 below: 1. How can we avoid significant and possibly crippling ?? stalls on error with these non-standard calls. 2. What is the best way to view these non-standard calls. I agree that issue 2. requires further thought and discussion under a

Hi! I have an application embedding R. For that of course, it is great, that since R 2.1.0 the pointers in Rinterface.h allow me to override some callbacks, easily. However, after implementing/overriding a couple of those, I'm a bit confused about when exactly they get called. So, here are a few specific questions: ptr_R_EditFile: I can find exactly one point in the R-sources where

Hi all, While compiling R to RISC-V64 architecture and debugging in R's C source codes, I think I have found a small bug. Can anyone please verify whether it is a real bug? The possible bug lies in the file `R-4.2.2/src/library/stats/src/approx.c` in function `R_approxfun` around line 148: #ifdef DEBUG_approx REprintf("R_approxfun(x,y, nxy = %.0f, .., nout = %.0f, method = %d,

Dear list, I am trying to embed R into a C++ program. After some tinkering, reading the documentation and browsing the source code I have this more or less working. A very very condensed and very simplified version of the code is included below. The program can create plots. However, after the plot is initially drawn it is no longer updated. When scaling or updating the plot the window becomes