search for: readconsolering

Dear R developers, i've got a question concerning an embedded R instance. I called the initialization routines as seen in the "writing extensions" guide (Rf_initialize, setup_Rmainloop and R_ReplDLLinit). I also changed the function callback pointer of readconsole and writeconsoleex to my local functions. when i call mainloop there is no problem and the commands are evaluated

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were

Dear R developers, I am building an ActiveX Com wrapper for R. I have successfully implemented an Evaluate function using rproxy_impl.c and rtest.c as examples. The Com object as it stands at the moment is similar to Thomas Baier's automation server StatConnectorSrv.exe except that it does not use the Proxy. My goal it to include a couple of activeX controls in the library: One to provide a

After a long processing, I was able to create a version of a small C# class that was able to emulate the rproxy by P/Invoke. This is mostly to find a workaround a performance problem of the StatConnector. It's almost work but ... I have strange memory exception when I call the print function. The variable seems to not survive from one call to the other. As there is no debug symbol for

Dear all, my aim is to integrate R in an interactive visualisation software called Bulk Analyzer developed by VrVis (http://www.vrvis.at). the code: SEXP e, tmp; ParseStatus status; PROTECT(tmp = mkString("x <- c(1.234,-3.45)")); PrintValue(tmp); PROTECT(e = R_ParseVector(tmp, -1, &status, R_NilValue)); PrintValue(e); UNPROTECT(2); produces the following output: [1] "x

Hi - I wrapped R.dll up using somebody code online (see below). I am comparing R on .NET IPC with R(D)COM. I got it all working. Except, I realize that in my client code of the IPC remoting, if I call 'plot' function in R via EvaluateNoReturn, I don't seem to see any results on the R plot window (although the window pops up). Is there anything to do with the code of R.dll wrapper

This patch provides notification of console updates via VIRQ. The readconsolering capabilities provide the opportunity to provide console output to other clients (remote systems, logging systems, etc). This patchs adds the ability to generate a notification of a change in the console buffer. I have available both client and server programs that will take either serial line (fro...

Dear R-developers, even though I may not be the first one to encounter the problem described below, I would really appreciate some help or a link to a forum where this topic is being discussed. Probably I am simply misinformed on the usage of structRstart but see for youselve. I did check multiple forums and the whole internet on the topic without success. I am using the shared library version

I wrote the interface between R and TeXmacs. Recently, I added tab completion. However, there is one slight problem. In order to enable easy interaction with R, I (I.e. my program) interact with the command-line interface. This means that the user can invoke demo(), and then R will interact with the user and ask to press enter. It also means that the user can enter a<-c(3,4 and then R will

Currently the function Rstd_Busy() does nothing (src/unix/sys-std.c): void attribute_hidden Rstd_Busy(int which) { } The function is called through a pointer and R interfaces can change this pointer and, thus, use a different function. I don't plan to create a whole new interface to R, but I maintain a package whose aim is to provide a new feature to R when it's running in a

A common need in R frontends is to provide some sort of read, (parse), evaluate, print loop. However, there are also a number of points where frontends may want to differ from the standard REPL as available e.g. in R_ReplDLLdo1(). First some thoughts on what is needed, and what is already there, or missing. If you want to skip over this, a short summary is provided in the second half, below

These patches update the example FLASK policy shipped with Xen and enable its build if the required tools are present. The third patch requires rerunning autoconf to update tools/configure. [PATCH 1/3] flask/policy: sort dom0 accesses [PATCH 2/3] flask/policy: rework policy build system [PATCH 3/3] tools/flask: add FLASK policy to build

Hello. I've dowloaded R-0.65.1 for WinNT/9X. >There is more support for (support of) ActiveX Automation via the >Rproxy.dll: see the file front-ends/readme. And where is this "the file front-ends/readme" which describes R's ActiveX Automation ? In "readme" under "r-install path\" and FAQ for Win port, no description about this. Please teach me.

Hello. I've dowloaded R-0.65.1 for WinNT/9X. >There is more support for (support of) ActiveX Automation via the >Rproxy.dll: see the file front-ends/readme. And where is this "the file front-ends/readme" which describes R's ActiveX Automation ? In "readme" under "r-install path\" and FAQ for Win port, no description about this. Please teach me.

Dear r-helpers, I have been trying to invoke R from Java in a Windows 2000 computer (unfortunately). All my environment variables seem to be properly set, everything seems to be in order, but I obtaining a Fatal error: unable to open the base package error window. Also, the output of the invoker is Loading RInterpreter library R_HOME: R_HOME=C:/Programas/R RVersion: R_VERSION=1.6.1 whereas

The Wine development release 5.18 is now available. What's new in this release (see below for details): - Vulkan shader compilation using the new vkd3d-shader library. - USER32 library converted to PE. - Console no longer requires the curses library. - Support for display modes with various orientations. - A number of syntax fixes in the WIDL compiler. - Non-recursive makefiles.

The Wine development release 1.7.17 is now available. What's new in this release (see below for details): - More implementations for the Task Scheduler. - C runtime made more compatible by sharing source files. - Fixes in the Mac OS X joystick support. - Various bug fixes. The source is available from the following locations:

The Wine development release 5.20 is now available. What's new in this release (see below for details): - More work on the DSS cryptographic provider. - A number of fixes for windowless RichEdit. - Support for FLS callbacks. - Window resizing in the new console host. - Various bug fixes. The source is available from the following locations:

Updated set of patches for coverage. Changes: - change copyright lines - use gcov: instead of cover: in commit comment - use #ifdef in xen/common/sysctl.c instead of dummy inline function - added base documentation in docs/misc - added -h option to xencov

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -