Displaying 3 results from an estimated 3 matches for "stdout_vfprintf".
2006 Sep 29
1
Possible bug in Rcons_vprintf
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...
2006 Oct 07
1
Request to open up getConnection to embedded interface
..._initEmbeddedR(argc, argv); /* initialize R */
/* Redirect stdout to apache specific routines */
con = getConnection(1);
con->private = (void *) apr_pcalloc(p,sizeof(struct ApacheOutpcon));
con->text = FALSE; /* allows us to do binary writes */
con->vfprintf = mr_stdout_vfprintf;
con->write = mr_stdout_write;
con->fflush = mr_stdout_fflush;
...
And here are the definitions of the mr_* functions:
int mr_stdout_vfprintf(Rconnection con, const char *format, va_list ap){
RApacheOutpcon this = con->private;
apr_status_t rv;
rv = apr_bri...
2024 Mar 01
2
dput(..., file = stderr())
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",