I am developing R functions that interface with C++ code from the OpenCV
library. During development and unit testing, I embed an R instance to prepare
the environment in which the function encapsulating OpenCV code is called.
Running the unit testing suite results in starting (and later termin
On Aug 29, 2012, at 10:08 AM, Christian Sigg wrote:
> I am developing R functions that interface with C++ code from the OpenCV
> library. During development and unit testing, I embed an R instance to
> prepare the environment in which the function encapsulating OpenCV code is
> called.
>
>
I think this belongs on R-devel and I'm forwarding there.
Here's a more refined example
library("XLConnect")
load(file="ddr.Rda")
oV <- function(x) {
if (is.leaf(x)) {
return(x)
}
for (j in seq_along(x)) {
b <- oV(x[[j]])
}
x
}
res <-
There are quite a few packages that make use of tcltk and although
- most R distributions have tcltk capability
- its possible to query this via capabilities()[["tcltk"]]
- attempting to build a package that needs it on such an R
distribution will give a message letting one know
users still seem
On Aug 30, 2012, at 3:39 PM, Martin Morgan wrote:
> I think this belongs on R-devel and I'm forwarding there.
>
> Here's a more refined example
>
> library("XLConnect")
> load(file="ddr.Rda")
>
> oV <- function(x) {
> if (is.leaf(x)) {
> return(x)
> }
> for (j in se
I think Kasper got a valid point and I'd second the idea of make R
accept tildes in filenames throughout. AFAIK, this is also compatible
with most file systems, cf. http://en.wikipedia.org/wiki/Filename
However, there will be some potentially ambiguous cases. For
instance, what if you have a dir
