search for: revprintf

...C please consider using the patch below in future releases. Thanks, Vadim Patch to R-2.6.1/include/R_ext/Print.h #ifdef __cplusplus extern "C" { #define CONST const #endif void Rprintf(CONST char *, ...); void REprintf(CONST char *, ...); void Rvprintf(const char *, va_list); void REvprintf(const char *, va_list); #ifdef __cplusplus } #undef CONST #endif [[alternative HTML version deleted]]

...rogram: /Users/dfaden/Desktop/R/a.out Reading symbols for shared libraries +......... done Program received signal EXC_BAD_ACCESS, Could not access memory. 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () Cannot access memory at address 0x0 Cannot access memory at address 0x0 #1 0x0054dd5c in REvprintf (format=0x5f0dc8 "%s", arg=0xbfffb5fc "") at ../../../../R-2.1.1/src/main/printutils.c:541 #2 0x0054dab0 in REprintf (format=0xbfff9570 "Error: invalid connection\n") at ../../../../R-2.1.1/src/main/printutils.c:458 #3 0x004de8c4 in verrorcall_dflt (call=0x0, format=...

...sole. Also, a corresponding interface pointer ptr_R_WriteErrConsole is added. I think this change is highly consistent with output handling in R in general. There are different sink ()s for "output" and "message", there is the distinction between Rprintf/Rvprintf and REprintf/REvprintf. This basically just carries this distinction over to the interface pointers. You will note that I wrote ptr_R_WriteErrConsole = R_WriteConsole; instead of ptr_R_WriteErrConsole = Rstd_WriteErrConsole; or ptr_R_WriteErrConsole = ptr_R_WriteConsole; This way, code that currently overrides ptr_R_Wri...

Curious to know if this warning is expected behavior, and if so, what is the recommended way instead: > dput(letters, file = stderr()) c("a", "b", "c", "d", "e", "f", "g", "h", "i", "j", "k", "l", "m", "n", "o", "p",

...orded as a warning/error. b) I'd have to add a fairly elaborate implementation in order to honor any sinks the user has (purposefully) created. If I can even access all necessary data/functions from my code (I have not investigated that, yet). 2) Similar, but add the hook a little later, in REvprintf. There, instead of directly calling R_WriteConsole, a new callback R_WriteError would be used (which defaults to R_WriteConsole). Using this callback I would get a stream of both warnings, and errors, separate from "regular" output. I could tell warnings and errors apart, using option...

...ed in Rinternals.h to installTrChar, of which it has been a wrapper since R 3.6.0. Neither are part of the API, but packages using installChar can replace it if they depend on R >= 3.6.2. * Header R_ext/Print.h defines R_USE_C99_IN_CXX and hence exposes Rvprintf and REvprintf if used with a C++11 (or later) compiler. * There are new Fortran subroutines dblepr1, realpr1 and intpr1 to print a scalar variable (gfortran 10 enforces the distinction between scalars and length-one arrays). Also labelpr to print just a label. * R_withCallingErrorHan...

...ed in Rinternals.h to installTrChar, of which it has been a wrapper since R 3.6.0. Neither are part of the API, but packages using installChar can replace it if they depend on R >= 3.6.2. * Header R_ext/Print.h defines R_USE_C99_IN_CXX and hence exposes Rvprintf and REvprintf if used with a C++11 (or later) compiler. * There are new Fortran subroutines dblepr1, realpr1 and intpr1 to print a scalar variable (gfortran 10 enforces the distinction between scalars and length-one arrays). Also labelpr to print just a label. * R_withCallingErrorHan...

...ed in Rinternals.h to installTrChar, of which it has been a wrapper since R 3.6.0. Neither are part of the API, but packages using installChar can replace it if they depend on R >= 3.6.2. * Header R_ext/Print.h defines R_USE_C99_IN_CXX and hence exposes Rvprintf and REvprintf if used with a C++11 (or later) compiler. * There are new Fortran subroutines dblepr1, realpr1 and intpr1 to print a scalar variable (gfortran 10 enforces the distinction between scalars and length-one arrays). Also labelpr to print just a label. * R_withCallingErrorHan...

...package. ? Sweave() handles keep.source=TRUE much better: it could duplicate some lines and omit comments. (Reported by John Maindonald and others.) C-LEVEL FACILITIES: ? Because they use a C99 interface which a C++ compiler is not required to support, Rvprintf and REvprintf are only defined by R_ext/Print.h in C++ code if the macro R_USE_C99_IN_CXX is defined when it is included. ? pythag duplicated the C99 function hypot. It is no longer provided, but is used as a substitute for hypot in the very unlikely event that the latter is not ava...

...package. ? Sweave() handles keep.source=TRUE much better: it could duplicate some lines and omit comments. (Reported by John Maindonald and others.) C-LEVEL FACILITIES: ? Because they use a C99 interface which a C++ compiler is not required to support, Rvprintf and REvprintf are only defined by R_ext/Print.h in C++ code if the macro R_USE_C99_IN_CXX is defined when it is included. ? pythag duplicated the C99 function hypot. It is no longer provided, but is used as a substitute for hypot in the very unlikely event that the latter is not ava...