similar to: Printing to file from C

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

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 >>

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

Hello all, I am getting into trouble when trying to do standard I/O from a C function called within R environment. This function is written in a small C library that is loaded whith dyn.load() and called in R via the .C() interface. I need to debug the C code using a text file for some logs, and also to speed up its result visualization by creating images on the fly using the GD library. Both

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:

Dear R-devel, My g++ complains about the first argument to Rprintf being non-const char *. For example when compiling the line Rprintf("hello world\n"); the following warning is emitted: warning: deprecated conversion from string constant to 'char*' Is there a reason for the non-const? It is curious that Rf_error, which is similar to RPrintf, is const. If there is a need

Hello, I've noticed that with g++ 4.3 I get the following "warning: deprecated conversion from string constant to ?char*?" when I call e.g., Rprintf("Hello world"); or when I try to define a const char e.g., char lower = 'L'; I am wrapping the c++ code in extern "C" {}. This seems to be something new with g++ 4.3, because the same code compiled

People of cygwin & rsync, I recently attempted to get cygwin and rsync working to solve a backup/mirroring need in my computer life. Well, as you might guess, I ran into a little but of trouble. Strangely enough, rsync seemed to be regularly hanging when I attempted to do a "get" (sycronize a remote to a local dir). Well, considering I want to automate this, that was not going

Hi R users, I have a test dataframe ("file1," shown below) for which I am trying to create a flag for the first and last ID record (equivalent to SAS first.id and last.id variables. Dump of file1: > file1 id rx week dv1 1 1 1 1 1 2 1 1 2 1 3 1 1 3 2 4 2 1 1 3 5 2 1 2 4 6 2 1 3 1 7 3 1 1 2 8 3 1 2 3 9 3 1 3

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

Hi, I am trying to use rsync for incremental backup and I am facing some issues. I would like to ask your help to understand what is going on and have the proper command line. 1) my goal is I the following folders: ./dest: file3.txt ./orig: file1.txt   file10.txt  file2.txt   file20.txt And I would like to have as incremental backup ./dest: backup      file1.txt     file2.txt  file3.txt

I have the following situation: file2 on remote host and file1 on localhost. file1 and file2 are mostly the same. Simply running rsync remotehost:file2 file2 will actually transfer the entire file. But I would like to use the factt that I have local file1 that is mostly similar to file2. I.e. how can I make rsync to use file1 as a reference while transferring file2? (cp file1 file2 locally and

HI, I had read from the rsync man page on transferring files using the user's numeric id and gid. I have a user which resides on 2 remote sites, having the same user names, but different uid and gid on both sites. I'm transferring the files as a root user. site A site B ----------------------------------------------- usr_A usr_A uid = 100 uid = 200 file1(usr_A)

It does give a warning, but then it overwrites the files, anyway. Reproducible example below. This is R 3.4.3, but it does not seem to be fixed in R-devel: https://github.com/wch/r-source/blob/4a9ca3e5ac6b19d7faa7c9290374f7604bf0ef64/src/main/dounzip.c#L171-L174 FYI, G?bor dir.create(tmp <- tempfile()) setwd(tmp) cat("old1\n", file = "file1") cat("old2\n", file

Hi everyone, I have a question for R code to merge. Say I have two dataframes: File1 is: V1 V2 V3 V4 1 100 101 name1 2 200 201 name2 2 300 301 name3 3 400 401 name4 3 500 501 name5 4 600 601 name6 4 700 701 name7 File2 is: V1 V2 V3 V4 1 50 55 p1 3 402 449 p2 4 550 650 p3 4 651 660

Here is the structure of my servers : Source : /home/test1/link_dir sub_dir1 file1 file2 ... sub_dir2 ... Destination: /home/test2/real_dir sub_dir1 file1 file2 ... subdir2

> From: Indunil Jayasooriya <indunil75 at gmail.com> > > > > > > [root at centos67 loop]# cat file1 > > > firstname1 > > > firstname2 > > > > > > [root at centos67 loop]# cat file2 > > > lastname1 > > > lastname2 > > > > > > I need a OUTPUT like this > > > > > > > > >

Hello, I want to use the --read/write-batch options, but i have problems to do so. The shell script [1] leads to the following error: [sender] expand file_list to 131072 bytes, did move delta-transmission disabled for local transfer or --whole-file file1 rsync: writefd_unbuffered failed to write 64 bytes: phase "unknown": Daten?bergabe unterbrochen (broken pipe) rsync error: error in

On 7/27/2010 12:40 PM, Devang Patel wrote: > On Tue, Jul 27, 2010 at 7:46 AM, Chuck Zhao<czhao at eecg.toronto.edu> wrote: >> LLVM (2.7 release version) provides 2 implementations for inlining >> function callsites: >> >> - InlineSimple.cpp (-inline): inline simple callsites >> according to its cost analysis >> - InlineAlways.cpp

Hi, > Suppose I have the following source: > > file1: > #include "file2" > #include "file3" > int fn1(void) ... > > file2: > int a; > > file3: > int fn2(void) ... > > then fn1, along with all the base types etc appear to be in compile unit > "file1", the variable a appears to be in compile unit